repo-of-repos: Skill for Claude Code

Implement Plan

Execute an implementation plan from _plans/, working through each step, updating the plan as you go, and running tests to verify.

This skill combines the "implement" and "run" phases into one — you build it, run it, test it, fix it, and the plan documents everything that happened.

Arguments

The user provides the plan file to implement. For example:

• /implement-plan _plans/20260409-auth-ui.plan.md
• /implement-plan auth-ui (shorthand — resolve to the matching .plan.md file in _plans/)
• /implement-plan (no argument — if only one plan has status: draft or status: in-progress, use that)

Steps

1. Load the Plan

1. Read the plan file from _plans/
2. If the user gave a shorthand (no path or partial name), find the matching .plan.md file
3. If no argument and multiple draft/in-progress plans exist, ask the user which one
4. Parse the frontmatter and step list
5. Identify which steps are already checked (- [x]) and which are pending (- [ ])

2. Read Per-Repo Instructions

For each repo listed in the plan's repos frontmatter:

1. Check if repos/<name>/CLAUDE.md exists — if so, read and follow it
2. Check if repos/<name>/AGENTS.md exists — if so, read and follow it
3. These instructions supplement the root CLAUDE.md and govern how code is written in that repo

3. Set Status to In-Progress

Update the plan file's frontmatter:

status: in-progress

4. Implement Each Step

For each unchecked step (- [ ]), in order:

1. Read the step — understand the task, files, and pseudocode
2. Implement it — write the actual code
   • Follow the plan as guidance, not strict requirements
   • If the plan's approach won't work, adapt — but document why
   • Follow the coding standards and per-repo instructions
   • Respect read/write separation: only modify files in one repo at a time
3. Mark it done — update the plan file: change - [ ] to - [x]
4. Add notes if needed — if you discovered something unexpected, adapted the approach, or made a decision not in the original plan, add a **Notes** line under the step:

   - [x] Step 3: Add OAuth endpoint
     - **Task**: Create POST /api/auth/google
     - **Files**: `repos/backend-api/src/routes/auth.ts`
     - **Pseudocode**: Validate token, create session
     - **Notes**: Used existing session middleware instead of creating new one. Added rate limiting per security best practice.