Tip · Plan, Build
Plan and ship are separate steps
Your agent never chains planning into building on its own, so you can review the plan before any code changes.
/planr:plan$plan@planr-plan ends with a handoff: it names the next ready task and gives you the exact command to build it. It never starts building on its own, and the router never chains the two on your behalf.
That pause is the point. Read the stories and tasks, fix what is wrong, and commit them. Then start the build with /ship$ship@planr-ship and one task ID.
Related prompts
Break a spec into stories and tasks
Get user stories and tasks with acceptance criteria and file-level changes.
Plan straight from a clear request
When the request is already clear, skip the spec and get stories and tasks from it.
Plan UI work from a finished design
Turn a design and its design spec into UI tasks that carry the screens, states, and frames.