Skill

implement

Phase 3 of the development workflow. Execute a plan step-by-step with verification. Checks for scope creep after each step. Use after /plan.

Install

npx claudepluginhub artmin96/forge-studio --plugin workflow

Tool Access

This skill is limited to using the following tools:

ReadWriteEditBashGlobGrep

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.8k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-editorial-review-prose

Reviews prose for communication issues impeding comprehension, outputs minimal fixes in a three-column table per Microsoft Writing Style Guide. Useful for 'review prose' or 'improve prose' requests.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Process

Read the plan: Check .claude/plans/ for the most recent plan

Validate before executing: Before making changes: a. Confirm all target files from the plan exist (ls or Glob) b. If the plan involves destructive/batch changes, dry-run first where possible c. If a target file doesn't exist or has changed unexpectedly, stop and update the plan

Execute step by step: For each change listed in the plan: a. Make the change b. Quick sanity check: does the file still make sense? c. Scope check: did you change ONLY what the plan specified?

Verify: Run the verification method specified in the plan

Report: Show evidence of success

Rules During Implementation

Follow the plan. If the plan is wrong, update it first — don't silently deviate.

One change at a time. Don't batch unrelated changes into a single edit.

If you discover something unexpected: stop, report it, adjust the plan.

After each step, mentally check: "Am I still within scope?"

Don't add anything the plan doesn't specify. No bonus refactoring.

After Implementation

Run the verification step from the plan. Show output.

IMPLEMENTATION COMPLETE ======================= Plan: {plan name} Steps completed: {X}/{Y} Verification: {PASS/FAIL} Evidence: {one-line summary of proof}

If verification fails: diagnose, fix, re-verify. Don't mark done until it passes. If the plan was wrong: note what was different and why.

Implement: Execute the Plan

Phase 3 of the Explore → Plan → Implement → Verify workflow.

Process

Read the plan: Check .claude/plans/ for the most recent plan
Validate before executing: Before making changes: a. Confirm all target files from the plan exist (ls or Glob) b. If the plan involves destructive/batch changes, dry-run first where possible c. If a target file doesn't exist or has changed unexpectedly, stop and update the plan
Execute step by step: For each change listed in the plan: a. Make the change b. Quick sanity check: does the file still make sense? c. Scope check: did you change ONLY what the plan specified?
Verify: Run the verification method specified in the plan
Report: Show evidence of success

Rules During Implementation

Follow the plan. If the plan is wrong, update it first — don't silently deviate.
One change at a time. Don't batch unrelated changes into a single edit.
If you discover something unexpected: stop, report it, adjust the plan.
After each step, mentally check: "Am I still within scope?"
Don't add anything the plan doesn't specify. No bonus refactoring.

After Implementation

Run the verification step from the plan. Show output.

IMPLEMENTATION COMPLETE
=======================
Plan: {plan name}
Steps completed: {X}/{Y}
Verification: {PASS/FAIL}
Evidence: {one-line summary of proof}

If verification fails: diagnose, fix, re-verify. Don't mark done until it passes. If the plan was wrong: note what was different and why.