writing-prds

A PRD captures feature scope, goals, and acceptance criteria in structured format. This Skill generates PRDs with user stories in role-benefit format, acceptance criteria using Given/When/Then style, and enforces a standard structure covering overview, goals, stakeholders, requirements, and timeline to align teams on scope.

User stories describe what a role needs and why in narrative form; acceptance criteria define testable conditions that must pass. This Skill formats user stories as "As a [role], I want [feature] so that [benefit]" and acceptance criteria as Given/When/Then scenarios, ensuring clarity on scope and expected behavior.

Acceptance criteria define explicit boundaries for what a feature does and doesn't include. This Skill applies Given/When/Then format to capture edge cases and limits, includes an Out of Scope section, and follows INVEST principles to keep requirements focused and prevent unplanned feature expansion.

This Skill generates PRDs for new features, projects, or initiatives of any scope. It guides task capture for goals, stakeholders, user stories, and timelines, then saves the structured document to a standard artifact path, making it suitable for single features or larger product initiatives.

Effective PRDs include goals and metrics, identified stakeholders, clear user stories with roles and benefits, detailed acceptance criteria, functional and non-functional requirements, and realistic timelines. This Skill enforces that structure and Given/When/Then criteria to ensure all parties understand scope, success measures, and dependencies.

A complete PRD has all sections filled: overview, goals with metrics, user stories following INVEST principles, Given/When/Then acceptance criteria for each story, functional and non-functional requirements, out-of-scope boundaries, and a defined timeline. This Skill enforces that checklist and outputs a formatted markdown document ready for team execution.