What problem does it solve? Turning a free-flowing feature discussion into an executable plan is error-prone: requirements get invented, slices arrive unordered, and criteria can't be checked. This Skill converts a feature discussion into a build document with dependency-ordered, independently verifiable slices that downstream build and review steps can execute without the original conversation. ## Core Features & Use Cases - Harvest and interview: Mines the discussion, the repo, and prior scope or wargame docs before asking only load-bearing questions, each with a recommendation attached. - Slice planning: Orders slices by dependency (data before services before surfaces), keeps each slice completable in one session, and requires checkable acceptance criteria per slice. - Fixed-format build doc: Writes to docs/plans/<date>-<feature>.md with load-bearing sections (Status lines, punch list, handoffs) that downstream build, signoff, and recheck steps read and update. - Use Case: After discussing a new export feature, ask for a build plan and receive a doc with three ordered slices, each with traceable requirements, measurable acceptance criteria, and explicit out-of-scope items. ## Quick Start Ask the assistant to blueprint the feature we just discussed into a sliced build plan.
