Run

# /karimo:run — Execute PRD (Recommended)

Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.

## Usage

```bash
/karimo:run --prd {slug} [--dry-run] [--skip-review] [--review-only] [--brief-only] [--resume] [--task {id}]

Arguments

• --prd {slug} (required): The PRD slug to execute
• --dry-run (optional): Preview the execution plan without making changes
• --skip-review (optional): Skip brief review and execute immediately
• --review-only (optional): Generate briefs and review, stop without executing
• --brief-only (optional): Generate briefs only, stop before review
• --resume (optional): Resume execution after pausing
• --task {id} (optional): Execute only a specific task by ID

What This Command Does (4 Phases)

KARIMO v7.0 introduces a 4-phase execution model with user iteration:

┌─────────────────────────────────────────────────────────────┐
│  Phase 1: Brief Generation                                  │
│    Read research + PRD → Generate task briefs               │
└─────────────────────────────────────────────────────────────┘
                           │
                           ↓
┌─────────────────────────────────────────────────────────────┐
│  Phase 2: Auto-Review                                       │
│    Validate briefs → Challenge order/deps → Find gaps       │
└─────────────────────────────────────────────────────────────┘
                           │
                           ↓
┌─────────────────────────────────────────────────────────────┐
│  Phase 3: User Iterate                                      │
│    Present recommendations → User feedback → Adjust briefs  │
│                    ↺ (loop until approved)                  │
└─────────────────────────────────────────────────────────────┘
                           │
                           ↓
┌─────────────────────────────────────────────────────────────┐
│  Phase 4: Orchestrate                                       │
│    Execute tasks in waves → Create PRs → Validate           │
└─────────────────────────────────────────────────────────────┘

---

Phase 1: Brief Generation

1. Load Research Context

   • Read research findings from .karimo/prds/{NNN}_{slug}/research/findings.md
   • If missing: Warning but continue (legacy PRDs)

2. Load PRD

   • Read PRD from .karimo/prds/{NNN}_{slug}/PRD_{slug}.md
   • Load tasks from tasks.yaml

3. Generate Task Briefs

   • Spawn karimo-brief-writer agent
   • Generate briefs: .karimo/prds/{NNN}_{slug}/briefs/*.md
   • Each brief inherits research context

4. Commit Briefs

   git add .karimo/prds/{NNN}_{slug}/briefs/
   git commit -m "docs(karimo): generate task briefs for {slug}
   
   Generated {count} briefs with research context.
   
   Co-Authored-By: Claude <noreply@anthropic.com>"
   

---

Phase 2: Auto-Review

1. Spawn Brief-Reviewer Agent

   @karimo-brief-reviewer.md
   

2. Challenge Briefs

   • Task order makes sense?
   • Dependencies correctly specified?
   • File boundaries respected?
   • Gaps in coverage?
   • Conflicts between tasks?

3. Generate Recommendations

   • Create recommendations.md with findings
   • Categorize: Critical, Warning, Observation
   • Include suggested fixes

4. Commit Review Findings

   git add .karimo/prds/{NNN}_{slug}/recommendations.md
   git commit -m "docs(karimo): brief review findings for {slug}
   
   Critical: {n} | Warnings: {n} | Observations: {n}
   
   Co-Authored-By: Claude <noreply@anthropic.com>"
   

---

Phase 3: User Iterate

Present findings and allow user iteration:

╭──────────────────────────────────────────────────────────────╮
│  Brief Review Complete: {slug}                               │
╰──────────────────────────────────────────────────────────────╯

Generated {count} task briefs.

┌─────────────────────────────────────────────────────────────┐
│  Recommendations                                             │
├─────────────────────────────────────────────────────────────┤
│                                                              │
│  ⚠️  Critical ({n}):                                        │
│      • Task T002 should run before T001 (dependency issue)  │
│      • Task T004 references non-existent file               │
│                                                              │
│  ⚡ Warnings ({n}):                                         │
│      • Task T003 complexity may be underestimated           │
│                                                              │
│  ℹ️  Observations ({n}):                                    │
│      • Consider adding test for edge case X                 │
│                                                              │
└─────────────────────────────────────────────────────────────┘

Options:
  1. Approve — Execute tasks as-is
  2. Apply fixes — Auto-correct critical issues, then execute
  3. Modify — Adjust briefs manually (opens editor)
  4. More research — Need additional context
  5. Cancel — Exit without executing

Your choice:

Option 1 — Approve:

• Proceed to Phase 4 (Orchestrate)

Option 2 — Apply fixes:

• Spawn karimo-brief-corrector to apply fixes

• Commit corrections:

  git add .karimo/prds/{NNN}_{slug}/briefs/ .karimo/prds/{NNN}_{slug}/tasks.yaml
  git commit -m "docs(karimo): apply brief corrections for {slug}
  
  Applied {n} critical fixes from review.
  
  Co-Authored-By: Claude <noreply@anthropic.com>"
  

• Proceed to Phase 4 (Orchestrate)

Option 3 — Modify:

• Accept user input for changes
• Regenerate affected briefs
• Loop back to Phase 2 (Auto-Review)

Option 4 — More research:

• Print: "Run /karimo:research --prd {slug} to add research context"
• Note: "Resume with /karimo:run --prd {slug} --resume after research completes"

Option 5 — Cancel:

• Exit withou