skills.rest
hiroshi75
hiroshi75COMMUNITY
Explore all skills by this author →
GitHub

feature-spec

Generate structured PRDs with problem statements, user stories, and Given/When/Then acceptance criteria.

Updated Mar 13, 2026
Search Tags:#product management#acceptance criteria#PRD#feature specification#requirements gathering#user stories
One-click install
npx skills add https://github.com/hiroshi75/agentlattice --skill feature-spec-hiroshi75
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/hiroshi75/agentlattice/tree/main/templates/skills/product-management/feature-spec
Command: npx skills add https://github.com/hiroshi75/agentlattice --skill feature-spec-hiroshi75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of Product Requirements Documents (PRDs) and feature specifications, ensuring clarity on what to build, why, and how to measure success.

Core Features & Use Cases

  • Structured PRD Generation: Creates comprehensive PRDs including problem statements, goals, user stories, requirements, and success metrics.
  • Acceptance Criteria Definition: Formulates clear, testable acceptance criteria using Given/When/Then format or checklists.
  • Scope Management Guidance: Provides strategies to prevent scope creep and manage feature additions effectively.
  • Use Case: A product manager needs to define a new user authentication feature. This Skill will guide them through documenting the problem of insecure logins, defining goals for improved security and user experience, outlining user stories for sign-up and login, specifying requirements, and setting success metrics like reduced password reset requests.

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?▼

Writing a product requirements document (PRD) involves defining problem statements, goals, user stories, requirements, and success metrics to ensure clarity on what to build and how to measure success.

What is the Given/When/Then format for acceptance criteria?▼

The Given/When/Then format structures acceptance criteria by defining a starting context, an action, and an expected outcome, ensuring feature requirements are clear and testable.

How do I structure user stories and success metrics in a PRD?▼

Structuring user stories and success metrics in a PRD involves defining target user needs and mapping them to measurable goals, like reduced password resets, to effectively guide product development.

What is the best way to manage scope creep when defining feature specifications?▼

The best way to manage scope creep when defining feature specifications is to use structured PRDs that establish strict boundaries and clear acceptance criteria to prevent uncontrolled feature additions.

Can I generate a feature specification for a user authentication flow without prior PRD experience?▼

Yes, you can generate a feature specification for a user authentication flow without prior experience, as the process guides you through documenting problems, defining goals, and outlining user stories.

Related Skills

Explore More Product & Management Skills→
me2reshme2resh
489

write-spec

Convert feature ideas into structured PRDs with problem statements and requirements.

Community
Intermediate
JochenYangJochenYang
21

product-manager

Generate structured PRDs and user stories with acceptance criteria.

Community
Intermediate
deltatreedeltatree

bmad-dev-story

Execute software development stories from markdown specifications with red-green-refactor cycles.

Community
Advanced
decebaldecebal

ralph-tui-prd

Generate structured PRDs with user stories and acceptance criteria.

Community
Advanced