todo-plan
Plan or re-plan the work in the TODO.md task tree. Use for /todo-plan [] [--revise []]. Turns a goal into a plan doc (docs/plans/PROJECT.md) and a proposed tree with lanes, or revises the plan at any time when it no longer fits. Only open [ ] nodes are changed; started or finished work is never touched. Shows the change and waits for confirmation. Never starts work.
/todo-plan
First load the todo core skill (tree format, scope rule and complexity, IDs, lanes, invariants), and read ../todo-add/SKILL.md and ../todo/reference/verification.md for how nodes are split, rated and written. If the core is not a skill, read ../todo/SKILL.md.
Never starts work and never touches code. Without --revise it plans; with it, it re-plans. Check git (core "Git mode"). In git mode read claims from git show <base>:TODO.md: the nodes of a claimed tree may be changed only from that tree's branch; anywhere else, list them as locked and leave them unchanged. Dates are date +%F. New roots, and changes to unclaimed trees, are written only on the base: on a todo/ branch, show the proposal but refuse to write it and name the base. Show every proposal in full before asking for confirmation.
Plan (default)
- Run the invariant check. Read README.md,
docs/,TODO.md,CHANGELOG.md, anddocs/plans/PROJECT.mdif it exists. - Ask once, at most 3 short questions, only for what the repo does not answer: the goal and its done-state, what is out of scope, and which parts can run in parallel (independent tracks). Skip any that are answered. When the goal is still unclear, read
../todo/reference/clarify.mdand apply its checklist and stop triggers. - Draft the plan doc
docs/plans/PROJECT.md(not written yet; ask first before creatingdocs/if it is absent; if the doc exists, propose edits to it instead of a new draft). Keep it short, sections as##headings in this order:- Goal, Scope, Out of scope.
- Lanes: one line each,
<name>: <what it covers>; independent of <lanes>. A lane is a track one agent can work alone. Usemainwhen there is only one. - Decisions and Open questions.
- Revisions: empty until the first revise.
- With an existing tree, propose only new roots (and children under open
[ ]roots in unclaimed trees); changes to existing nodes go through--revise. Propose the tree with the/todo-addrules (scope, complexity,Done when, 3 levels; if it would pass 120 lines, propose roots and first levels only, withnext: decomposewhere a node still needs children): each root getsRef: docs/plans/PROJECT.md(only when that doc exists or is written in the same confirmation) (with a section anchor when one fits) and, unless its lane ismain, aLane:inLinks:. Order roots so independent lanes do notDepends:on each other. Show IDs, complexity, lanes and one-line titles. If an RTM exists (../todo/reference/rtm.md:docs/RTM.md, else README## RTM), link roots that implement a listed requirement withRef: <rtm path>#<Req>and show the RTM row changes with the tree; with no RTM, skip this and do not offer one more than once. - Wait for confirmation. Then write the plan doc and the tree, only what the user confirms. Lint. Do not commit; the next tree claim commits them (core "Backlog files").
Revise (--revise)
Use when the user thinks the plan is not proper, at any time, even mid-tree.
- Run the invariant check. Read the plan doc (missing: propose creating it with only
## Revisions, asking before creatingdocs/) and the whole tree. Take the reason from the argument, or ask one question: "what is wrong with the plan?". - Only
[ ]nodes change.[/],[x]and[!]nodes, and anything drained to CHANGELOG, are never edited. If the change needs an active node to change, say so and offer/todo-update <ID> --status readyfirst. - Propose the change as a diff: nodes added, dropped, split, merged, re-rated, re-ordered or moved to another lane, and plan-doc lines changed. IDs are kept; new IDs follow the core rules; a dropped node is deleted from
TODO.mdand its ID is never reused (the Revisions line names it, which the ID rule counts). A plan-doc section the change needs (for example Out of scope for dropped work) is created if missing, at its place in the Plan step 3 order; other missing sections are left alone. A node with any descendant that is not[ ]is not dropped, merged or moved; say why. EveryDepends:orFrom:on a dropped ID is removed or re-pointed in the same diff (I7). - Wait for confirmation. Apply, append a bullet to Revisions in the plan doc (
- <date +%F> · <the user's reason, verbatim> · <what changed, naming every added, dropped or moved ID>), lint, and report the new tree. Do not commit, as in Plan step 5. The plan doc andTODO.mdmust agree afterwards. With an RTM, remove a dropped ID from its Tasks cell in the same diff and keep the IDs of moved or re-rated nodes unchanged.
Independent design review (optional, never a required stage)
For a high root, or one that touches security, data migration, concurrency or a public interface, offer once a design review before the first build node starts; read ../todo/reference/review.md ("Design review") only then. Never ask for it on other roots and never block a plan on it.
- Downloads
- 117All time
- Security audit
- Pass
- Last updated
- 1w ago
- Current version
- v0.1.0
- License
- MIT-0
