feature-spec

Generates structured PRDs with goals, user stories, requirements, and metrics.

1|Updated May 7, 2022

Search Tags:#requirements #product management #acceptance criteria #PRD #feature specification #user stories

Ready to run

npx skills add https://github.com/brandonburrus/dotfiles --skill feature-spec-brandonburrus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/brandonburrus/dotfiles/tree/main/.agents/skills/feature-spec
Command: npx skills add https://github.com/brandonburrus/dotfiles --skill feature-spec-brandonburrus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive product requirements documents (PRDs), ensuring clarity on what to build, why, and how success will be measured.

Core Features & Use Cases

Structured PRD Generation: Guides users through defining problem statements, goals, user stories, requirements, and success metrics.
Scope Management: Helps prevent scope creep by defining non-goals and prioritizing requirements.
Use Case: A product manager needs to spec out a new user authentication feature. They use this Skill to define the problem of insecure logins, outline goals for improved security and user experience, write user stories for different user types, and detail must-have and nice-to-have requirements.

Quick Start

Use the feature-spec skill to write a PRD for a new user profile editing feature.

Frequently Asked Questions about feature-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write structured product requirements for a new feature?▼

To write structured product requirements, define the problem statement, goals, user stories, requirements, and success metrics. This approach ensures clarity on what to build and why, while explicitly outlining non-goals to prevent scope creep.

What should be included in a PRD to prevent scope creep?▼

A PRD prevents scope creep by explicitly defining non-goals alongside core requirements. Utilizing a prioritization framework like MoSCoW helps categorize must-have features versus nice-to-haves, keeping the feature specification focused on intended outcomes.

How do I define acceptance criteria and success metrics for user stories?▼

Defining acceptance criteria and success metrics involves detailing specific conditions that user stories must meet and how outcomes will be measured. This Skill guides you through establishing these metrics to ensure the feature specification tracks actual product success.

Can I use the MoSCoW method to prioritize requirements in a feature specification?▼

Yes, you can use the MoSCoW method to prioritize requirements in a feature specification. This framework categorizes features into must-have, should-have, could-have, and won't-have items, facilitating effective scope management within your product requirements document.

What is the best way to structure a product requirements document for an authentication feature?▼

The best way to structure a product requirements document is to start with the problem statement, outline specific goals, write user stories for different user types, and detail prioritized requirements. This ensures comprehensive coverage of the authentication feature's needs.