write-spec

Convert vague feature ideas into structured PRDs with goals and acceptance criteria.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/cy-wali/knowledge --skill write-spec-cy-wali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/cy-wali/knowledge/tree/main/product-management/skills/write-spec
Command: npx skills add https://github.com/cy-wali/knowledge --skill write-spec-cy-wali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning vague ideas, feature requests, or problem statements into structured PRDs that define goals, scope, success metrics, and acceptance criteria, so teams can align and execute with clarity.

Core Features & Use Cases

  • Structured PRDs: Generate problem statements, goals, non-goals, user stories, requirements, and success metrics in a single document.
  • Phased specs & open questions: Organize work into phases and capture unresolved questions for cross-functional teams.
  • Use Case Scenarios: Provide concrete examples to illustrate scope and impact for stakeholders.

Quick Start

Provide a problem statement and any constraints, and I will 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 feature idea into a structured PRD?

To turn a vague feature idea into a structured PRD, you provide a problem statement and any constraints to generate a complete document with defined goals, success metrics, and acceptance criteria.

What is the best way to write user stories and requirements for stakeholders?

The best way to write user stories and requirements for stakeholders is to organize them into phased specs with concrete use case scenarios, ensuring clear scope, non-goals, and testable outcomes.

How do I prioritize requirements using Must-Have, Should-Have, and P2 categories?

Prioritizing requirements using Must-Have, Should-Have, and P2 categories involves structuring your phased specs to separate critical features from secondary ones, defining clear scope for execution.

Can I capture open questions and unresolved constraints in a product spec?

Yes, you can capture open questions and unresolved constraints in a product spec by organizing them alongside user stories and requirements, which helps cross-functional teams align on unresolved issues.

How do I define success metrics and acceptance criteria for a roadmap?

Defining success metrics and acceptance criteria for a roadmap requires converting problem statements into structured PRDs that establish testable outcomes and measurable goals before execution begins.