feature-spec

To write a product requirements document, define the problem statement, goals, non-goals, user stories, requirements, and success metrics. The feature-spec skill structures these elements to prevent scope creep by categorizing requirements into Must-Have, Nice-to-Have, and Future Considerations.

Acceptance criteria for user stories should include explicit conditions that define success and prevent scope creep. The feature-spec skill facilitates defining these criteria alongside problem statements and user stories to ensure clear product decisions for new feature development.

To prevent scope creep in a PRD, explicitly document non-goals alongside your feature requirements. The feature-spec skill enforces this by guiding product managers to define non-goals and categorize requirements into Must-Have, Nice-to-Have, and Future Considerations.

Yes, you can write user stories for different user types. The feature-spec skill supports product managers in documenting problem statements and specifying user stories and acceptance criteria tailored to various user types within a new feature flow.

The best way to structure success metrics for feature development is to align them with documented goals and problem statements. The feature-spec skill facilitates defining these success metrics within a comprehensive PRD to track the impact of new features.

Yes, feature-spec works for documenting a new user authentication flow. It guides you through defining the login friction problem, setting goals for user experience and security, writing user stories, and specifying acceptance criteria for the flow.