Coding agents write fast. rota makes sure what they merge works.

Step 1 of 3 Write the item down. Capture records it and stops.

[B03] list shows every row when the limit is zero   Bug, P2

Use when the user brain-dumps work, says “capture”, “add to backlog”, “note this bug”, “/rota-capture”, or describes a problem without asking for an immediate fix. Also use on “remove [B07]”, “delete this entry”, “drop this item” to delete captured items. Use --triage <N> on a tracker issue filed by someone else. All about /rota-capture

Step 2 of 3 Build it in small commits. The proof gate needs a red run, then a green one.

Tree clean. Branch rota/B03-limit-zero created.
T1  treat 0 as a real limit in cmd/list.go
    rota proof record B03 -- go test ./cmd -run TestListLimitZero   FAIL (red run)
    rota proof record B03 -- go test ./cmd -run TestListLimitZero   PASS
a1b2c3d fix: treat --limit 0 as zero rows [B03]

Use when backlog items already exist and need implementation (“implement 42”, “build these”, or “implement [B07]” on the file backend), or with no argument to reconcile active work and pick the next item. A parallel round with standing workers is /rota-orchestrate, not this skill; an item not yet captured goes through /rota-capture first. All about /rota-work

Step 3 of 3 Review the branch, then open the PR or merge.

/rota-review: PASS
PR body built from commit subjects and resolved IDs: B03
Merged into main with --no-ff; branch deleted.

Use on “ship it”, “open the PR”, “finish this branch”, or when work is done and ready to integrate. Use –undo on “roll back the last cycle”, “revert that merge”. All about /rota-ship

Step 1 of 3 Reproduce it, test one hypothesis at a time, fix it in one commit.

Reproducer: TestAmountRoundTrip FAILED (0.10 -> 9, want 10)
H1 (likely): the minor-unit helper multiplies a float64 by 100 and truncates.
Verified H1: the intermediate float prints 9.999999999999998.
Fix: decimal Shift(2) instead of Float64() * 100. Reproducer passes.
fix(money): use decimal.Shift instead of Float64 for minor-unit conversion
Root cause was non-obvious. Consider running /rota-learn to capture this.

Use on “debug 42” or “debug [B07]” on the file backend, “why is X broken”, “investigate the crash”, or when a bug needs a proper cycle rather than a one-shot fix. All about /rota-debug

Step 2 of 3 Review and merge the fix.

/rota-review: PASS
PR body built from commit subjects and resolved IDs: F04
Merged into main with --no-ff; branch deleted.

Use on “ship it”, “open the PR”, “finish this branch”, or when work is done and ready to integrate. Use –undo on “roll back the last cycle”, “revert that merge”. All about /rota-ship

Step 3 of 3 Keep what the bug taught you for the next session.

Proposed bullet under ## Money & Decimals:
Never multiply a decimal.Decimal by a float to convert to minor units. Float64() * 100 gives 9.999... for 0.10, and truncation gives 9. Use decimal.NewFromString(...).Shift(2).IntPart() end to end.
Written to .rota/KNOWLEDGE.md.

Use at the end of a session that surfaced reusable knowledge, after a correction-rich debugging arc, or on “save what we learned”, “capture this learning”, “/rota-learn”. All about /rota-learn

Step 1 of 5 Shape the slate so every issue has clear acceptance.

Planning dial: 2 (spec) - new flag on a published command; revert is clean. Override: say "level 1" or "level 4".
Goal: export --since DATE keeps only rows on or after DATE.
T1. Parse and validate --since in cmd/export.go (AC-1).
    Verify: go test ./cmd -run TestExportSince
T2. Document the flag in docs/usage/export.md (AC-2).
    Verify: grep -n -e --since docs/usage/export.md
Confirm this plan? (yes / changes)

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”. All about /rota-plan

Step 2 of 5 Hand issues to workers, review their PRs, merge through the gate.

rota round start --scope slate --items 42,51,58,63
rota round assign 42   # claims #42, cuts <agent>/42-<slug>, starts a worker
...
Armed rota round watch in the background; it wakes me on a slot, PR or escalation change.

Use on “you are the orchestrator”, “run a round”, “orchestrate”, “assign the next issues to the workers”, “what are my workers doing”. All about /rota-orchestrate

Step 3 of 5 Answer the decisions the round put to you, one at a time.

1 of 3: slot nia is blocked on #58.
Worker asks: keep the old --json shape or break it?
A) Keep the old shape (recommended)
B) Break it and note it in the changelog
C) Write your own answer

Recorded as a decision comment on #58 and relayed to nia.

Use only when the maintainer types “/rota-answer” during a round. The orchestrator points the maintainer to it when two or more decisions wait; it never starts it. All about /rota-answer

Step 4 of 5 At wind-down, keep what the round learned.

Read the round summary: #58 bounced twice on the same criterion.
Proposed bullet under ## Rounds:
A criterion with two readings produces the same wrong PR on every bounce. Audit the acceptance criteria before the third relay.
Written to .rota/KNOWLEDGE.md.

Use at the end of a session that surfaced reusable knowledge, after a correction-rich debugging arc, or on “save what we learned”, “capture this learning”, “/rota-learn”. All about /rota-learn

Step 5 of 5 Cut a release when the work adds up to one.

Checklist (.rota/RELEASE.md): all items pass.
Commits since v0.25.0: 1 feature, 4 fixes. Recommend minor.

Release notes drafted for v0.26.0.
Notes look good? Yes pushes the tag and publishes the release. (manual gate)

Use on “release”, “cut a release”, “tag a release”, “ship X.Y.Z”. All about /rota-release