What problem does it solve? Bringing existing brownfield code under specification-driven workflows normally requires hand-writing specs from scratch, which is slow and often skipped. This Skill reads a named code area's surface (exports, routes, props, signatures) and drafts honest, clearly-marked [DRAFT] living specs, then registers the capability so the rest of the Living Specs pipeline recognizes it. ## Core Features & Use Cases - Surface-first spec drafting: Reads only exported symbols, routes, and signatures to propose a small capability tree, writing requirement-and-scenario specs with confidence tags and [NEEDS CLARIFICATION] markers. - Flexible storage layouts: Supports central specs under capabilities/<name>/spec.md or colocated specs next to the code, with the layout chosen by the developer at a review gate. - Idempotent registry integration: Appends capabilities to living-specs.yml via a deterministic helper script and verifies resolver recognition, without touching unrelated specs. - Use Case: You inherit a billing module with no documentation. Point the Skill at src/billing/, confirm the proposed capability, and receive a draft living spec plus a registered capability ready for the fold-back pipeline. ## Quick Start Ask the assistant to adopt the src/billing/ directory into a living spec using a central layout.
