What problem does it solve? Teams running an Agentic SDLC workflow need architecture and feature designs that stay traceable to approved requirements, but design documents often drift, lose stable IDs, or get rewritten without evidence. This Skill turns requirements and gathered context into canonical FEAT records in docs/design.md with preserved IDs and validated ownership. ## Core Features & Use Cases - Requirements-to-Design Mapping: Maps stable REQ-* blocks to stable FEAT-* blocks, recording selected and rejected design options with trade-offs and reversibility. - Failure-Driven Redesign: Admits redesign only with classifier-validated proof of a system-contract defect, reproducibility, and durable human approval when public contracts change. - Vertical Feature Flow Design: Defines end-to-end layer maps, boundary contracts, validation, test, rollout, and rollback plans per feature before planning starts. - Use Case: After requirements are approved, the SDLC coordinator routes to this Skill to produce docs/design.md where every P0 requirement maps to a ready feature with implementation boundaries and done criteria. ## Quick Start Ask the Agentic SDLC coordinator to create the initial design from docs/requirements.md and the gathered context packs using the sdlc-create-design adapter.
