From workflow
Phase 2 of the development workflow. Create an implementation plan based on exploration. Lists exact files, changes, risks, and verification method. Use after /explore.
npx claudepluginhub artmin96/forge-studio --plugin workflowThis skill is limited to using the following tools:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
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.
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.
Phase 2 of the Explore → Plan → Implement → Verify workflow. From Anthropic: "Planning is most useful for uncertain approach, changes across many files, or unfamiliar code."
Based on the exploration (or direct knowledge), create a plan:
Write the plan to .claude/plans/{task-name}.md:
# Plan: {task-name}
## Problem
{one sentence}
## Approach
{2-3 sentences}
## Changes
1. `path/to/file.ext` — {what changes}
2. `path/to/other.ext` — {what changes}
## Risks
- {risk 1}
- {risk 2}
## Verification
{how to verify — specific command or check}
After writing the plan:
Skip planning for tasks where you can describe the diff in one sentence.