mcpField
I
implement-plan

implement-plan

github.com/casper-studiosAgent workflows15267 installsUpdated 1d ago
Repository

About implement-plan

A skill for implementing approved technical plans stored in `.claude/scratchpad/`. It guides coding agents through reviewing context, completing plan phases, tracking progress, and handling mismatches.

Key features

  1. 01Read plans and referenced files
  2. 02Track implementation with todos
  3. 03Complete phases and verify changes
  4. 04Update plan checkboxes
  5. 05Surface plan mismatches

Use cases

  1. 01Implementing an approved multi-phase plan
  2. 02Resuming work from checked-off plan items
  3. 03Resolving differences between a plan and codebase

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/casper-studios/casper-marketplace --skill implement-plan

After installing, type/implement-planin Claude Code to confirm it loaded.

Details

From the project README

Implement Plan

You are tasked with implementing an approved technical plan from .claude/scratchpad/{plan_name}.md. These plans contain phases with specific changes and success criteria. If no file is provided, ask for one.

Getting Started

When given a plan path:

  • Read the plan completely and check for any existing checkmarks (- [x])
  • Read the original ticket and all files mentioned in the plan
  • Read files fully - never use limit/offset parameters, you need complete context
  • Think deeply about how the pieces fit together
  • Create a todo list to track your progress
  • Start implementing if you understand what needs to be done

If no plan path provided, ask for one.

Implementation Philosophy

Plans are carefully designed, but reality can be messy. Your job is to:

  • Follow the plan's intent while adapting to what you find
  • Implement each phase fully before moving to the next
  • Verify your work makes sense in the broader codebase context
  • Update checkboxes in the plan as you complete sections

When things don't match the plan exactly, think about why and communicate clearly. The plan is your guide, but your judgment matters too.

If you encounter a mismatch:

  • STOP and think deeply about why the plan can't be followed

  • Present the issue clearly:

    Issue in Phase [N]:
Expected: [what the plan says]
Found: [actual situation]
Why this matters: [explanation]

How should I proceed?

Verification Approach

After implementing a phase:

  • Fix any issues before proceeding
  • Update your progress in both the plan and your todos
  • Check off completed items in the plan file itself using Edit

Don't let verification interrupt your flow - batch it at natural stopping points.

If You Get Stuck

When something isn't working as expected:

  • First, make sure you've read and understood all the relevant code
  • Consider if the codebase has evolved since the plan was written
  • Present the mismatch clearly and ask for guidance

Use sub-tasks sparingly - mainly for targeted debugging or exploring unfamiliar territory.

Resuming Work

If the plan has existing checkmarks:

  • Trust that completed work is done
  • Pick up from the first unchecked item
  • Verify previous work only if something seems off

Remember: You're implementing a solution, not just checking boxes. Keep the end goal in mind and maintain forward momentum.

Comments

Markdown supported