메뉴
Turn a request, ticket, or file into a phased implementation plan. Use to plan a feature before building, or to turn a ticket into phases. Do NOT use to write code or review a diff.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
| name | 01-plan |
| description | Turn a request, ticket, or file into a phased implementation plan. Use to plan a feature before building, or to turn a ticket into phases. Do NOT use to write code or review a diff. |
| argument-hint | gather | explore | wireframe | plan |
Turn a gathered source into an implementation plan and its phase files. Never writes code.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | gather | Collect and restate the source | user request |
| 02 | explore | Read the codebase for projection, rules, feasibility | gathered source |
| 03 | wireframe | Sketch a screen at low fidelity, frontend only | source + explore context |
| 04 | plan | Break into phases, write the plan and phase files | explore output + wireframe |
Run them in order, 01 → 04. The plan is the culmination. Skip 03 when there is no UI.
Before running an action, read its file in actions/, not only the table or assets.
references/wireframe-conventions.md: how to draw the ASCII wireframe a screen needs.references/plan-status.md: the plan lifecycle status values and who writes each.assets/plan-template.md: the plan.md scaffold.assets/phase-template.md: the per-phase scaffold.