What problem does it solve? Vague ideas, GitHub issues, and stakeholder notes often jump straight into code without clear scope, leading to rework and misaligned expectations. This Skill turns that rough input into a structured specification with defined scope, testable acceptance criteria, constraints, risks, and open questions before any coding begins. ## Core Features & Use Cases - Structured Spec Generation: Produces a consistent specification template covering problem, goal, scope, acceptance criteria, constraints, assumptions, risks, and suggested implementation waves. - Flexible Input Handling: Accepts rough ideas, GitHub issues, bug reports, feature requests, product requirements, or technical improvement requests. - Uncertainty Management: Forces assumptions and open questions to be explicit instead of inventing business rules silently. - Use Case: A product manager pastes a vague stakeholder request like "users want better notifications" and receives a complete spec with in-scope/out-of-scope boundaries, Given/When/Then acceptance criteria, and a review checklist ready for team approval. ## Quick Start Turn this GitHub issue about slow dashboard loading into a full specification with scope, acceptance criteria, and risks.
