consistency-analysis

# Consistency Analysis Skill

## Purpose

This skill provides expertise in detecting inconsistencies, gaps, and conflicts across specification documents. It performs read-only cross-document analysis to ensure that requirements, tasks, data models, and plans are aligned and complete. The output is a structured analysis report with categorized findings and severity levels.

**IMPORTANT: This skill NEVER modifies files. It is strictly a read-only analysis tool.** All findings are reported for human review and resolution.

## When It Activates

The skill is triggered when the conversation involves:

- Reviewing specification quality or completeness
- Checking cross-document consistency (spec vs. tasks vs. plan)
- Detecting gaps in requirement coverage or task traceability
- Identifying conflicting definitions across documents
- Performing traceability analysis between artifacts

## Analysis Rule Categories

The skill evaluates documents against eight rule categories:

### 1. Requirement Coverage

Verify that every functional requirement (`FR-XXX`) and non-functional requirement (`NFR-XXX`) in the specification is addressed by at least one implementation task or plan item. Flag orphaned requirements with no downstream mapping.

### 2. Task Traceability

Ensure every task in `tasks.md` traces back to a specific requirement or user story in `spec.md`. Flag tasks with missing `[Spec §X.Y]` references or invalid reference targets.

### 3. Plan Alignment

Check that the implementation plan is consistent with the task list and specification. Detect mismatches in scope, ordering assumptions, or phase assignments between documents.

### 4. Data Model Consistency

Verify that entity definitions, field names, types, and relationships are consistent across the specification, data model section, and API contracts. Flag naming mismatches, type conflicts, or missing fields.

### 5. Contract Coverage

Ensure every API endpoint defined in the specification has corresponding tasks for i