spec

Generate a structured PRD with requirements, user stories, and acceptance criteria.

Updated Aug 23, 2026

Search Tags:#documentation #prd #user-stories #acceptance-criteria #product-requirements #requirements-engineering

Ready to run

npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill spec-gudzenkov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/gudzenkov/SuperClaudeZero/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill spec-gudzenkov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a clear, structured Product Requirements Document from a vague idea or feature request, helping teams align on goals, scope, and success criteria.

Core Features & Use Cases

Structured PRD generation: formalizes goals, non-goals, functional and non-functional requirements, user stories, and acceptance criteria.
Context-aware documentation: cross-references existing docs (PRD, vision) to ensure consistency.
Iterative refinement: supports clarifying questions and incremental updates as details evolve.

Quick Start

Provide your idea or feature description to generate the PRD.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I generate a PRD from a vague feature idea?▼

To generate a PRD from a feature idea, provide your concept to receive a structured document enforcing goals, non-goals, functional requirements, user stories, and acceptance criteria. This formalizes your initial concept into clear documentation.

What is the best way to structure user stories and acceptance criteria for product requirements?▼

Structuring user stories and acceptance criteria requires organizing them alongside functional and non-functional requirements within a PRD. This ensures clear scope boundaries and validation metrics for product teams.

Can I update an existing PRD with new product requirements as details evolve?▼

Yes, you can update existing product requirements through iterative refinement. The skill supports clarifying questions and incremental updates to cross-reference existing docs, ensuring consistency as your project details evolve.

Does PRD generation work without predefined functional and non-functional requirements?▼

Yes, PRD generation works from a basic idea or feature request without predefined functional or non-functional requirements. It automatically formalizes these constraints, goals, and non-goals during the documentation workflow.

When do I need to define non-goals in a Product Requirements Document?▼

You need to define non-goals in a Product Requirements Document to establish strict scope boundaries and prevent feature creep. Setting non-goals explicitly clarifies what functionality is excluded from the current product requirements.