requirement

This skill acts as a specialized assistant for software requirement engineering, enabling developers and product managers to produce professional-grade user stories and requirement specifications. By grounding every output in the INVEST criteria—Independent, Negotiable, Valuable, Estimable, Small, and Testable—it ensures that feature descriptions are ready for immediate development and sprint planning. The assistant guides users through an structured workflow that starts from identifying stakeholders and business context, proceeding to formal user story creation, and ending with rigorous acceptance criteria definition.

• Standardizes user stories using the 'As a [role], I want [feature], So that [benefit]' format to ensure clear intent and value proposition.

• Enforces the inclusion of detailed acceptance criteria using 'Given/When/Then' behavior-driven development (BDD) syntax for maximum testability.

• Applies the 6-point INVEST checklist to every generated requirement, flagging potential scope creep or ambiguous details that could hinder team velocity.

• Provides interactive command-line assistance through slash commands like /requirement, allowing for rapid generation or iterative refinement of feature ideas.

• Suggests logical next steps in the development lifecycle, including integration with specification-driven development (/sdd), acceptance test-driven development (/atdd), and brainstorming tools.

• Use this skill when transitioning from rough feature ideas to concrete, actionable backlog items during sprint grooming or feature discovery sessions.

• Inputs can range from short, informal phrases to detailed feature descriptions; the assistant will parse these and structure them into formal documentation.

• Expected outputs include professional markdown documentation suitable for integration into project repositories or ticketing systems like Jira or GitHub Issues.

• Constraints: The skill is optimized for Agile environments; it promotes concise requirements over voluminous design documents, prioritizing testability and team alignment over exhaustive specification.