메뉴
Use at the start of every conversation and when deciding how to approach a task. Routes to the appropriate phase of the Discover → Execute → Verify flow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use before any code change — new feature, bug fix, refactor, or tech debt. Explores the problem, builds understanding through concrete artifacts, and produces a spec that gates the transition to execution.
Use when you have an approved spec from the Discover phase. Orchestrates implementation — parallel or serial — with autonomy and guardrails.
Use after execution is complete, before declaring work ready to ship. Unified verification through multiple lenses: correctness, code quality, review, and architectural feel.
Use when creating, switching, syncing, or cleaning up git branches. Enforces naming conventions and the branching flow.
Use at the start of a new conversation or when working in an unfamiliar codebase. Generates a ranked map of the repository structure to orient before diving into code.
Use when creating a git commit. Guides intelligent staging, conventional commit message authoring, and pre-commit validation.
| name | getting-started |
| description | Use at the start of every conversation and when deciding how to approach a task. Routes to the appropriate phase of the Discover → Execute → Verify flow. |
Code-flow is a thinking discipline for any code change. One process — Discover → Execute → Verify — whether the work is a new feature, a bug fix, a refactor, or tech debt.
If you were dispatched as a subagent or teammate for a specific task, stop here. Do not activate the full workflow. You have a focused job — do it and report back. The orchestrator handles the big picture.
Only activate these skills when you are the top-level agent in a conversation with the user.
Check the project state to figure out where in the flow you are:
| Signal | You're in... | Skill |
|---|---|---|
| No spec file exists | Discover | discover |
| Spec file exists but implementation is incomplete | Execute | execute |
| Implementation matches the spec, needs verification | Verify | verify |
| User describes a new problem, feature, or bug | Discover | discover |
| User says "let's build this" with a clear spec | Execute | execute |
| User says "is this ready?" or "review this" | Verify | verify |
When in doubt, start with Discover. Exploring the problem before acting is never wasted time.
Before starting any work, check the sprint counter in CLAUDE.md:
TECH-DEBT.md.TECH-DEBT.md doesn't exist yet, create it.CLAUDE.md yet, ask the user to set one up.┌─────────┐ ┌─────────┐ ┌─────────┐
│ Discover │ ──▶ │ Execute │ ──▶ │ Verify │
└─────────┘ └─────────┘ └─────────┘
▲ │ │
└───────────────┘ │
(amend spec) │
▼
Ready to ship
Phase transitions are gated by the spec:
Code-flow ends at "ready to ship." What happens after (PR, merge, deploy) is outside this flow.