By name: tpp description: Load and execute a Technical Project Plan (TPP). Use when the user invokes /tpp or references a _todo/*.md file. Reads the plan, identifies the current phase, and begins work. argument-hint: <path/to/_todo/YYYYMMDD-name.md> disable-model-invocation: true allowed-tools: Read, Glob, Grep, Bash, Edit, Write
TPP: Load and Execute a Technical Project Plan
Required reading (load before starting work)
- Read
docs/TPP-GUIDE.md— workflow conventions and phase definitions - Read
CLAUDE.md(if it exists in the project root) — codebase standards - Read the TPP file:
$ARGUMENTS
Procedure
1. Identify the TPP file
If $ARGUMENTS is blank, look in _todo/ for the most recently modified .md file:
- Use Glob to list
_todo/*.mdsorted by modification time - If there is exactly one file, use it
- If there are multiple, list them and ask the user to pick one
2. Read the TPP
Read the file in full. Extract:
- The current phase: the first unchecked
- [ ]checkbox in the "Current phase" section - The remaining tasks: unchecked items in "Remaining tasks" / "Must do" sections
- The tribal knowledge section: key gotchas, constraints, discovered facts
- The required reading list: files and docs referenced there
3. Load required reading
For each item in the TPP's "Required reading" section, read the referenced file using the Read tool. Do not skip this — these files contain critical context.
4. Act on the current phase
| Phase | Action |
|---|---|
| Research & Planning | Explore codebase, read referenced docs, update findings in TPP |
| Write breaking tests | Write failing tests that verify the desired behavior |
| Design alternatives | Generate ≥2 approaches with pros/cons, add to TPP Solutions section |
| Task breakdown | Break remaining work into specific tasks with verification commands |
| Implementation | Work through tasks in order; update TPP as each is completed |
| Review & Refinement | Review recent changes for correctness, style, DRY opportunities |
| Final Integration | Run full type-check and benchmark; verify nothing regressed |
5. After completing work in this session
Tell the user: "Context is getting full — run /handoff to update the TPP before ending this session." Do not run /handoff automatically.
Constraints
- Do not commit or push without user approval (CLAUDE.md rule)
- Keep TPP under 400 lines — trim completed tasks and redundant prose as you work
- If you discover the TPP is stale or incorrect, update it to reflect reality