feature-spec

Name: feature-spec
Availability: InStock
Author: chelleboyer

Generate structured PRDs and feature specifications from a PRD template.

Updated Jan 11, 2026

Search Tags:#documentation #requirements #prd #product-management #user-stories #acceptance-criteria #feature-spec

Ready to run

npx skills add https://github.com/chelleboyer/reachy_mini_retail_assistant --skill feature-spec-chelleboyer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/chelleboyer/reachy_mini_retail_assistant/tree/main/skills/product-management/skills/feature-spec
Command: npx skills add https://github.com/chelleboyer/reachy_mini_retail_assistant --skill feature-spec-chelleboyer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to align stakeholders and engineers around a clear problem statement, measurable goals, and a shared understanding of success.

Core Features & Use Cases

Structured PRD templates: Provides sections for problem, goals, non-goals, user stories, and acceptance criteria.
Decision traceability: Captures non-goals, open questions, dependencies, and timeline assumptions.
Guided quick start: A reproducible starting prompt to generate a complete PRD from minimal input.

Quick Start

Create a complete PRD by providing the problem statement, goals, non-goals, user stories, acceptance criteria, and success metrics.

Frequently Asked Questions about feature-spec

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

FAQPage Schema

What is a PRD and what sections should it include for feature specification?▼

A PRD is a structured document for aligning stakeholders and engineers. It should include problem statements, goals, non-goals, user stories, acceptance criteria, success metrics, open questions, and timeline considerations.

How do I write a PRD from minimal input?▼

Write a PRD by providing a basic problem statement, goals, non-goals, user stories, acceptance criteria, and success metrics. This guided quick start generates a complete PRD from minimal input.

What's the best way to document non-goals and open questions during product scoping?▼

The best way to document non-goals and open questions is using a structured feature spec template. This ensures decision traceability by capturing dependencies, open questions, and timeline assumptions.

Can I use a PRD template for prioritizing requirements and scoping new features?▼

Yes, you can use a structured PRD template for scoping new features and prioritizing requirements. It documents decisions for product teams and provides sections for user stories and acceptance criteria.

Does a feature spec require success metrics and acceptance criteria?▼

Yes, a feature spec requires success metrics and acceptance criteria. These sections establish a shared understanding of success and align engineers around measurable goals.