tally

Use before building any feature or non-trivial change — explores the problem, cuts scope, and lands an approved design in a tally scratchpad before any code is written. Triggers on "let's brainstorm", "help me think through", or ambiguous feature requests.

Execute a plan task-by-task with fresh subagents — TDD, per-task review, tally todos as the ledger. Runs inside its own worktree from a plan:<slug> scratchpad, opens a PR, then review. Use after /tally:plan (usually dispatched into a worktree), or directly on any plan:<slug> todos.

Use on any bug, test failure, or unexpected behavior, before proposing fixes — root cause first, one hypothesis at a time. The second loop entry beside /tally:brainstorm; exits into an inline fix or /tally:plan.

Turn an approved design into an executable plan — authored as a plan:<slug> scratchpad (surfaced beside the live todos) plus one tally todo per task; in herdr, dispatches the build into its own worktree. Use after /tally:brainstorm, once a design scratchpad exists.

Whole-branch adversarial review before merge — runs against the open PR (build opens it), scoped reviewers probe the live tree, findings carry verdicts and defined severities, p1s fixed in one consolidated pass pushed to the PR. Use when a feature branch is complete (after /tally:build) or before merge.

One-time, consent-gated setup of the tally dev loop for this repo — asks before enabling session routing, proposes repo-specific reviewer lenses, then writes .claude/tally-dev-loop.md. Use when the user asks to set up, enable, or configure the dev loop, or when another tally skill suggested it.