product-spec-builder

Generates Product-Spec.md documents through phased requirement interviews and iteration workflows.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill product-spec-builder-lygolang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-spec-builder
Source: https://github.com/LYGOLANG/fufan-cc-flow/tree/main/.agents/skills/product-spec-builder
Command: npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill product-spec-builder-lygolang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a vague product idea into a development-ready specification is hard: founders describe solutions instead of problems, skip scope decisions, and leave AI features undefined. This Skill runs a disciplined, phased interview that forces concrete answers and produces a complete Product-Spec.md an engineer can build from directly. ## Core Features & Use Cases - 0-1 Mode: When no spec exists, it runs a seven-phase interview (problem & users, job & success, scope & non-goals, journeys & features, AI capabilities, UI states, acceptance criteria) and generates a structured Product-Spec.md with numbered TASK/FLOW/REQ items. - Iteration Mode: When a Product-Spec.md already exists, it interviews about the change, detects conflicts with the existing spec, updates the document, and appends a versioned changelog entry. - AI Capability Planning: Every AI feature gets a quality bar, trigger mode, fallback behavior, and explicit guardrails; agent products get an additional autonomy, tooling, eval, and cost specification section. - Use Case: A founder says "I want to build an AI video tool." The Skill searches current competitors, challenges vague answers ("everyone will use it"), pins down one target user and three explicit non-goals, then outputs a spec with Given-When-Then acceptance criteria. ## Quick Start Tell the assistant "I want to build a product that does X" and it will start interviewing you phase by phase until it can generate your Product-Spec.md.

Frequently Asked Questions about product-spec-builder

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

FAQPage Schema
How do I turn a product idea into a product requirements document?▼

Describe your product idea and the Skill runs a phased interview covering problem, target user, scope, user journeys, features, AI capabilities, UI states, and acceptance criteria. It then generates a Product-Spec.md with numbered requirements an engineer can implement directly.

How do I update an existing product spec when requirements change?▼

State the change you want and the Skill enters iteration mode: it asks follow-up questions sized to the change's impact, checks for conflicts with the existing spec, updates only the affected sections, and appends a versioned entry to Product-Spec-CHANGELOG.md.

What makes this different from writing a PRD from a template?▼

It enforces interview discipline: vague answers like "make it simple" get challenged until they become concrete instances, numbers, or observable facts. It also requires at least three explicit non-goals and Given-When-Then acceptance criteria before generating the document.

Does it handle AI features and agent products in the spec?▼

Yes. Every AI feature must define a quality threshold, trigger mode, uncertainty behavior, and degradation strategy, plus explicit guardrails. Agent products get an extra section covering autonomy levels, tool permissions, context management, evaluation, cost limits, and failure handling.

When should I not use a full spec interview process?▼

Skip it for trivial changes like copy or style tweaks, which the iteration mode handles with minimal questioning. It is also not suited for operational decisions like pricing, growth, or launch timing, which the Skill deliberately leaves to the user.