staged-coding-3-planlisted
Install: claude install-skill Shadysmetools/claude-skills
# Stage 3 - plan (only if it needs one) + council (only on the four markers)
Part of the `/staged-coding` chain. Runs after Stage 2.5 (ask the owner) and before Stage 3.5
(pre-mortem, which reads this plan) and Stage 4 (build). Callable alone (e.g. to re-plan a ticket
that came back from Stage 4 needing a different approach); the conductor carries the cross-cutting
rules, including the "council vs refuter" comparison, which is not repeated here.
## Inputs
- The ticket / slices from Stage 1 and the build / will-not-build list from Stage 2
- The owner's answers from Stage 2.5 (or its "nothing unclear" receipt)
- `config.checker_model` and `config.council_second_opinion` (optional second-vendor CLI)
## What to do
### Plan (only if it needs one)
If the approach is not obvious, write a plan (a plan-writing skill if available, e.g.
`writing-plans`) and name the unknowns. Small mechanical ticket -> skip and say so. If the ticket's
scope feels wrong or underspecified, grill yourself on it (e.g. `grill-me`) rather than guessing.
Self-grilling interrogates YOU; Stage 2.5 interrogates the OWNER. They are not substitutes.
### Council - only on the four markers
The builder writes the code on every ticket (on `config.builder_model`). A council of two advisors
(`config.checker_model` plus, ideally, a second vendor via `config.council_second_opinion`), run in
parallel and told to disagree with each other, sits **only** when a ticket hits one of four markers:
- **(a)** it touches log