iikit-06-analyze

Validates cross-artifact consistency across spec, plan, and tasks documents.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/hafidzlvm/opencode --skill iikit-06-analyze-hafidzlvm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iikit-06-analyze
Source: https://github.com/hafidzlvm/opencode/tree/main/.tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-06-analyze
Command: npx skills add https://github.com/hafidzlvm/opencode --skill iikit-06-analyze-hafidzlvm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Design documents drift apart as a feature evolves: requirements lose task coverage, plans reference undefined components, and constitution principles get violated silently. This Skill audits spec.md, plan.md, and tasks.md together to detect inconsistencies before implementation begins. ## Core Features & Use Cases - Traceability Analysis: Maps every requirement (FR-xxx/SC-xxx) to tasks and plan sections, flagging zero-coverage requirements and orphaned tasks. - Multi-Pass Detection: Runs eight detection passes covering duplication, ambiguity, underspecification, constitution alignment, phase separation, coverage gaps, inconsistency, and BDD feature-file traceability. - Health Scoring: Computes a 0-100 health score from severity-weighted findings and persists score history to .specify/score-history.json with trend tracking. - Use Case: Before running implementation, a developer invokes the analyze phase to confirm all 12 spec requirements have mapped tasks, the plan's tech stack matches task file paths, and no constitution MUST principles are violated — receiving a severity-ranked report in analysis.md. ## Quick Start Ask the AI to run a consistency analysis across the current feature's spec, plan, and tasks artifacts and report any critical issues.

Frequently Asked Questions about iikit-06-analyze

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

FAQPage Schema
How do I check requirements traceability between spec and tasks?▼

Run the analyze phase, which builds a task coverage mapping from tasks.md and verifies every FR-xxx and SC-xxx requirement in spec.md has at least one mapped task. Requirements with zero coverage are flagged as findings with severity based on their blocking status.

What does a spec-driven consistency analysis detect?▼

It detects near-duplicate requirements, vague terms without measurable criteria, underspecified stories, constitution MUST violations, content placed in the wrong artifact, coverage gaps, terminology drift, and untested requirements missing BDD feature tags.

Does the analysis modify my spec or plan files?▼

No, the analysis is read-only for spec.md, plan.md, and tasks.md. It only writes the analysis.md report and appends score history to .specify/score-history.json. Remediation edits are suggested but never applied automatically.

How is the specification health score calculated?▼

The score starts at 100 and subtracts weighted penalties: 20 per critical finding, 5 per high, 2 per medium, and 0.5 per low, floored at zero. Each run is appended to score history so trends show as improving, declining, or stable.

Why does the analyze phase fail with a constitution error?▼

Phase 06 requires hard constitution mode, meaning CONSTITUTION.md must exist at the repository root. If it is missing, the prerequisites script exits with an error directing you to run the constitution phase first.

When should I run consistency analysis in the workflow?▼

Run it after tasks are generated and before implementation begins. It requires valid spec, plan, and tasks artifacts, and critical findings should be resolved before proceeding to the implement phase.