What problem does it solve? Turning rough ideas, tickets, or chat threads into durable, testable product requirements is slow and error-prone. This Skill converts accepted user intent into canonical REQ records in docs/requirements.md with stable IDs, acceptance criteria, and explicit open questions, all inside the guarded Agentic SDLC workflow. ## Core Features & Use Cases - Structured Requirement Authoring: Breaks user intent into stable REQ-* blocks with acceptance criteria, negative criteria, validation, test, and evaluation methods. - Guarded Publication: Writes only the requirements managed region through the maintain-project-specs paired publisher, preserving design bytes and existing requirement IDs. - Live Experiment Environment Capture: Records an optional guarded section for non-production test environments, including allowed actions, reset steps, and evidence rules. - Use Case: A product manager pastes a Jira ticket and Slack thread into an active SDLC run; the Skill extracts functional requirements, asks only blocking clarifying questions, and publishes a validated requirements file ready for the design phase. ## Quick Start Ask the Agentic SDLC coordinator to turn my approved project prompt into structured requirements in docs/requirements.md using the sdlc-create-requirements skill.
