analysis-phase

Standard Operating Procedure for /analyze phase. Covers cross-artifact consistency validation and breaking change detection.

⭐0stars🔀0forks📁View on GitHub🕐Updated Nov 24, 2025

When & Why to Use This Skill

This Claude skill provides a structured Standard Operating Procedure (SOP) for the critical analysis phase of the software development lifecycle. It streamlines cross-artifact consistency validation and breaking change detection, helping developers maintain perfect alignment between specifications, plans, and implementations while proactively identifying technical risks.

Use Cases

  • Cross-Artifact Validation: Ensure that technical specifications, development plans, and actual code implementations remain perfectly synchronized to prevent logic drift.
  • Breaking Change Detection: Proactively identify potential regressions or breaking changes in API contracts, database schemas, and UI components during the development process.
  • Dependency & Integration Checks: Validate that all internal and external dependencies are correctly mapped and consistent with the current project state.
  • Automated Quality Reporting: Generate comprehensive analysis-report.md files that document findings, verify completion criteria, and provide a clear audit trail for the /analyze phase.
nameanalysis-phase
description"Standard Operating Procedure for /analyze phase. Covers cross-artifact consistency validation and breaking change detection."
allowed-toolsRead, Edit, Grep, Bash

Analysis Phase: Standard Operating Procedure

Training Guide: Validate cross-artifact consistency and detect breaking changes.

Phase Overview

Purpose: Review work and identify potential breaking changes or inconsistencies. Inputs: All workflow artifacts Outputs: analysis-report.md with findings Expected duration: 15-30 minutes

Execution Steps

  1. Check spec-plan consistency
  2. Verify task-implementation alignment
  3. Detect breaking changes (API, database, UI)
  4. Validate dependencies
  5. Generate analysis report

Common Mistakes

  • Missing breaking change detection
  • Inconsistent artifacts
  • No cross-reference validation

Completion Criteria

  • All artifacts consistent
  • Breaking changes documented
  • Analysis report generated

This SOP guides the analysis phase.