Menu
Use when starting or clarifying a focused requirement change under SDC governance.
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.
Basé sur la classification professionnelle SOC
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 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-change |
| description | Use when starting or clarifying a focused requirement change under SDC governance. |
Codex/Hermes workflow skill generated from
commands/change.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 the requirement or change name.
Always start with Mandatory Change Intake Gate:
.sdc/common-ground.md if it exists; use ESTABLISHED items to avoid repeated questions, treat WORKING items as candidates, and ask about relevant OPEN items..sdc/expert-routing.md if it exists; use product-discovery and relevant domain/data/security profiles to shape questions, not to create facts..sdc/knowledge/index.md if it exists, then prefill known context as Confirmed only when the source is confirmed; memory-derived content remains Candidate.../../sdc-references/artifact-output-contracts.md when available. Within the same 4 intake categories, identify likely input evidence and required output artifacts: process/state diagram, sequence/integration diagram, API/contract specification, data/migration contract, UX flow, test matrix, deploy/release checklist, and AI involvement note.Proposed until the user confirms scope. Do not generate final diagrams, API designs, schemas, or release plans during intake.discovery.md, optional Draft proposal.md, and brief notes.md only.spec.md, design.md, tasks.md, impact.md, context-pack.md, or knowledge-candidates.md until Discovery Gate exits.Proposed or Assumed; do not mark them Confirmed or use them as execution inputs.For Brownfield/Legacy projects, run focused current-change impact analysis only after requirements are confirmed.