analysis-phase

Diagnoses cross-consistency issues and detects breaking changes across specs, plans, tasks, and dependencies.

Updated Oct 26, 2025
One-click install
npx skills add https://github.com/oxie/portfolio-cms-project --skill analysis-phase-oxie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analysis-phase
Source: https://github.com/oxie/portfolio-cms-project/tree/main/.claude/skills/analysis-phase
Command: npx skills add https://github.com/oxie/portfolio-cms-project --skill analysis-phase-oxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures consistency across all project artifacts (specification, plan, tasks) and identifies potential breaking changes early in the development lifecycle. It prevents costly rework, integration issues, and unexpected disruptions by catching problems before implementation begins.

Core Features & Use Cases

  • Cross-Artifact Consistency Checks: Validates alignment between the feature specification, implementation plan, and detailed tasks.
  • Breaking Change Detection: Identifies potential breaking changes in APIs, database schemas, or UI components that could impact existing systems.
  • Dependency Validation: Verifies that all internal and external dependencies are correctly accounted for and aligned.
  • Use Case: Before starting implementation, this skill helps a technical lead review a feature's specification, plan, and tasks to ensure everything aligns and no breaking changes have been overlooked, saving significant time and effort.

Quick Start

Analyze the 'Student Progress Dashboard' feature, checking for cross-artifact consistency and detecting any potential breaking changes.

Frequently Asked Questions about analysis-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect breaking changes across project artifacts before implementation?

Breaking-change detection identifies API, database, and UI modifications that could disrupt existing systems by analyzing specifications, plans, and tasks before development begins. This catches inconsistencies early, preventing costly rework and integration failures.

What's the best way to ensure consistency between specifications, plans, and tasks?

Cross-artifact consistency checks validate alignment between feature specifications, implementation plans, and detailed tasks. The analysis-phase workflow compares these documents against defined rules to flag misalignments that could derail projects.

Can I validate dependencies across my project artifacts?

Dependency validation verifies that all internal and external dependencies are correctly accounted for and aligned across specifications, plans, and tasks. This ensures no missing or conflicting requirements propagate into implementation.

When should I run consistency and breaking-change checks in the development lifecycle?

Analysis-phase checks should run before implementation begins. Early detection of cross-artifact inconsistencies and breaking changes in specifications, plans, and tasks prevents costly delays and rework later in the development cycle.

What output does a cross-artifact analysis provide?

The analysis generates a comprehensive report documenting cross-artifact inconsistencies, detected breaking changes, dependency validation results, and alignment issues. This report guides technical leads and teams on what to resolve before proceeding.