What problem does it solve? Building features without structure leads to unchallenged requirements, missing specs, and untracked work. This Skill enforces a disciplined, phase-gated workflow that captures the change, challenges the why, grills the how, writes the spec, slices tickets, and only then implements code. ## Core Features & Use Cases - Gated five-phase workflow: Capture the change and mint its key, challenge and shape requirements, write the spec, slice blocking-ordered tickets, then implement and review, with a stop-and-ask gate between every phase. - Change key and work item tracking: Mints a collision-safe change key via a sha-guarded counter on the coordination branch and opens a tracker work item that holds the why, challenge, specification pointer, and tickets. - Autopilot and --ship modes: Supports unattended runs that auto-advance gates while still recording verdicts, with a defined ceiling (review, preprod, or release) based on repository authority configuration. - Use Case: Describe a new feature in one line (or reference a brainstorm idea issue), and the Skill walks it through requirement grilling, spec writing, ticket slicing, test-first implementation, and code review before handing off to merge. ## Quick Start Run /feature with a short description of what you want to build, or pass a brainstorm idea issue number, and approve each phase gate as the workflow progresses.
