feature-spec

Generate structured product requirements documents with problem statements, user stories, and acceptance criteria.

Updated Mar 5, 2026

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

Ready to run

npx skills add https://github.com/8GG-Git/knowledge-work-plugins --skill feature-spec-8gg-git

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/8GG-Git/knowledge-work-plugins/tree/main/product-management/skills/feature-spec
Command: npx skills add https://github.com/8GG-Git/knowledge-work-plugins --skill feature-spec-8gg-git

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 problems, goals, user stories, and success metrics for new features.

Core Features & Use Cases

PRD Structuring: Guides users through defining problem statements, goals, non-goals, user stories, requirements, and success metrics.
Requirement Definition: Helps categorize requirements into Must-Have, Nice-to-Have, and Future Considerations.
Use Case: A product manager needs to define a new user authentication flow. They use this Skill to document the problem of current login friction, define goals for improved user experience and security, write user stories for different user types, and specify acceptance criteria for the new flow.

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 a product requirements document for a new feature?▼

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.

What should be included in acceptance criteria for user stories?▼

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.

How do I define non-goals to prevent scope creep in a PRD?▼

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.

Can I use this to write user stories for different user types?▼

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.

What is the best way to structure success metrics for feature development?▼

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.

Does feature-spec work for documenting a new user authentication flow?▼

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.