Plan
Batuta's formal planning. Use when the user invokes /batuta:plan or when work will span sessions and needs an approvable, persistent plan.From its SKILL.md
npx -y skills add franciscpd/batuta --skill planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Batuta — formal plan
Use only for work that spans sessions. Work that fits in one session uses inline planning (2–3 questions in the conversation) or goes straight into the cycle.
How
With superpowers installed, conduct steps 1–2 by the writing-plans method
(plugin root superpowers.md, /batuta:plan row); artifact, format and
approval below stay unchanged.
- Understand the goal; ask the missing questions (few, all at once).
- Break the work into atomic-commit-sized tasks. For each one:
- a 1–2 sentence description;
- estimated complexity (trivial/medium/complex/critical) and the executor predicted by the routing table;
- acceptance criteria.
- Save to
.batuta/plan-<slug>.mdin the project, in this format:
# Plan — <title>
**Goal:** <1–3 sentences>
**Created:** <date>
**Status:** proposed | approved | in progress | done
## Tasks
- [ ] 1. <task> — <predicted executor>
Accept: <criteria>
- [ ] 2. ...
## Decisions and context
<free prose: what a fresh session needs to know to resume>
- Present the plan to the user and wait for approval before executing.
- Approved → execute task by task through the normal cycle of the
batutaskill, ticking the plan's checkboxes and recording inWORK.md.
Prose + checkboxes, no rigid schema. The plan is resumable: a fresh session must be able to continue from the file alone.