skills.rest
abner-magal
abner-magalCOMMUNITY
Explore all skills by this author →
GitHub

analysis-phase

Validate cross-artifact consistency and detect breaking changes in software development plans.

Updated Aug 23, 2026
Search Tags:#validation#breaking changes#consistency check#task alignment#spec to plan#pre-implementation analysis
One-click install
npx skills add https://github.com/abner-magal/mcp-video-audio --skill analysis-phase-abner-magal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analysis-phase
Source: https://github.com/abner-magal/mcp-video-audio/tree/main/.opencode/skills/analysis-phase
Command: npx skills add https://github.com/abner-magal/mcp-video-audio --skill analysis-phase-abner-magal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents costly rework and deployment failures by rigorously validating the consistency between your specifications, plans, and tasks, and by proactively identifying breaking changes before they impact development.

Core Features & Use Cases

  • Cross-Artifact Validation: Ensures spec requirements map to plan components, and plan components are broken down into actionable tasks.
  • Breaking Change Detection: Scans for modifications in APIs, databases, UIs, and authentication that could disrupt existing systems.
  • Use Case: Before starting development on a new feature, run this Skill to confirm that the spec.md accurately reflects the plan.md, and that no unintended API signature changes have been introduced, ensuring a smooth implementation phase.

Quick Start

Validate the consistency between spec, plan, and tasks artifacts for the current feature.

Frequently Asked Questions about analysis-phase

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

FAQPage Schema
How do I check for breaking changes before deploying a new feature?▼

Validate cross-artifact consistency by mapping specification requirements to plan components and task breakdowns, ensuring no unintended API, database, UI, or authentication regressions are introduced before implementation begins.

How do I validate spec to plan alignment for software development tasks?▼

Validate spec to plan alignment by mapping specification requirements to plan components and verifying those components are broken down into actionable tasks, ensuring complete task alignment before the implementation phase starts.

What is cross-artifact consistency check in the software lifecycle?▼

Cross-artifact consistency check is a pre-implementation analysis that ensures alignment between specification documents, implementation plans, and task breakdowns, preventing costly rework and deployment failures caused by misaligned artifacts.

Does pre-implementation analysis detect API signature regressions?▼

Yes, pre-implementation analysis scans for modifications in APIs and other system components to catch unintended signature changes, detecting potential breaking changes that could disrupt existing systems before development starts.

When do I need to run a consistency check between specs and plans?▼

Run a consistency check before starting development on a new feature to confirm that the specification document accurately reflects the implementation plan and that no unintended breaking changes have been introduced into the workflow.

Related Skills

Explore More Software Engineering Skills→
dan1901dan1901
1

spec-validator

Validate Spec-Driven Development artifacts across feature directories and generate a report of findings and recommendations.

Community
Basic
tangzheng202202tangzheng202202
1

systematic-debugging

Guide engineers through a four-phase root-cause investigation to diagnose bugs.

Community
Advanced
devon87warren-afkdevon87warren-afk

braingrid-cli

Convert user prompts into software requirements and tasks using BrainGrid CLI.

Community
Advanced
jonnymuirjonnymuir
1

security-regression-contract-audit

Audit C# security regression suites to separate genuine vulnerabilities from placeholder tests.

Community
Advanced