rota

/rota-plan

Write a signed-off implementation plan with verifiable tasks.

When to use

Use when an item or milestone slice is too big to one-shot, or when alignment matters before code lands, or on “plan 42”, “write a plan for this”.

Reach for another skill when

  • the item is small enough to build directly; work plans its own tasks: /rota-work
  • the design itself is still undecided: /rota-brainstorm
  • you need milestones for the whole project, not a plan for one item or slice: /rota-vision
/rota-plan
Usually after/rota-work
Exampleillustrative, condensed
/rota-plan B03
Goal: --limit 0 yields zero rows.
T1. Treat 0 as a real limit in cmd/list.go.
    Verify: go test ./cmd -run TestListLimitZero
Confirm this plan? (yes / changes)
yes
What changes
  • the plan written to .rota/plans/B03.md (issue backend: a note on the issue)

Details

Writes an implementation plan before /rota-work runs, keyed by a milestone slice (M01-S01) or an item (M01-B07, #42). Each task must fit one execution window and have a verifiable outcome. /rota-work consults the plan automatically if one exists. See vision and plans for the full flow.

Edit this page on GitHub