From ork
Generates Product Requirements Documents (PRDs) using 8-section templates with user stories, INVEST criteria, acceptance criteria, and release plans. Outputs PRD-[product].md; choose full PRD, lightweight spec, stories only, or update.
How this command is triggered — by the user, by Claude, or both
Slash command
/ork:write-prdThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Auto-generated from skills/write-prd/SKILL.md # Source: https://github.com/yonatangross/orchestkit # 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 ## STEP 0: Scope Clarification \nFull PRD (8 sections)\n─────────────────────\n1. Executive Summary\n2. Problem Statement\n3. Objectives & KPIs\n4. User Stories (INVEST)\n5. Fu...
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)
PRODUCT = "$ARGUMENTS" # Product name or feature, e.g., "SSO invite flow"
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", "markdown": "```\nFull PRD (8 sections)\n─────────────────────\n1. Executive Summary\n2. Problem Statement\n3. Objectives & KPIs\n4. User Stories (INVEST)\n5. Functional Requirements\n6. Non-Functional Requirements\n7. Release Plan\n8. Appendices\n```"},
{"label": "Lightweight spec", "description": "Summary, objectives, user stories only", "markdown": "```\nLightweight Spec\n────────────────\n1. Summary (1 paragraph)\n2. Objectives (3-5 bullets)\n3. User Stories\n\nBest for: internal tools,\nsmall features, quick specs\n```"},
{"label": "User stories only", "description": "INVEST stories with acceptance criteria", "markdown": "```\nUser Stories Only\n─────────────────\nAs a [role], I want [goal]\nso that [benefit].\n\nAcceptance Criteria:\nGiven... When... Then...\n\nINVEST: Independent,\nNegotiable, Valuable,\nEstimable, Small, Testable\n```"},
{"label": "Update existing PRD", "description": "I have a PRD file to iterate on", "markdown": "```\nUpdate Existing PRD\n───────────────────\n→ Read current PRD file\n→ Identify gaps/changes\n→ Preserve approved sections\n→ Track change history\n```"}
],
"multiSelect": false
}]
)
TaskCreate(
subject="Write PRD: {PRODUCT}",
description="8-section PRD with user stories and acceptance criteria",
activeForm="Writing PRD for {PRODUCT}"
)
# Search for prior PRDs and product decisions
mcp__memory__search_nodes(query="{PRODUCT} PRD requirements")
# After PRD is written, store key decisions
mcp__memory__create_entities(entities=[{
"name": "PRD-{product-slug}",
"entityType": "document",
"observations": ["PRD written for {PRODUCT}", "Key objectives: ..."]
}])
Load Read("${CLAUDE_SKILL_DIR}/references/prd-template.md") for the full template with all 8 sections (Summary, Contacts, Background, Objective, Market Segments, Value Propositions, Solution, Release), priority levels, and NFR categories.
Load Read("${CLAUDE_SKILL_DIR}/references/user-stories-guide.md") for INVEST criteria, story format, Gherkin acceptance criteria, and Definition of Ready/Done.
Load Read("${CLAUDE_SKILL_DIR}/references/value-prop-canvas-guide.md") for the canvas template and fit check process. Every Value Map item must correspond to a Job, Pain, or Gain.
Load from rules: Read("${CLAUDE_SKILL_DIR}/rules/strategy-go-no-go.md") for stage gate criteria and scoring thresholds (Go >= 7.0 | Conditional 5.0-6.9 | No-Go < 5.0).
After generating the PRD, write it to disk:
Write(f"PRD-{product_slug}.md", prd_content)
TaskUpdate(status="completed")
After PRD is approved, chain into implementation:
/ork:implement PRD-{product-slug}.md
ork:user-research — Build user understanding (personas, journey maps, interviews) before writing the PRDork:implement — Execute the implementation plan from the PRDork:brainstorm — Explore solution alternatives before committing to PRD scopeork:assess — Rate PRD quality and completenessVersion: 2.0.0
npx claudepluginhub yonatangross/orchestkit --plugin ork/write-prdCreates a structured Product Requirements Document from a feature idea or problem statement by gathering context conversationally.
/create-prdGenerates a Product Requirements Document (PRD) from conversation context using a structured template and writes it to a specified Markdown file.
/create-prdGenerates a Product Requirements Document (PRD) from conversation context with sections for summary, users, MVP scope, stories, architecture, tech stack, and phases. Outputs to specified filename.
/write-prdWrite a complete PRD from an idea — JTBD analysis, user stories, success metrics, and a prototype-ready spec appendix, all wired to your memory