buildlisted

Implement the approved plan incrementally: $ARGUMENTS Follow these disciplines: ## Before Starting **why-not-mechanizable:** skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state). - Verify an approved plan exists (in `.claude/state/plans/` or the current conversation) `(review-time: see section note)` - If no plan exists, stop and ask the user to run /plan first `(review-time: see section note)` - Read the plan and identify the task list `(review-time: see section note)` - Load relevant expert agents based on the plan's domain (see `rules/agent-routing.md`) - their guardrails apply to every increment `(review-time: see section note)` - If the plan has 2+ file-isolated lanes, execute it in **lane mode** - spawn one lane-mode teammate per lane (see `rules/parallel-agents.md`); single-lane plans stay in this session `(review-time: lane-vs-single judgment from the plan shape)` ## Increment Rules For each task in the plan: 1. **Ask**: "What is the simplest thing that could work?" `(review-time: see section note)` 2. **Scope**: touch only what the task requires - no drive-by refactors, no "while I'm here" changes `(review-time: see section note)` 3. **Follow `rules/engineering-principles.md`**: vertical slicing, change sizing (~100 lines per commit, max 300, split at 1000+), and anti-rationalization rules all apply `(review-time: see section note)` 4. **Compile continuously**: the project must build after every incr