create-plan

Implementation Plan

You are tasked with creating detailed, vertical implementation plans from an approved design document. The design decisions are already made — your job is to translate them into actionable phases.

Mark the herdr phase

As your very first action, tag this agent's herdr tab so the session navigator shows the workflow phase (safe no-op outside herdr):

bash "$(git rev-parse --show-toplevel)/.claude/scripts/herdr-phase.sh" plan

Initial Response

When this command is invoked:

1. Check if parameters were provided:

   • If a design doc path was provided as $ARGUMENTS, read it FULLY
   • Also check for and read any referenced research docs or tickets
   • Begin the planning process

2. If no parameters provided, respond with:

   I'll help you create an implementation plan. Please provide:
   1. The design document (from /design-doc) — required
   2. Optionally, the research doc or ticket reference
   
   Tip: /create-plan .rpi/design-2026-01-05-auth-redesign.md
   

   Then wait for the user's input.

Process

Step 1: Context Gathering

1. Read the design document FULLY — this is your primary input
2. Read any concrete reference artifact it links — an HTML mockup, a schema diff, example request/response payloads. These are the spec; prefer them over the prose describing them.
3. Read any referenced research docs and tickets
4. Spawn focused research agents if needed:
   • Use codebase-locator to find specific files referenced in the design
   • Use codebase-analyzer to understand implementation details needed for planning
   • Only research what the design doc doesn't already cover
5. Read all files identified by research agents

Step 2: Create Plan Outline

Present a high-level outline of vertical phases before writing the full plan:

Based on the design document, here's my proposed phasing:

Phase 1: [Name] — [What it accomplishes end-to-end]
  Testing: [How this phase will be verified]

Phase 2: [Name] — [What it accomplishes end-to-end]
  Testing: [How this phase will be verified]

Phase 3: [Name] — [What it accomplishes end-to-end]
  Testing: [How this phase will be verified]

Files by phase:
src/
├── routes/dashboard/+page.svelte       # P1, P3
├── lib/server/jobs/metrics.ts          # P2
└── routes/dashboard/+page.server.ts    # P3

Does this phasing make sense? Should I adjust?