← ClaudeAtlas

staged-coding-2-restraintlisted

staged-coding stage 2 - restraint (decide what NOT to build). Runs a do-less pass and applies the lane-specific guard - BUG lane against over-building, EPIC lane against under-building. Signs its ledger line on finish. Triggers: /staged-coding-2-restraint, or invoked in order by /staged-coding.
Shadysmetools/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill Shadysmetools/claude-skills
# Stage 2 - restraint (decide what NOT to build) Part of the `/staged-coding` chain. Runs after Stage 1 (recon) and before Stage 2.5 (ask the owner). Callable alone; the conductor carries the cross-cutting rules. ## Inputs - What already exists (reuse candidates) and the call path traced in Stage 1 - The lane: BUG (bugs board) or EPIC (product board), set once at the start of the run ## What to do Run a do-less pass (a YAGNI / minimalism skill if available, e.g. `ponytail`; otherwise do it by hand). Question whether the task needs to exist at all; reach for the standard library before custom code, native platform features before dependencies, one line before fifty. A guardrail that is only referenced, never run, enforces nothing: actually run it. **The failure direction depends on your lane.** The two lanes drift in OPPOSITE directions, so "be restrained" means different things: - **BUG lane -> guard against over-building.** The risk is wandering past the defect into adjacent code that was never broken. This is NOT the same as Stage 4's "fix every call site of the same defect" rule: widening to every sibling of the SAME defect is required; drifting into unrelated nearby code because you are already in the file is the over-building this guard stops. Same file, two different instincts. Know which one you are following. - **EPIC lane -> guard against under-building.** The risk is trimming a slice until it no longer meets its own WHEN/THEN/SHALL acceptance criter