skills.rest
iJosueeh
iJosueehCOMMUNITY
Explore all skills by this author →
GitHub

product-spec-builder

Generates Product-Spec.md requirements documents through structured Socratic requirement interviews.

Updated Jun 29, 2026
Search Tags:#specification#product management#requirements gathering#prd#product spec#scope validation#socratic interview
One-click install
npx skills add https://github.com/iJosueeh/amauta --skill product-spec-builder-ijosueeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-spec-builder
Source: https://github.com/iJosueeh/amauta/tree/main/.opencode/skills/product-spec-builder
Command: npx skills add https://github.com/iJosueeh/amauta --skill product-spec-builder-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a vague product idea into an implementable requirements document is hard: users give fuzzy answers, scope creeps silently, and developers start coding before requirements are confirmed. This Skill runs a structured interview workflow that produces a complete, validated Product-Spec.md before any code is written. ## Core Features & Use Cases - Multi-mode requirement gathering: Routes between Quick Mode, 0-to-1 deep-dive, Iteration Mode (updating an existing Spec with changelog), Light Grill alignment, and Distillation Mode that infers needs from a one-line idea. - Quality gates before writing: Multi-Stakeholder Review (business, technical, experience, scope lenses) and an adversarial Critique Gate that surfaces hidden assumptions, unchallenged decisions, and scope to cut. - HARD-GATE enforcement: Blocks development planning and source-code edits until Product-Spec.md is saved and explicitly confirmed by the user. - Use Case: A founder says "I want to build an offline attendance app for rural teachers." The Skill interviews them on users, flows, AI capabilities, and platform, runs stakeholder and critique passes, then outputs a Product-Spec.md with use cases, functional requirements, UI layout, and technical direction. ## Quick Start Tell the agent "I want to build a product" followed by your idea, or run /product-spec-builder with a short description of the app or feature you want to specify.

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 requirements document with AI?▼

Describe your idea to the product-spec-builder skill and it interviews you across positioning, target users, core features, user flows, and AI capabilities. It then generates a Product-Spec.md following a structured template with use cases, functional requirements, UI layout, and technical direction.

What is the difference between Quick Mode and 0-to-1 Mode?▼

Quick Mode handles one-sentence ideas with a lightweight path and sensible defaults. 0-to-1 Mode runs the full pipeline: exploration, clarifying questions, refinement, multi-stakeholder review, critique gate, then document generation with at least three validation cycles.

Can I update an existing Product-Spec.md when requirements change?▼

Yes. Iteration Mode detects an existing Product-Spec.md, interviews you about the change, checks for conflicts with the current spec, updates the file, and appends a versioned entry to Product-Spec-CHANGELOG.md.

Why does the skill block coding until the spec is confirmed?▼

The HARD-GATE prevents building on unvalidated assumptions. Until Product-Spec.md is saved and explicitly confirmed, the skill refuses to invoke development planners or edit application source code, since chat-level agreement is not treated as confirmation.

What is the Critique Gate and when does it run?▼

The Critique Gate is an adversarial review that scans for hidden assumptions, unchallenged decisions, and scope that should be cut. It runs by default in 0-to-1 mode after stakeholder review, requires at least three evidence-backed findings, and is skipped in Quick and Iteration modes.

When should I use Distillation Mode instead of the interview?▼

Use Distillation Mode when you only have a vague one-line idea and want the AI to infer needs rather than answer questions. It runs four inference paths (real need, competitors, domain patterns, feasibility) and outputs a Distillation Map marking items confirmed, inferred, or needing your confirmation.

Related Skills

Explore More Product & Management Skills→
lalulalilalulali
8

explore-idea

Synthesize a concept brief and coordinate market, competitor, and user research.

Community
Advanced
sirius-cc-wusirius-cc-wu
3

plan

Convert spec.md into a phase-based plan.md with milestones and verification steps.

Community
Intermediate
iJosueehiJosueeh

change-manager

Orchestrates scoped brownfield changes through propose, apply, verify, and archive phases.

Community
Advanced
statsclawstatsclaw
89

simplified-workflow

Run a 4-step pipeline for small routine code changes.

Official
Intermediate