菜单
Work on a Technical Project Plan — read the plan, identify the current phase, do that phase's work, and update the plan with discoveries. Use when starting or resuming multi-session work tracked in a plan file.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Validation gate for freshly written code — run two independent reviews (codex CLI + a Claude review subagent) over the same scoped diff, then empirically vet every finding against ground truth before accepting or vetoing it. Use after landing a work item (especially subagent-written code) and before committing.
Work through a queue of Technical Project Plans serially — delegate each to a TDD subagent, double-review the result with codex and a Claude /review subagent, empirically vet every finding before accepting or vetoing it, and land one coherent commit per plan. Use when executing a roadmap of plan files (e.g. a _todo/ directory) for a port, migration, or multi-stage feature.
Review code for potential issues and improvements. Use when asked to review specific files, functions, or code sections.
Update the active Technical Project Plan for handoff when context is running low or the session is ending, so the next session continues instead of restarting.
Plan and execute coherent Conventional Commit groupings for large, tangled working tree changes across many files.
Iterative deep planning with critiques and alternatives. Use when facing complex design decisions requiring thorough analysis.
| name | tpp |
| description | Work on a Technical Project Plan — read the plan, identify the current phase, do that phase's work, and update the plan with discoveries. Use when starting or resuming multi-session work tracked in a plan file. |
| argument-hint | [path-to-tpp] |
| disable-model-invocation | false |
| allowed-tools | Bash, Read, Glob, Grep, Edit, Write, WebSearch, Skill |
Documented in depth: Claude Code has amnesia. So do PRs, changelogs, and your future self.
A Technical Project Plan (TPP) is a living handoff document: it carries research, design decisions, failed approaches, and next steps across sessions, so the next session (or the next engineer) continues instead of restarting.
Make progress on the referenced TPP. Determine the current phase and take appropriate action.
Before any work, you MUST read:
CLAUDE.md and/or AGENTS.md, if presentdocs/TPP-GUIDE.md if it exists; otherwise the
bundled reference TPP-GUIDE.md_todo/, or in a priority folder
(_active/, _p1/…_p4/) if this project uses them.When context runs low before the work is done, run the handoff skill rather
than letting the session end silently. When the TPP is complete, move it to
_done/.
docs/TPP-GUIDE.md (start from the bundled reference)
and tailor the layout, frontmatter fields, and template to your conventions —
the project guide always takes precedence over the bundled copy.DESIGN-PRINCIPLES.md, TDD.md, architecture decisions). Every listed file
is read on every invocation, so keep it short.claude.sh with
--append-system-prompt) so sessions reliably write to TPPs when exiting
plan mode — see the article for the pattern.