| name | cross-artifact-analysis |
| description | Perform cross-artifact consistency and coverage analysis across constitution, specification, plan, and task artifacts to detect gaps, conflicts, and misalignments before implementation. |
| allowed-tools | Read, Bash, Grep, Glob, Agent, AskUserQuestion |
| graph | {"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]} |
- When verifying that all specification requirements have corresponding tasks
- When checking for contradictions between constitution and plan
- When assessing readiness for the implementation phase
Key Principle
Every specification requirement must be traceable through the plan to at least one task. No artifact should contradict another. Coverage gaps and conflicts must be resolved before implementation.
Process
- Build traceability matrix - Map requirements -> plan components -> tasks
- Detect coverage gaps - Requirements without corresponding tasks
- Identify conflicts - Contradictory constraints or requirements across artifacts
- Verify constitution compliance - Plan and tasks comply with governance
- Check acceptance criteria - Task criteria match specification requirements
- Score consistency - Numeric score (0-100) across dimensions
- Determine readiness - Boolean assessment for implementation phase
- Human review - Approve analysis results before proceeding
Tool Use
Invoke via babysitter process: methodologies/spec-kit/spec-kit-planning (analysis phase)
Full pipeline: methodologies/spec-kit/spec-kit-orchestrator
