Write Prd

Turns product ideas into structured eight-section PRDs with user stories, acceptance criteria, and go/no-go gates. Walks you through scope (full PRD, lightweight spec, or stories-only), searches memory for prior decisions, then generates a markdown file following INVEST criteria and value proposition validation. Includes a clever chain where you can pipe the output to prd-to-goal to get a runnable /goal command from your acceptance criteria. The task management setup with dependencies is unusually thorough, which means you get real progress tracking instead of a wall of text. Best for teams that need repeatable product spec processes rather than one-off documentation.

skills.sh installs: 336
GitHub stars: 301
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add yonatangross/orchestkit --skill write-prd --agent claude-code

Installs into .claude/skills of the current project.

Files

PRD — Product Requirements Document

Translate product vision and research into clear, actionable engineering specifications. Produces PRD-[product-name].md output files following an 8-section structure.

Output file naming: PRD-[product-name].md (e.g., PRD-sso-invite-flow.md)

Argument Resolution

PRODUCT = "$ARGUMENTS"  # Product name or feature, e.g., "SSO invite flow"

STEP 0: Scope Clarification

AskUserQuestion(
  questions=[{
    "question": "What type of PRD?",
    "header": "PRD Scope",
    "options": [
      {"label": "Full PRD (Recommended)", "description": "All 8 sections with research, stories, and release plan"},
      {"label": "Lightweight spec", "description": "Summary, objectives, user stories only"},
      {"label": "User stories only", "description": "INVEST stories with acceptance criteria"},
      {"label": "Update existing PRD", "description": "I have a PRD file to iterate on"}
    ],
    "multiSelect": false
  }]
)