prd-breakdown

PRD Breakdown - Analyze and Decompose Product Requirements

Analyze a Product Requirements Document (PRD) and decompose it into atomic features that integrate with the claude-harness workflow.

Arguments: $ARGUMENTS

Phase 0: PRD Input Detection & Storage

1. Detect PRD source (in priority order):

   • If arguments start with @ -> treat as file reference (e.g., @./docs/prd.md)
   • Else if --url flag provided -> fetch from GitHub issue
   • Else if --file flag provided -> read from specified file path
   • Else if file ./.claude-harness/prd.md exists -> read from file
   • Else if arguments provided -> treat as inline PRD markdown
   • Else -> prompt user for interactive input

2. Validate PRD format:

   • Check minimum length (at least 100 characters of content)
   • If Markdown: verify structure (sections, requirements)
   • If plain text: parse as-is
   • If too large (>100KB): warn user, ask to focus on specific sections

3. Store PRD input:

   • Create .claude-harness/prd/ directory if missing
   • Save PRD content to .claude-harness/prd/input.md
   • Create .claude-harness/prd/metadata.json:

     {
       "version": 1,
       "sourceType": "inline|file|github|interactive",
       "fetchedAt": "{ISO timestamp}",
       "sourceUrl": "{URL or path}",
       "hash": "{SHA256 of PRD}",
       "characterCount": 0,
       "sections": 0
     }
     

Phase 1: PRD Analysis

Perform comprehensive analysis from three perspectives:

1. Product Analysis:

   • Extract business goals, user personas, functional requirements
   • Identify non-functional requirements, dependencies, constraints

2. Architecture Analysis:

   • Review feasibility and technical complexity
   • Propose implementation order (dependency graph)
   • Identify risks and mitigations
   • Suggest MVP features

3. QA Analysis:

   • Define acceptance criteria for each requirement
   • Identify edge cases and error scenarios
   • Specify performance/security requirements