product-spec

Writes and audits PRDs, feature specs, and user stories through guided discovery.

39|4|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/firatcand/founder-skills --skill product-spec-firatcand
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-spec
Source: https://github.com/firatcand/founder-skills/tree/main/product-spec
Command: npx skills add https://github.com/firatcand/founder-skills --skill product-spec-firatcand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a feature idea into structured requirements that align a team is slow and error-prone; this Skill guides discovery and produces complete PRDs, feature specs, and user stories, or audits existing specs for gaps and anti-patterns. ## Core Features & Use Cases - Spec Writing Modes: Generate PRDs, feature specs, or user stories with acceptance criteria through a four-round discovery process covering problem, scope, success metrics, and behavioral detail. - Spec Audit Mode: Review an existing document against anti-pattern checklists (vague goals, happy-path-only specs, epics disguised as stories) and receive severity-rated findings with rewrite suggestions. - Story Decomposition: Break specs into INVEST-compliant user stories using splitting patterns by workflow step, CRUD operation, persona, or rollout phase. - Use Case: A founder says "spec out our self-serve billing feature" and receives a full feature spec with user flows, system states, edge cases, and testable acceptance criteria. ## Quick Start Ask the assistant to write a PRD for your next feature idea and answer its discovery questions to get a complete markdown spec document.

Frequently Asked Questions about product-spec

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

FAQPage Schema
How do I write a PRD for a new product feature?▼

Provide your feature idea and answer discovery questions about the problem, users, scope, and success metrics. The skill then generates a complete PRD in markdown with goals, personas, requirements, risks, and a rollout plan.

How to break a feature spec into user stories?▼

Share your spec and request decomposition into stories. Each story follows the INVEST model with Given/When/Then acceptance criteria, split by workflow step, CRUD operation, persona, or rollout phase when too large.

What makes a good acceptance criterion in a feature spec?▼

Good acceptance criteria are specific, measurable, and testable, typically written in Given/When/Then format. They must cover edge cases and error states, not just the happy path, so QA can derive test cases directly.

Can this skill review an existing PRD for problems?▼

Yes, audit mode evaluates an existing PRD, feature spec, or user stories against anti-pattern checklists such as vague goals, missing non-goals, and happy-path-only coverage. It returns a report with Critical, Major, and Minor severity ratings plus rewrite suggestions.

When should I write a full PRD versus a lightweight spec?▼

Depth should match ambiguity, risk, and novelty. Write a full PRD when two or more dimensions are high, such as billing or compliance work; a brief spec with annotated stories suffices for low-risk, well-understood changes.