write-spec

Name: write-spec
Availability: InStock
Author: clawpod-app

Generate a structured PRD from a vague idea or user request.

46|11|Updated Mar 29, 2026

Search Tags:#specification #prd #product-management #user-stories #acceptance-criteria #write-spec

Ready to run

npx skills add https://github.com/clawpod-app/awesome-openclaw-agent-packs --skill write-spec-clawpod-app

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/clawpod-app/awesome-openclaw-agent-packs/tree/main/packs/product-management/skills/write-spec
Command: npx skills add https://github.com/clawpod-app/awesome-openclaw-agent-packs --skill write-spec-clawpod-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product teams convert vague ideas or user requests into a structured PRD, reducing back-and-forth and misalignment.

Core Features & Use Cases

Generate a Problem Statement, Goals, Non-Goals, User Stories, Requirements, Open Questions, and Timeline.
Break down a feature idea into acceptance criteria and success metrics.
Example: convert a one-line idea into a full PRD ready for stakeholder review.

Quick Start

Describe your feature idea or problem statement to generate a complete PRD.

Frequently Asked Questions about write-spec

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

FAQPage Schema

How do I turn a vague product idea into a structured PRD?▼

To turn a vague idea into a structured PRD, describe your feature concept to generate a document containing a Problem Statement, Goals, Non-Goals, User Stories, and Requirements. This breaks down ambiguous requests into clear stakeholder-ready specifications.

What should be included in a product requirement document for user stories?▼

A product requirement document should include User Stories, acceptance criteria, and success metrics. It breaks down feature ideas into actionable items with clear P0/P1/P2 requirements, Open Questions, and a Timeline to ensure alignment.

How do I write acceptance criteria and success metrics for a feature?▼

You write acceptance criteria and success metrics by breaking down your feature idea into specific user stories and prioritized requirements. This process converts a one-line concept into measurable goals and clear boundaries for development teams.

Can I generate non-goals and open questions for my product specification?▼

Yes, you can generate non-goals and open questions for your product specification. The PRD explicitly structures these sections alongside the Problem Statement and Timeline to prevent scope creep and highlight unresolved stakeholder queries.

What is the best way to break down a one-line idea into stakeholder-ready PRDs?▼

The best way to break down a one-line idea is to process the concept into a full PRD with Problem Statements, Goals, and prioritized P0/P1/P2 Requirements. This reduces back-and-forth misalignment by converting vague thoughts into structured documents.

How do I structure feature timelines and prioritized requirements in product management?▼

You structure feature timelines and prioritized requirements by categorizing deliverables into P0, P1, and P2 tiers. The generated PRD maps these requirements directly against a clear Timeline to guide development sequencing and stakeholder reviews.