plan

User Input

$ARGUMENTS

You MUST parse the user input to extract the feature slug (the folder name in rpi/).

Purpose

This command creates comprehensive planning documentation for a feature request. It generates detailed specifications, technical design, and implementation plans in the feature's RPI folder.

Prerequisites:

• Feature folder exists at rpi/{feature-slug}/
• Research completed with GO recommendation (rpi/{feature-slug}/research/RESEARCH.md exists)

Output Location: All files saved to rpi/{feature-slug}/plan/

This is Step 3 of the RPI Workflow (after Research approves with GO).

Outline

1. Load Context: Read research report and project constitution (if exists)
2. Understand Requirements: Parse feature scope and requirements
3. Analyze Technical Requirements: Review architecture and dependencies
4. Design Architecture: Create high-level architecture and API contracts
5. Break Down Implementation: Create phased task breakdown
6. Generate Documentation: Create structured documentation files
7. Validate Output: Ensure all quality gates pass
8. Report Completion: Provide summary and next steps

Phases

Phase 0: Load Context

Prerequisites: Feature slug provided

Process:

1. Verify research completed:

   • Check rpi/{feature-slug}/research/RESEARCH.md exists
   • Verify GO recommendation (warn if NO-GO or CONDITIONAL)

2. Read research findings:

   • Extract product analysis
   • Extract technical discovery
   • Extract technical feasibility assessment
   • Note risks and constraints

3. Load project constitution (if exists):

   • Look for a constitution or principles document in the repository
   • Extract relevant constraints and preferences

Outputs:

• Research summary
• Constitutional context (if found)
• Planning constraints

Validation:

• Research report exists
• GO recommendation confirmed
• Constitution loaded (if exists)

---