Skip to content
Skills Library
Management & product · Review & audit

analysis-phase

/analysis-phase

Validates cross-artifact consistency and detects breaking changes during feature analysis. Use when running /analyze command, validating spec-plan alignment, checking task-implementation consistency, or identifying API/database/UI breaking changes before deployment. (project)

Repository
Spec-Flow ↗
Licence
MIT
Last repository change
23.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Validates cross-artifact consistency and detects breaking changes during feature analysis. Use when running /analyze command, validating spec-plan alignment, checking task-implementation consistency, or identifying API/database/UI breaking changes before deployment. (project)

Original author description

Validates cross-artifact consistency and detects breaking changes during feature analysis. Use when running /analyze command, validating spec-plan alignment, checking task-implementation consistency, or identifying API/database/UI breaking changes before deployment. (project)

How it works

SKILL.md has no level-two headings · 151 lines, 519 words

SKILL.md preview
---
name: analysis-phase
description: Validates cross-artifact consistency and detects breaking changes during feature analysis. Use when running /analyze command, validating spec-plan alignment, checking task-implementation consistency, or identifying API/database/UI breaking changes before deployment. (project)
allowed-tools: Read, Edit, Grep, Bash
---

<objective>
Validates cross-artifact consistency and detects breaking changes during the /analyze phase. Ensures spec requirements align with plan components, tasks match implementation, and breaking changes are identified before deployment.
</objective>

<quick_start>
Validate cross-artifact consistency and detect breaking changes:

1. Check spec → plan → tasks alignment
2. Detect breaking changes (API, database, UI, auth)
3. Validate dependencies
4. Generate analysis-report.md with findings

**Inputs**: spec.md, plan.md, tasks.md
**Outputs**: analysis-report.md
</quick_start>

<workflow>
<step number="1">
**Check spec-plan consistency**

Read spec.md requirements, verify each has corresponding plan component. Flag missing mappings in analysis report.

See references/examples.md for grep commands.
</step>

<step number="2">
**Verify task-implementation alignment**

Read plan.md components, verify each broken into tasks in tasks.md.

Validate:

- Each plan component has ≥1 task
- Task acceptance criteria match spec success criteria
- No orphaned tasks (tasks without plan component)
  </step>

<step number="3">
**Detect breaking changes**

Scan for patterns indicating breaking changes:

- **API changes**: Endpoint signature modifications, required parameter additions, response format changes
- **Database changes**: Schema modifications, required field additions, migrations affecting existing data
- **UI changes**: Component interface changes, prop requirement additions
- **Auth changes**: Permission model modifications, authentication flow changes

Flag with impact level (Low/Medium/High) using reference rubric.
</step>

<step number="4">
**Validate dependencies**

Cross-reference:

- Imports and integrations mentioned in plan
- External dependencies in tasks
- Integration points in spec

Verify all dependencies documented and accounted for.
</step>

<step number="5">
**Generate analysis report**

Create specs/NNN-slug/analysis-report.md:

```markdown
# Analysis Report

## Consistency Check

- Spec-Plan: [✓/✗] Description
- Plan-Tasks: [✓/✗] Description

## Breaking Changes

- [High/Medium/Low] Description and impact

## Dependency Validation

- [✓/✗] Dependencies documented

## Recommendations

- Action items to fix inconsistencies
```

Update state.yaml: `analysis.status = completed`
</step>
</workflow>

<validation>
After analysis, verify:

- All spec requirements have plan component coverage
- All plan components have task breakdown
- Breaking changes flagged with impact level (Low/Medium/High)
- Analysis report generated with actionable findings
- No orphaned artifacts (tasks without plan, plan without spec)
  </validation>

<anti_patterns>
<pitfall name="missing_breaking_changes">
**❌ Don't**: Assume no breaking changes without scanning
**✅ Do**: Explicitly check API signatures, database schema, required fields, auth changes

**Why**: Breaking changes missed in analysis cause production issues post-deployment
</pitfall>

<pitfall name="inconsistent_artifacts">
**❌ Don't**: Assume spec and plan are aligned
**✅ Do**: Explicitly validate each spec requirement has corresponding plan component

**Why**: Missing mappings lead to incomplete implementation
</pitfall>

<pitfall name="no_cross_reference">
**❌ Don't**: Skip dependency validation
**✅ Do**: Cross-reference all imports, integrations, external dependencies

**Why**: Undocumented dependencies cause integration failures
</pitfall>

<pitfall name="vague_findings">
**❌ Don't**: Write vague findings like "inconsistencies found"
**✅ Do**: Specify exact artifacts, line numbers, and recommended fixes

**Why**: Actionable findings enable quick remediation
</pitfall>
</anti_patterns>

<success_criteria>

- [ ] All spec requirements mapped to plan components (no gaps)
- [ ] All plan components broken into tasks (no orphans)
- [ ] Breaking changes documented with impact level (High/Medium/Low)
- [ ] Dependencies validated and documented
- [ ] analysis-report.md generated with actionable findings
- [ ] state.yaml updated (analysis.status = completed)
      </success_criteria>

<references>
See references/ for:
- Cross-artifact consistency matrix
- Breaking change detection patterns
- Impact assessment rubric
- Real-world analysis examples
</references>
Files in this package (5)
  • SKILL.md 5 KB
  • references/breaking-changes.md 5 KB
  • references/consistency-matrix.md 2 KB
  • references/examples.md 5 KB
  • references/reference.md 20 KB

Versions

The database has no other skills named analysis-phase.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 97046300929f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100phase-review
    Review implementation plans from the .tasks/ directory for flaws before committing — either a single phase (phase mode) or across all phases of a task for consistency (cross-phase analyze mode). Triggers on: 'use phase mode', 'review phase', 'review the plan', 'check phase',…
  • 84review-spec
    Reviews proposal, specification, design, and task artifacts for internal consistency, testability, traceability, and cross-artifact alignment. Use when asked to review a spec, review artifacts, check design documents, check a change for consistency, or verify artifact quality before implementation.
  • 100spec-analyze
    Check consistency and alignment between spec.md, plan.md, and project/TASKS.md — detect drift and mismatches. Use when: analyze spec, consistency check, alignment, drift, spec vs plan, are specs aligned, spec mismatch.
  • 100api-design-reviewer
    Review REST API designs for quality, consistency, and breaking changes. Lints OpenAPI specs, generates scorecards, and detects breaking changes between versions. Use when designing APIs, reviewing contracts, or managing API versioning.
  • 100validate-plan
    This skill should be used when the user asks to 'validate a plan', 'check plan against spec', or 'verify plan alignment'. Validates a project plan against its parent spec for alignment, missing requirements, and consistency.
  • 91breaking-change-detector
    Detect and warn about breaking API/schema changes before implementation. Auto-trigger when modifying API routes, database schemas, or public interfaces. Validates changes against api-strategy.md versioning rules. Suggests migration paths for breaking changes. Prevents removing…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.