메뉴
Use when a project needs an SDC workspace, project cognition, or standards import.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when a development request must be routed through the SDC lifecycle.
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.
SOC 직업 분류 기준
| name | sdc-init |
| description | Use when a project needs an SDC workspace, project cognition, or standards import. |
Codex/Hermes workflow skill generated from
commands/init.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.
Initialize or repair the standard .sdc/ workspace in the current project. Treat "$ARGUMENTS" as additional project context.
Do not overwrite user-authored .sdc/ artifacts. If old SDC-generated managed templates are clearly stale, upgrade them to the current schema only with a .bak-* backup and report the repair.
Run the SDC init workflow:
.sdc/ idempotently.constitution.md, project.md, project-cognition.md, common-ground.md, expert-routing.md, knowledge/, memory/, standards/, templates/, changes/, specs/, decisions/, reviews/, and reports/.common-ground.md with ESTABLISHED / WORKING / OPEN sections; do not mark generated starter content as ESTABLISHED.expert-routing.md with candidate expert profiles; do not expose those profiles as additional public slash commands..sdc/standards/company/ and create a routing index. Do not publish those private rules with SDC.project-cognition.md; do not perform per-change impact analysis during init.