Menu
Use when a development request must be routed through the SDC lifecycle.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a project needs an SDC workspace, project cognition, or standards import.
Use when an approved SDC plan is ready for implementation and evidence capture.
Use when a completed SDC change is ready for archival and durable knowledge compaction.
Use when starting or clarifying a focused requirement change under SDC governance.
Use when an SDC change needs validation, review, testing, quality, impact, or repository checks.
Use when project-level AI guardrails must be generated from SDC standards.
| name | sdc |
| description | Use when a development request must be routed through the SDC lifecycle. |
Codex/Hermes workflow skill generated from
commands/sdc.md. Treat the user's current request as$ARGUMENTS. In Codex/Hermes, route to the matching SDC skill/workflow instead of expecting/sdc:*slash-command support.
Use this command as the unified SDC entry. Interpret "$ARGUMENTS" as the user's current intent and route to the correct SDC stage:
/sdc:init.sdc/common-ground.md and .sdc/expert-routing.md inside the chosen SDC stage.sdc/standards/company/ with a routing index/sdc:change, then confirmed specification and /sdc:plan/sdc:apply/sdc:check/sdc:archive/sdc:harnessPrefer the smallest correct public SDC capability. Use internal expert routing instead of adding new public commands. Stop instead of inventing shortcuts when discovery, Common Ground, decisions, knowledge sources, impact, traceability, expert coverage, or validation evidence is missing.