What does 'Non-blocking — advisory only' mean?

The tool reports gaps and mismatches but does not block progress; use the results to improve traceability and coverage.

Can Pactkit-analyze verify the actual content of the Spec or tests?

It verifies traceability: that R{N} requirements, Board Tasks, and AC items link to each other via Scenarios. It does not validate full content semantics.

Can I run this for multiple stories at once?

The usage is per STORY-XXX run. To cover many stories, run the command for each story in a loop or CI pipeline and aggregate the results.

pactkit-analyze

npx machina-cli add skill pactkit/claude-code-plugin/pactkit-analyze --openclaw

Files (1)

SKILL.md

606 B

Skill: pactkit-analyze

Run a consistency check between Spec, Sprint Board, and Test Cases for a given Story.

Usage

/pactkit-analyze STORY-XXX

What It Checks

Spec ↔ Board: Every Requirement (R{N}) has a matching Board Task, and every Task traces to a Requirement.
Spec AC ↔ Test Case: Every Acceptance Criteria item has a corresponding Scenario in the Test Case file.

Output

Prints an alignment matrix and coverage report. Non-blocking — advisory only.

Source

git clone https://github.com/pactkit/claude-code-plugin/blob/main/pactkit-plugin/skills/pactkit-analyze/SKILL.mdView on GitHub

Overview

pactkit-analyze performs a cross-artifact consistency check across the Spec, Sprint Board, and Test Case files for a given story. It verifies that all requirements (R{N}) map to board tasks and that every acceptance criteria item ties to a test scenario, then outputs a non-blocking alignment matrix and coverage report.

How This Skill Works

It analyzes references across the Spec, Board, and Test Case files to ensure each R{N} requirement has a matching Board Task and that every Task traces back to a Requirement. It also checks that each Acceptance Criteria item has a corresponding Scenario in the Test Case file. The result is an alignment matrix and a coverage report presented as advisory feedback.

When to Use It

During sprint planning to verify traceability from Spec to Board to Tests.
After updating the Spec or acceptance criteria to ensure changes propagate.
During backlog grooming to identify missing or orphaned tasks.
Before release to confirm test coverage aligns with acceptance criteria.
When auditors require a traceability matrix for compliance.

Quick Start

Step 1: Run /pactkit-analyze STORY-XXX
Step 2: Review the generated alignment matrix and coverage report
Step 3: Update Spec, Board, or Test Case to resolve gaps and re-run

Best Practices

Use consistent identifiers: R{N} in the Spec, board tasks, and AC tags.
Run pactkit-analyze after every major change to maintain alignment.
Treat the alignment matrix as advisory: fix gaps but prioritize critical gaps.
Document gaps and resolutions in a lightweight audit log.
Automate runs in CI to catch drift early.

Example Use Cases

STORY-101: All R{N} requirements map to board tasks and each Task traces back; ACs align with corresponding Scenarios.
STORY-102: AC2 has no matching Test Case Scenario detected, triggering a gap report.
STORY-150: Board Task exists without a corresponding Spec requirement, flagged for clarification.
STORY-203: Acceptance Criteria items map to multiple Scenarios with full coverage in the Test Case file.
STORY-301: Coverage matrix highlights gaps between Spec, Board, and Tests, suggesting concrete fixes.

Frequently Asked Questions

Add this skill to your agents