aico-pm-prd-writing

name

aico-pm-prd-writing

description

Create comprehensive Product Requirements Documents (PRD) that define what to build and why, focusing on goals, scope, user stories, and success criteria without implementation details. Use this skill when: - User asks to "write a PRD", "create PRD", "write requirements document" - User mentions "requirements document", "product requirements", "product spec" - Running /pm.plan command to create version planning document - Starting a new product, major feature, or initiative that needs formal requirements - Need to document goals, scope, user stories, functional requirements, and success criteria Output: ALWAYS write PRD files to docs/reference/pm/versions/{version-name}.md

PRD Writing

⚠️ CRITICAL RULES - READ FIRST

BEFORE doing anything, you MUST:

1. CHECK EXISTING FILES:

   • Look in docs/reference/pm/versions/ directory
   • If version file already exists, READ it first and ask user if they want to update it
   • DO NOT create duplicate version files

2. ALWAYS USE THIS SKILL:

   • When user says "write PRD", "create PRD", "write requirements" → USE THIS SKILL
   • DO NOT write PRD files directly without using this skill
   • This skill ensures proper format and validation

3. ALWAYS SAVE TO CORRECT PATH:

   • Path: docs/reference/pm/versions/{version-name}.md
   • NO exceptions, NO other locations

4. READ CONSTITUTION FIRST:

   • ALWAYS read docs/reference/pm/constitution.md before writing PRD
   • Use constraints and domain info from constitution

Language Configuration

Before generating any content, check aico.json in project root for field to determine the output language. If not set, default to English.