l4ci
@l4ci
Public Skills
rota-capture
by l4ci
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.
rota-orchestrate
by l4ci
Use on "you are the orchestrator", "run a round", "orchestrate", "assign the next issues to the workers", "what are my workers doing".
rota-release
by l4ci
Use on "release", "cut a release", "tag a release", "ship X.Y.Z".
rota-plan
by l4ci
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".
rota-work
by l4ci
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.
rota-review
by l4ci
Use on "review this", "check before I ship", "look over the branch", before a merge or PR, or implicitly from /rota-ship.
rota-ship
by l4ci
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". Use --docs on "update docs".
rota-refactor
by l4ci
Use on "review the architecture", "find refactoring opportunities", "deepen modules", or scoped to one area ("/rota-refactor internal/cli").
rota-learn
by l4ci
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".
rota-brainstorm
by l4ci
Use when a Major feature or P0 bug needs design negotiation before implementation planning, or on "brainstorm 42", "design this item".
rota-spike
by l4ci
Use when X must be tried before committing to it ("can we use SSE?", "does this library handle our scale?") and the answer is a finding, not shipped code.
rota-decide
by l4ci
Use on "decide on X", "we're committing to X", "lock in the boundary that Y", or when a session has produced a constraint future work must respect. Manual only, never auto-invoked.
rota-debug
by l4ci
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.
rota-vision
by l4ci
Use on "let's plan", "what's the bigger picture", "create a roadmap", "brainstorm milestones".
rota-pause
by l4ci
Use when the session is approaching a context limit, the work must be handed off, a long /rota-work cycle should stop cleanly, or an orchestrator must stop mid-round.
rota-qa
by l4ci
Use on "/rota-qa", "run QA", "test the feature", "validate the build", before ship as a gate, or on the first cycle to scaffold a per-repo QA strategy. QA of the built product, not the diff.