원클릭으로
worktree
Use for non-trivial or parallel work that should happen in a separate git worktree.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use for non-trivial or parallel work that should happen in a separate git worktree.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | worktree |
| description | Use for non-trivial or parallel work that should happen in a separate git worktree. |
git worktree add ../<repo>-<topic> -b <type>/<topic> # <type>: feat | fix | chore | ...
cd ../<repo>-<topic> && <setup> && <run tests>
Baseline must be green. If red, STOP - don't build on broken ground. Done -> ship.