What problem does it solve? Writing consistent story-layer artifacts (use cases, user stories, acceptance criteria) is slow and error-prone, often producing vague acceptance criteria or missing exception flows. This Skill standardizes the process by seeding structured templates with traceable IDs and enforcing quality rules. ## Core Features & Use Cases - Three output modes: usecase produces a Cockburn-style USECASE.md, userstory produces a prioritized USER_STORIES.md backlog, and ac produces Given/When/Then acceptance criteria in AC.md. - Hard quality contract: Blocks vague acceptance criteria ("works", "as per spec"), requires extension/exception flows on use cases, and mandates actor/need/value plus priority on stories. - Traceability: Links UC/US/AC/BR IDs across artifacts and records open questions with blocking flags for handoff to testers or business analysts. - Use Case: A business analyst needs acceptance criteria for a login feature. Run mode ac to generate AC.md with testable Given/When/Then statements mapped to US and FR IDs. ## Quick Start Use the story-spec skill with mode=ac to generate Given/When/Then acceptance criteria for the login epic from the AC template.