skills.rest
nsalvacao
nsalvacaoCOMMUNITY
Explore all skills by this author →
GitHub

feature-spec

Structure product requirements documents with problem statements, goals, and acceptance criteria.

Updated Feb 9, 2026
Search Tags:#prioritization#scope#prd#user-stories#acceptance-criteria#product-requirements
One-click install
npx skills add https://github.com/nsalvacao/nsalvacao-claude-code-plugins --skill feature-spec-nsalvacao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/nsalvacao/nsalvacao-claude-code-plugins/tree/main/plugins/product-management/skills/feature-spec
Command: npx skills add https://github.com/nsalvacao/nsalvacao-claude-code-plugins --skill feature-spec-nsalvacao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write structured PRDs with problem statements, goals, and acceptance criteria to standardize product decisions and reduce ambiguity across teams.

Core Features & Use Cases

  • Provides a complete PRD template with sections: Problem Statement, Goals, Non-Goals, User Stories, Requirements, Success Metrics, Open Questions, Timeline.
  • Includes guidance and examples to help product managers craft clear, verifiable specifications.
  • Supports quick-start prompts and best practices for prioritization (MoSCoW) and decision logging.

Quick Start

Draft a new feature PRD by describing the problem, the intended user and business goals, and the acceptance criteria in a structured format.

Frequently Asked Questions about feature-spec

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

FAQPage Schema
How do I structure a product requirements document to reduce ambiguity across teams?▼

Structure your PRD using a standardized template with Problem Statement, Goals, Non-Goals, User Stories, Requirements, Success Metrics, Open Questions, and Timeline sections to standardize decisions and reduce ambiguity across teams.

What should I include in a PRD problem statement and acceptance criteria?▼

A PRD problem statement should define the specific issue being addressed, while acceptance criteria must provide clear, verifiable specifications to guide product teams in crafting outcome-driven requirements.

How do I write non-goals and user stories for a feature spec?▼

Writing non-goals for a feature spec involves explicitly stating what is out of scope for the product requirements, while user stories should capture the intended user and business goals within the structured PRD template.

What is the best way to prioritize features and requirements in a PRD?▼

The best way to prioritize features in a PRD is by applying the MoSCoW method, which categorizes product requirements into must-have, should-have, could-have, and won't-have tiers to guide clear decision logging.

Can I use this PRD template for quick-start feature spec creation?▼

Yes, you can use this PRD template for quick-start feature spec creation by describing the problem, the intended user and business goals, and the acceptance criteria in a structured format to standardize product decisions.

Related Skills

Explore More Product & Management Skills→
compozycompozy
2.5k

cy-idea-factory

Transform feature ideas into research-backed _idea.md drafts with ADRs.

Official
Advanced
ramybarsoumramybarsoum

create-tickets

Convert approved Feature Doc Section 5 use cases into engineering tickets for Linear, Jira, or text.

Community
Intermediate
tann200tann200

product-manager

Generate PRDs, user stories, and roadmaps with RICE prioritization.

Community
Intermediate
nexu-ionexu-io
84.7k

pm-spec

Generates a one-page HTML-ready product spec (PRD) with all required sections.

Official
Advanced