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, changeImpactAnalysistestingRequirements, specificationMapping, testCaseImpact
1C: Specification Mapping
- Test case mapping (existing tests affected)
- Business requirement mapping (new vs existing)
- Entity relationship impact, workflow integration
- Coverage gap analysis
1D: Overall Analysis
Write summary: end-to-end workflows, architecture patterns, business logic changes, integration points, test coverage.
Phase 2: Detailed Analysis
- Implementation Impact: Component impact, integration points, data flow, platform compliance
- Business Logic: New rules, modified workflows, validation requirements
- Testing Strategy: Coverage requirements, new scenarios, regression needs
- Specification Update Strategy: Integration, traceability, existing coverage preservation
- Rollback & Safety: Backup procedures, rollback plan, validation checkpoints
Phase 3: Approval Gate
CRITICAL: Present comprehensive analysis for explicit approval. DO NOT proceed without it.
Phase 4: Specification Update Execution
Once approved:
- Backup original specification
- Read and parse existing specification
- Execute updates: requirements, entity relationships, test cases, traceability matrix
- Quality assurance validation
Success Validation
- Requirements Traceability: All plan requirements mapped
- Test Coverage: All changes covered by tests
- Workflow Validation: End-to-end workflows documented
- Regression Prevention: Existing functionality protected
IMPORTANT Task Planning Notes
- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed
1---2name: plan-analysis3description: 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".4---5
6# Implementation Plan Analysis & Specification Update
7
8Expert full-stack analyst for implementation plan analysis, impact assessment, and specification updates.
9
10**IMPORTANT**: Think hard, plan step-by-step todo list first. Preserve todo list through all operations.
11
12**⚠️ MUST READ** `.claude/skills/shared/anti-hallucination-protocol.md` before starting analysis — validation checkpoints, evidence chains, confidence levels.
13
14---
15
16## Phase 1: Plan Analysis (External Memory)
17
18Build knowledge model in `.ai/workspace/analysis/[plan-name].md`.
19
20### 1A: Initialization & Discovery
21
22- Read and parse implementation plan completely
23- Extract features, requirements, phases, dependencies
24- Catalog all planned code changes (new files, modifications, deletions)
25- Identify affected components, services, layers, integration points
26
27### 1B: Knowledge Graph Construction
28
29For each file, document:
30- `currentContent`, `plannedChanges`, `changeImpactAnalysis`
31- `testingRequirements`, `specificationMapping`, `testCaseImpact`
32
33### 1C: Specification Mapping
34
35- Test case mapping (existing tests affected)
36- Business requirement mapping (new vs existing)
37- Entity relationship impact, workflow integration
38- Coverage gap analysis
39
40### 1D: Overall Analysis
41
42Write summary: end-to-end workflows, architecture patterns, business logic changes, integration points, test coverage.
43
44---
45
46## Phase 2: Detailed Analysis
47
481. **Implementation Impact**: Component impact, integration points, data flow, platform compliance
492. **Business Logic**: New rules, modified workflows, validation requirements
503. **Testing Strategy**: Coverage requirements, new scenarios, regression needs
514. **Specification Update Strategy**: Integration, traceability, existing coverage preservation
525. **Rollback & Safety**: Backup procedures, rollback plan, validation checkpoints
53
54---
55
56## Phase 3: Approval Gate
57
58**CRITICAL**: Present comprehensive analysis for explicit approval. **DO NOT** proceed without it.
59
60---
61
62## Phase 4: Specification Update Execution
63
64Once approved:
651. Backup original specification
662. Read and parse existing specification
673. Execute updates: requirements, entity relationships, test cases, traceability matrix
684. Quality assurance validation
69
70---
71
72## Success Validation
73
74- **Requirements Traceability**: All plan requirements mapped
75- **Test Coverage**: All changes covered by tests
76- **Workflow Validation**: End-to-end workflows documented
77- **Regression Prevention**: Existing functionality protected
78
79
80## IMPORTANT Task Planning Notes
81
82- Always plan and break many small todo tasks
83- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed
majiayu000