plan-review

Plan Review Skill

Evaluate research findings and decide whether to adjust upcoming stories in the PRD.

---

The Job

1. Read the research report for the current story
2. Evaluate if findings impact the current or future stories
3. Decide on plan modifications (if any)
4. Update prd.json with changes
5. Document all changes in changeLog
6. Ensure plan remains coherent and achievable

---

When to Modify the Plan

MODIFY stories when research reveals:

• A better technical approach than originally planned
• Missing prerequisite steps
• Stories that should be split (too large for one context)
• Stories that can be combined (too small, tightly coupled)
• Changed dependencies requiring reordering
• New edge cases requiring additional acceptance criteria

DO NOT modify when:

• The finding is interesting but doesn't affect implementation
• Changes would invalidate already-completed stories
• The modification is scope creep (outside original PRD goals)

---

Types of Plan Modifications

1. Modify Existing Story

Update acceptance criteria, description, or research topics.

{
  "timestamp": "2026-01-29T12:00:00Z",
  "storyId": "US-002",
  "action": "modified",
  "reason": "Research found that existing badge component supports priority colors, simplifying implementation",
  "changes": {
    "acceptanceCriteria": {
      "removed": ["Create new PriorityBadge component"],
      "added": ["Reuse Badge component with priority color variant"]
    }
  }
}

2. Add New Story

Insert a prerequisite or follow-up story.

{
  "timestamp": "2026-01-29T12:00:00Z",
  "storyId": "US-001.5",
  "action": "added",
  "reason": "Research revealed need for database index on priority column for filter performance",
  "insertAfter": "US-001"
}

3. Split Story

Break a story into smaller pieces.

{
  "timestamp": "2026-01-29T12:00:00Z",
  "storyId": "US-003",
  "action": "split",
  "reason": "Story too large - separating dropdown component from save logic",
  "splitInto": ["US-003a", "US-003b"]
}