skills.rest
FoundationForge
FoundationForgeOFFICIAL
Explore all skills by this author →
GitHub

write-spec

Generate a structured PRD from a problem statement or feature idea.

Updated Apr 12, 2026
Search Tags:#roadmap#prd#acceptance-criteria#stakeholders#feature-spec#product-requirements#write-spec
One-click install
npx skills add https://github.com/FoundationForge/cowork-plugins --skill write-spec-foundationforge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/FoundationForge/cowork-plugins/tree/main/plugins/product-management/skills/write-spec
Command: npx skills add https://github.com/FoundationForge/cowork-plugins --skill write-spec-foundationforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Idea and problem statements often lack the structured detail required to align stakeholders, plan work, and measure success. This Skill guides you from a vague concept to a complete PRD that captures the problem, goals, decisions, and acceptance criteria.

Core Features & Use Cases

  • Structured PRD generation: Convert a problem statement or user request into a formal PRD with sections for Problem Statement, Goals, Non-Goals, User Stories, Requirements, and Timeline.
  • Guided workflow: Collect essential context such as user problems, target users, success metrics, constraints, dependencies, and prior art to ensure a thorough specification.
  • Open questions & phased planning: Capture unresolved questions and plan phased milestones to align engineering, design, and product teams.
  • Output-ready artifacts: Produce a review-ready PRD that can be shared with stakeholders or fed into planning tools.

Quick Start

Provide a complete PRD from a feature idea to align teams and accelerate consensus.

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 feature idea into a PRD with acceptance criteria?▼

To turn a feature idea into a PRD, you provide a problem statement or user request. The tool generates a structured document containing goals, non-goals, user stories, requirements, and acceptance criteria to align stakeholders.

What sections are included in a product requirements document?▼

A product requirements document typically includes a Problem Statement, Goals, Non-Goals, User Stories, Requirements, Open Questions, and a Timeline. These sections ensure teams capture the problem, decisions, and phased planning milestones.

How to write user stories and success metrics from a vague problem statement?▼

Writing user stories and success metrics from a vague problem statement involves a guided workflow. You collect essential context like target users, constraints, dependencies, and prior art to ensure a thorough and review-ready specification.

Can I use this to plan phased milestones for engineering and design teams?▼

Yes, you can use this to plan phased milestones for engineering and design teams. The generated specification captures unresolved open questions and outlines a timeline to align cross-functional teams on delivery expectations.

Does generating a feature spec require prior technical context or dependencies?▼

Generating a feature spec does not require hard dependencies, but benefits from prior context. The guided workflow collects constraints, dependencies, and prior art to ensure the final product requirements document is comprehensive.

Related Skills

Explore More Product & Management Skills→
thepriceisrightthepriceisright

prd

Generate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.

Community
Advanced
cano721cano721

create-prd

Generate a structured Markdown PRD from guided interviews.

Community
Advanced
RDCrystalLabRDCrystalLab

prd-to-plan

Convert product requirements documents into phased implementation plans with vertical slices.

Official
Advanced
kiryteokiryteo
1

feature-spec

Draft structured PRDs with YAML frontmatter and defined templates.

Community
Advanced