Agent skill · Documentation

plan-analysis

Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes. Triggers on keywords like "analyze plan", "implementation plan", "assess impact", "update spec from plan", "verify plan".

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill plan-analysis --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Allowed tools: ReadWriteEditBashGrepGlobTaskTodoWrite
Path: skills/analysis/plan-analysis/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Implementation Plan Analysis & Specification Update Expert full-stack analyst for implementation plan analysis, impact assessment, and specification updates. **IMPORTANT**: Think hard, plan step-by-step todo list first. Preserve todo list through all operations. **⚠️ MUST READ** `.claude/skills/shared/anti-hallucination-protocol.md` before starting analysis — validation checkpoints, evidence chains, confidence levels. --- ## Phase 1: Plan Analysis (External Memory) Build knowledge model in `.ai/workspace/analysis/[plan-name].md`. ### 1A: Initialization & Discovery - Read and parse implementation plan completely - Extract features, requirements, phases, dependencies - Catalog all planned code changes (new files, modifications, deletions) - Identify affected components, services, layers, integration points ### 1B: Knowledge Graph Construction For each file, document: - `currentContent`, `plannedChanges`, `changeImpactAnalysis` - `testingRequirements`, `specificationMapping`, `testCaseImpact` ### 1C: Specification Mapping - Test case mapping (existing tests affected) - Business requirement mapping (new vs existing) - Entity relationship impact, workflow integration - Coverage gap an

What's inside
Steps it walks through
  1. Phase 1: Plan Analysis (External Memory)
  2. 1A: Initialization & Discovery
  3. 1B: Knowledge Graph Construction
  4. 1C: Specification Mapping
  5. 1D: Overall Analysis
  6. Phase 2: Detailed Analysis
  7. Phase 3: Approval Gate
  8. Phase 4: Specification Update Execution
  9. Success Validation
  10. IMPORTANT Task Planning Notes
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the plan-analysis skill do?

Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes. Triggers on keywords like "analyze plan", "implementation plan", "assess impact", "update spec from plan", "verify plan".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill plan-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going