메뉴
Use after design approval for milestone plans with executable acceptance.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use at ship time to merge the spec into the living documentation, delete the staging spec and plan, and ask how to finish.
Use when taking over an existing codebase that has no living document. Produces a factual record of what already exists.
Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.
Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.
Use at session start to learn how Praxis skills are invoked and why triage runs before every task.
Use when the goal is vague or vision-level and can't be defined well enough for design questions.
SOC 직업 분류 기준
| name | plan |
| description | Use after design approval for milestone plans with executable acceptance. |
docs/staging/plans/YYYY-MM-DD-<topic>.md. Reference the spec; don't restate it.
If unresolved spec notes affect implementation or task order, return to design.
Spec references a milestone (milestone: MN)? Check docs/ROADMAP.md — expand only that milestone. Leave the rest as stubs.
After ship: open docs/ROADMAP.md, confirm which milestone is next, then expand it. Return to design only if the milestone's goal materially changed.
Every task is - [ ] T<n>: <name> - always a checkbox, never a heading. tdd/subagents flip it to - [x] on completion; ship refuses to run while any - [ ] remains.
goal: <one sentence>
files: <paths>
acceptance: <test or cmd>
spec: <docs/staging/specs/...#anchor>
No exact code. No step-by-step. Acceptance is verifiable: a test, command, or scripted check — or, when none is possible, an explicit manual check (steps + expected result). Each task leaves the repo green.
Mark independent tasks: [parallel] T3, T4, T5.
Only mark [parallel] when shared contracts, state, errors, and acceptance are closed.
Atomic expansion is deferred until dispatch time - subagents expands a milestone into 2-5 min steps at dispatch time, not here.
for New project: derive an initialization task — scaffold code, tests, CI, and always include: README.md, CHANGELOG.md, .gitignore, and a Makefile (or equivalent task runner config).
background, architecture, rationale (spec), CI commands, copy-pasted acceptance.
<gate> docs/staging/plans/YYYY-MM-DD-<topic>.md must exist on disk before handing off to tdd/subagents.</gate>
Confirm plan with the user.
mostly [parallel] -> subagents. Otherwise -> tdd.