feature-spec

Generate structured PRDs with problem statements, user stories, and success metrics.

2|1|Updated Apr 3, 2026

Search Tags:#prd #user-stories #acceptance-criteria #feature-spec #moscow #success-metrics

Ready to run

npx skills add https://github.com/GACLove/feishu-aily-skills --skill feature-spec-gaclove

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/GACLove/feishu-aily-skills/tree/main/skills/feature-spec
Command: npx skills add https://github.com/GACLove/feishu-aily-skills --skill feature-spec-gaclove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to create comprehensive, structured product requirement documents that capture problem statements, goals, user stories, and measurable success criteria.

Core Features & Use Cases

Template-driven PRD creation: Provides a clear outline covering problem statements, goals, non-goals, user stories, requirements (P0/P1/P2), success metrics, and timeline considerations.
Guidance for user story quality: Enforces INVEST principles and offers examples to avoid common pitfalls.
Scope management tools: Includes MoSCoW and non-goal sections to prevent scope creep.
Use Case: When a product manager needs to define a new feature, they can invoke this skill to generate a full PRD ready for stakeholder review.

Quick Start

Ask the skill to generate a PRD for a new feature, specifying the problem statement, goals, and user stories in a single request.

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

A PRD captures problem statements, goals, user stories, and success metrics. Using a template ensures your product requirement document remains comprehensive, testable, and measurable for stakeholder review.

What is the best way to write user stories for product development?▼

Writing user stories requires applying INVEST principles to avoid common pitfalls. This framework ensures each story is independent, negotiable, valuable, estimable, small, and testable for product development.

How do I use MoSCoW prioritization to manage scope creep?▼

MoSCoW prioritization prevents scope creep by categorizing requirements into Must-have, Should-have, Could-have, and Won't-have groups. Defining explicit non-goals further clarifies feature scope boundaries.

How do I define success metrics and acceptance criteria for a PRD?▼

Success metrics and acceptance criteria require establishing measurable definitions for your goals. Clear metric definitions ensure your specifications are testable and verifiable throughout product development.

Can I generate acceptance criteria and P0/P1/P2 requirements automatically?▼

Generating acceptance criteria and P0/P1/P2 requirements is possible by applying template-driven PRD creation. Providing problem statements and goals yields categorized, testable specifications instantly.