coverage-matrix
Skill1 starsChanged 41 days agoNo licenceView on GitHub
Generate or maintain the three-way coverage matrix (invariants<->tests / events<->tests / DoD<->gate) for staged-delivery projects using this skill family's layout: unit tests under tests/unit/, a domain event registry (e.g. TIMELINE_EVENT_SPECS in src/domain/timeline.ts), per-stage spec DoD files, output at docs/tests/coverage-matrix.md — if your project does not follow this layout, this skill does not apply without path adaptation. Scans those sources, produces the matrix, and flags gaps (invariant without test, event without assertion) into the project's audit-item ledger. USER-INVOKED ONLY: it writes a tracked artifact and opens audit items; run only on the user's explicit request. Use when at a stage end or after adding invariants/events. NOT for: runtime enforcement — the matrix is a human-checked artifact, never a test gate.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- conjure-3301/skillstheir own version, first seen Aug 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- conjure-3301/skills★ 0same 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 repository93 other files it gives its agents.
- accessibility-auditorSkill
- agent-dispatchSkill
- api-contract-validatorSkill
- architecture-patternsSkill
- audit-itemSkill
- autonomous-investigationSkill
- battle-card-builderSkill
- cicd-pipelineSkill
- codebase-designSkill
- code-reviewSkill
- company-intelSkill
- competitive-analysis-processSkill
- competitive-intel-watchSkill
- competitive-research-snapshotSkill
- config-scanSkill
- core-rulesSkill
- customer-journey-mapSkill
- ddd-aggregatesSkill
- ddd-context-mapSkill
- ddd-contextsSkill
- ddd-discoverSkill
- ddd-domain-interactionsSkill
- ddd-model-reviewSkill
- ddd-openspec-bridgeSkill
- ddd-qa-chainSkill
- ddd-scopeSkill
- ddd-subdomainsSkill
- ddd-tactical-reviewSkill
- decision-logSkill
- deep-codebase-analysisSkill
- delegated-researchSkill
- dependency-scanSkill
- discovery-interview-prepSkill
- electron-best-practicesSkill
- env-checkSkill
- event-stormingSkill
- executing-plansSkill
- experiment-handoffSkill
- frontend-designSkill
- git-workflowSkill
- grill-meSkill
- intelligence-collection-disciplinesSkill
- jobs-to-be-doneSkill
- k6-performanceSkill
- llm-gateway-opsSkill
- marketing-copywritingSkill
- market-landscape-scanSkill
- perf-checkSkill
- pipeline-0to1Skill
- pixel-perfectSkill
- plan-grillingSkill
- playwright-best-practicesSkill
- positioning-statementSkill
- positioning-workshopSkill
- prd-developmentSkill
- prd-driven-dddSkill
- press-releaseSkill
- problem-handlingSkill
- problem-statementSkill
- product-doc-auditSkill
- The first 60 shown.
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.