What problem does it solve? Feature planning in AI-assisted coding often skips discovery, produces vague stories, and loses track of state between sessions. This Skill enforces a strict, state-tracked planning pipeline that turns a feature request into validated, dependency-ordered executable work items (beads) with evidence requirements. ## Core Features & Use Cases - Phased planning pipeline (0–6): pre-flight indexing, four-lane discovery (Architecture, Patterns, Constraints, External), risk-based business and test clarification, approach synthesis, phase contracts, story maps, script-materialized beads, and graph validation. - Hook-enforced gates: mechanical guards block skipped phases, premature approvals, and invalid state transitions via .claude/hooks/planning_guard.mjs and a single authoritative JSON state file. - Deterministic bead materialization: materialize_beads.mjs converts approved Bead Specs into real br issues with dependency edges, replacing <bead:KEY> tokens with canonical IDs. - Use Case: A developer runs /onehammer:plan on a new fullstack feature; the Skill indexes the repo with Serena/GitNexus, runs discovery lanes, asks only blocking clarification questions, produces phase contracts and story maps, and outputs a cycle-free bead graph ready for execution. ## Quick Start Ask the assistant to run /onehammer:plan for your feature request and follow the PIPELINE STATUS header through each phase until the validated bead graph is produced.
