Create a structured implementation plan with risk assessment, phased steps, and validation gates. Saves plan to ./plans/ directory. Waits for user confirmation before any implementation begins.
From cc-setupnpx claudepluginhub krzemienski/cc-setup --plugin cc-setupThis skill uses the workspace's default tool permissions.
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.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Create a detailed, file-backed implementation plan before any code is written.
Restate what will be built in your own words. Be specific about scope and what is explicitly out of scope.
Rate each risk HIGH / MEDIUM / LOW:
Break work into phases. Each phase must have:
Phase structure:
Phase 1: <Name>
Goal: <What this phase achieves>
Steps:
1.1 ...
1.2 ...
Validation gate: <What must be true before Phase 2 begins>
Every plan must end with a Functional Validation Phase:
Phase N: Functional Validation
Goal: Prove the system works end-to-end through real execution
Steps:
N.1 Build / start the real system (no mocks, no stubs)
N.2 Exercise the feature through its actual interface (CLI, UI, API)
N.3 Capture evidence (screenshot, log output, response body)
N.4 Confirm evidence matches requirements from Phase 1
Validation gate: Evidence captured and requirements met
No unit tests. No test files. No mocks. Validate through the real system only.
Determine the plan slug from the requirements (kebab-case, descriptive).
Save the plan to:
./plans/YYMMDD-HHMM-<slug>/plan.md
Use today's date and current time for the timestamp (format: YYMMDD-HHMM).
The plan file should contain:
After saving the plan, output the full plan to the user and end with:
Plan saved to: ./plans/YYMMDD-HHMM-<slug>/plan.md
CONFIRM to proceed, or tell me what to change.
Do NOT write any code, create any files (other than the plan), or take any implementation action until the user replies with "confirm", "yes", "proceed", or equivalent.
If the user requests changes, update the plan file and re-present it. Wait again.
## Requirements
<Clear restatement of what will be built and what is out of scope>
## Risks
| Severity | Risk | Mitigation |
|----------|------|------------|
| HIGH | ... | ... |
| MEDIUM | ... | ... |
| LOW | ... | ... |
## Dependencies
- <Dependency 1>: <why needed>
## Complexity: HIGH / MEDIUM / LOW (~X hours / days)
## Phases
### Phase 1: <Name>
**Goal:** ...
1.1 ...
1.2 ...
**Validation gate:** ...
### Phase 2: ...
### Phase N: Functional Validation
**Goal:** Prove the system works through real execution
N.1 Build / start the real system
N.2 Exercise through actual interface
N.3 Capture evidence
N.4 Confirm requirements met
**Validation gate:** Evidence captured and requirements met