planlisted

Write an implementation plan for: $ARGUMENTS (default: the most recent approved spec in `.claude/state/specs/`) ## Workflow **why-no-hook:** skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state). 1. **Read the spec**: its acceptance criteria, Seams, and Out of Scope. No spec and no approved grill outcome in the conversation? Run `/spec` first `(review-time: see section note)` 2. **Read the code the spec touches**: find and name the existing pattern each slice follows, the test runner, and the CI commands `(review-time: see section note)` 3. **Draft vertical slices** per `rules/engineering-principles.md`: `(review-time: see section note)` - Each slice cuts through every layer it needs and is verifiable on its own `(review-time: see section note)` - Each slice names the criteria it closes. A prefactor slice closes none and goes first `(review-time: see section note)` - Each slice names its tests first: one test per `test` criterion, at the spec's seams `(review-time: see section note)` - Each slice fits one fresh context window and about 100 to 300 changed lines `(review-time: see section note)` 4. **Check coverage**: every automated criterion maps to exactly one slice. A criterion with no slice, or a slice with no criterion and no prefactor reason, is a plan defect `(review-time: see section note)` 5. **Group lanes**: slices that touch disjoint files form separate lanes for `rules/parallel-agents.md`. S