Menu
Use when a confirmed SDC change needs an executable design, task plan, and context handoff.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Use when a development request must be routed through the SDC lifecycle.
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.
Basé sur la classification professionnelle SOC
| name | sdc-plan |
| description | Use when a confirmed SDC change needs an executable design, task plan, and context handoff. |
Codex/Hermes workflow skill generated from
commands/plan.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 "$ARGUMENTS" as extra planning context. Ensure the plan is based on current SDC proposal/spec/design/tasks and produces small, verifiable tasks.
Run the SDC plan workflow:
.sdc/common-ground.md; do not plan final execution from OPEN or high-impact WORKING items..sdc/expert-routing.md; select the smallest relevant expert profiles internally..sdc/knowledge/index.md and relevant product/technical knowledge before planning.../../sdc-references/artifact-output-contracts.md when available. Convert the confirmed output contract into concrete design sections and validation tasks.../../sdc-references/execution-orchestration.md when available. Produce the Global Constraints, Plan Preflight, task interface, and review fields required for reliable execution.SCN -> REQ -> AC -> T### traceability.design.md: process/state diagrams, sequence/integration diagrams, API/contract specs, data/migration contracts, UX flow, test matrix, deploy/release checklist, and AI involvement note. If a triggered artifact is not applicable, write N/A with evidence-based reason.context-pack.md as the short execution handoff: goal, knowledge sources, Common Ground used, Expert Profiles Used, confirmed product/technical knowledge, boundaries, forbidden assumptions, tasks, validation commands, and candidate routing.Artifact Output Contract in context-pack.md so apply/check agents know which outputs must remain satisfied.Global Constraints in design.md, tasks.md, and context-pack.md; do not weaken exact values by paraphrasing.Status: Passed only after task conflicts, placeholders, undefined interfaces, and review-hostile instructions are resolved.Files, Consumes, Produces, Verify, Expected, Review, Evidence, and Source fields.S or M.