agent-ixagent-ix/spec-skills/spec-matrix/SKILL.md

spec-matrix

Skill1 starsChanged 6 months agoMITView on GitHub

Build and maintain the requirements Test Matrix ensuring 100% coverage.

1 other project uses a version of this.

Adopted by

Most recently taken up by

agent-ix/quointheir own version, first seen Jun 25, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
agent-ix/quoin★ 20same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- spec-app-reviewSkill
- spec-blueprintSkill
- spec-dependency-analysisSkill
- spec-evidence-analysisSkill
- spec-failure-domain-analysisSkill
- specifySkill
- spec-integrity-analysisSkill
- spec-object-reviewSkill
- spec-reviewSkill
- spec-risk-complexity-analysisSkill
- spec-scope-boundary-analysisSkill
- spec-security-analysisSkill
- spec-to-planSkill
- spec-us-to-frSkill
- spec-write-frSkill
- spec-write-itSkill
- spec-write-nfrSkill
- spec-write-strSkill
- spec-write-usSkill

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Use this skill to create the requirements Test Matrix and ensure comprehensive coverage.
line 8
Distinctive:
Verify: Ensure all 6 rules are satisfied.
line 37
Distinctive:
If ANY requirement specifies integration testing, include this section.
line 51
Very specific:
Use template section ## Integration Test Matrix with:
line 62

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Build Test Matrix

Use this skill to create the requirements Test Matrix and ensure comprehensive coverage.

Rules (The Six Requirements)

Coverage: Every Acceptance Criterion (AC) must have ≥1 Test Case (TC).
Option Permutation: Test all valid option combinations.
Constraint Boundary: Test min, max, below-min (fail), above-max (fail).
Error Path: Test all documented error conditions.
State Transition: Test all valid state transitions (if applicable).
Edge Case: Identify and test extreme/unusual scenarios.

Process

Initialize:
- Use template assets/test-matrix-template.md.
- Target: Correct location.
  - Single Repo: spec/tests.md
  - Multi-Repo: specs/<category>/<component>/spec/tests.md
Traceability:
- Map StR -> TC.
- Map US -> TC.
- Map FR -> TC.
- Map NFR -> TC.
- Map C (Constraints) -> TC.
Enumerate: List all Test Cases with ID, Title, Type, Priority, Status.
Define Detailed TCs (Optional):
- For complex tests, create at:
  - Single Repo: spec/test-cases/TC-XXX.md
  - Multi-Repo: specs/<category>/<component>/spec/test-cases/TC-XXX.md
Verify: Ensure all 6 rules are satisfied.
Status: Mark as ✅ Complete only when all rules are met.

React Components (Conditional)

For React projects, add a Storybook Test Matrix section.

See skills/review-react/SKILL.md for:

Story file requirements per component
AC trace code format in story JSDoc
Coverage matrix template (FR → AC → Story)

Integration Test Matrix (Conditional)

If ANY requirement specifies integration testing, include this section.

When Required

FR/NFR annotation: integration_test: true or mentions integration verification
Cross-project interactions (other services in your org)
Interactions with local-provided services (Redis, Postgres, message bus)
UI component browser testing (React → Storybook)

Section Contents

Use template section ## Integration Test Matrix with:

Purpose column: What integration is being tested
Target column: External system/service/project
Type column: service | browser | event | database
Test Cases: Extensive functional coverage, not just smoke tests

Coverage Expectations

Extensively test functionality (multiple scenarios per integration)
Include happy path + error conditions + edge cases
For browser tests: visual verification + interaction flows

Markers

✅ Complete
⚠️ Partial
❌ Missing
🚧 In Progress

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free