메뉴
Implement a ready Issue inside its own git worktree, building only within existing architecture. Cord-pull to needs-plan if hidden architecture is discovered. Use when advancing an Issue out of issues/ready/.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Re-validate an Issue against current main and perform the real git merge to main. Merges are serialized (one at a time). Use after the Validation Pipeline passes (auto-merge) or after a human merge-review approves.
Co-author plan.md INTERACTIVELY with a human through an interview (grill-with-docs style) for a needs-plan Issue. Agents never author a Plan alone — this Skill is the human-input gate. Invoked by /plan <id>.
Second pass over an Issue — explore the codebase, produce a candidate file list and deterministic signals, and FINALIZE Difficulty. Use for any Issue not fast-pathed as trivial by Triage.
First pass over an inbox Issue — assign Type and a provisional Difficulty from the Issue text ALONE (no code exploration). Use when advancing an Issue out of issues/inbox/.
Run the pre-merge Validation Pipeline on an Issue's worktree — intent-judge, then tests, then deterministic checks — each with a bounded fix-and-retry loop. Use for an Issue in validating/, and again at merge time for re-validation.
| name | implement |
| description | Implement a ready Issue inside its own git worktree, building only within existing architecture. Cord-pull to needs-plan if hidden architecture is discovered. Use when advancing an Issue out of issues/ready/. |
Agents implement every Issue (including architectural ones, after their Plan exists).
Build within existing architecture; do not invent architecture (DESIGN.md §7, ADR 0001).
issues/ready/<id>/ with issue.md and, if it was planned,
plan.md.main:
git worktree add -b issue/<id> .worktrees/<id> main
ln -s "$PWD/app/node_modules" .worktrees/<id>/app/node_modules
app/package.json, do not symlink — run npm install inside .worktrees/<id>/app/
instead (and note that a new dependency is an architectural signal — consider cord-pull).issue.md (+ plan.md if present). If a Plan exists, implement to its Intent,
stay inside its Files expected to change, and respect its Out of scope boundary.
Do the minimal thing — no scope creep (the intent-judge checks both directions)..worktrees/<id>/app/.issue/<id> branch:
git -C .worktrees/<id> add -A && git -C .worktrees/<id> commit -m "<id>: <summary>"
DESIGN.md §7)If you discover the Issue actually requires inventing structure (a new abstraction,
module boundary, dependency, schema/contract change) and there is no Plan, STOP. Do not
invent it. Remove the worktree and return a reclassify verdict. The trivial/standard path
can always abort upward into the human gate.
result: implemented | reclassify
branch: issue/<id> # when implemented
reclassifyTo: architectural # when reclassify
note: <what you found>
implemented → /tick moves the Issue to validating/.reclassify → /tick moves it to needs-plan/ and frees the concurrency slot.