| name | plan-todo-setup |
| description | Set up or audit a PLAN.md, TODO.md, and TESTING.md workflow before long-running agent work. Use when the user invokes setup mode or asks to prepare the workflow. |
Plan Todo Workflow: Setup
Preferred slash command in Claude/Puku: /plan-todo-setup.
You are in setup mode for the Plan Todo Workflow plugin.
First inspect the repository root and run:
./bin/planflow setup
./bin/planflow validate
If ./bin/planflow does not exist in the target repository, use the plugin copy when available, or follow the same contract manually.
Setup mode must leave the project with:
PLAN.md containing scope, assumptions, references, architecture or approach, risks, and decisions.
TODO.md containing granular checkbox tasks ordered for unattended sequential-loop execution. Each task should reference a plan section with PLAN.md#... or PLAN.md.
TESTING.md containing agent-runnable verification criteria and closing gates for each task.
Rules:
- Do not create workflow docs that require git writes unless the user explicitly asks for git work. Do not put
git add, git commit, git push, branch operations, or staging/commit-state checks into TODO or TESTING gates.
- Design for unattended execution: avoid user-dependent gates unless they are unavoidable external blockers, and label those blockers clearly.
- Do not implement feature code in setup mode unless the user explicitly asks.
- Prefer creating missing workflow files over guessing implementation details.
- If existing files are present, preserve their intent and add only missing structure.
- End by reporting whether the workflow is ready for
research or what is still missing.