From codex-next
Coordinates SDLC workflows: identifies if work needs SDLC treatment, routes to authoring skills for requirements, architecture, specs, validation, traceability, readiness, handoff, and change control.
How this skill is triggered — by the user, by Claude, or both
Slash command
/codex-next:sdlc-managerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill as the SDLC entrypoint inside Codex Next. It manages which SDLC
Use this skill as the SDLC entrypoint inside Codex Next. It manages which SDLC
workflow should run next, while keeping sdlc-router focused on lane, ADS, and
minimum-material classification.
This skill coordinates. It does not replace the authoring skills.
For canonical lane, ADS, dev path, ID, local/sdlc, delivery card, and
midstream-intake vocabulary, follow:
../sdlc-router/references/sdlc-operating-model.md
Identify whether this is SDLC work.
local/sdlc, or release-risk planning are SDLC work.dev-* skill.Decide whether routing is enough.
sdlc-router.dev-spec-driven-implementation or the relevant dev-* skill instead of
stopping at planning.Treat external proposals as reference input.
REQ, TASK, or VAL.| Need | Next skill |
|---|---|
| Lane, ADS, dev path, or minimum materials | sdlc-router |
| Existing repo capability map | sdlc-project-research |
| Requirements package | sdlc-requirements-workflow |
| Business, user, or product incubation | sdlc-brd-workflow, sdlc-urs-workflow, or sdlc-prd-workflow |
| Software requirements | sdlc-srs-workflow |
| Measurable quality constraints | sdlc-nfr-spec |
| Architecture or high-level design | sdlc-hld-workflow |
| Detailed design | sdlc-lld-workflow |
| Domain ownership or dependency boundaries | sdlc-domain-boundary-modeling |
| Modular monolith architecture | sdlc-modular-monolith-architecture |
| Durable architecture decision | sdlc-architecture-decision-record |
| Solution/spec package coordination | sdlc-solution-spec-workflow |
| Implementation-facing slice | sdlc-spec-slice-writer |
| Validation artifact | sdlc-validation-plan-workflow |
| Traceability | sdlc-requirements-traceability |
| Readiness review | sdlc-readiness-review |
| Baseline or scope change | sdlc-change-control |
| Dev handoff | sdlc-dev-handoff-planning |
When managing only, return:
## SDLC Manager Route
- Intent:
- Current evidence:
- SDLC need:
- Next skill:
- Why:
- Not needed:
- Next action:
When the user asks to solve, author, or implement, do not stop after routing. Continue with the selected skill and report the actual result.
npx claudepluginhub blueskyxn/codex-is-all-you-need --plugin codex-nextRoutes SDLC/ADS work by lane (bugfix, new feature, refactor, rebuild, greenfield) and selects minimal required materials. Use when delivery scope or material needs are unclear.
Orchestrates 6-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) for guided feature development. Supports plan persistence, wave-based resume, autonomous mode, verification, and Stitch UI integration.
Routes SDLC requests to specialist skills by detecting CMMI maturity level. Covers requirements management, design documentation, quality assurance, governance, metrics, and process adoption on projects.