Agent skill
vibe-scenario-matrix
Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning. Maps user scenarios to acceptance criteria with stable IDs.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/scenario-matrix
SKILL.md
vibe-scenario-matrix
Test coverage isn't about code lines -- it's about user scenarios. Map them all.
When to Use This Skill
- Planning test coverage for a complex feature
- Preparing for a release or milestone review
- After expanding requirements significantly
- When stakeholders ask "what's tested?"
- Transitioning from ad-hoc testing to systematic testing
When NOT to Use This Skill
- Single-function unit testing (just write the test)
- Already have comprehensive test specifications
- Prototyping/spiking (too early for formal coverage)
Steps
-
Gather scenarios from:
- PRD / Requirements document
- User stories / acceptance criteria
- Bug reports (past failures = scenarios to test)
- User feedback / support tickets
- Edge cases discovered during development
-
Assign stable IDs -- Use format
[Section]-[Number]:- Example:
AUTH-001,PAYMENT-015,ONBOARD-003 - IDs never change once assigned (even if scenario text changes)
- Example:
-
Classify testing approach:
- Deterministic (61%): Can be tested with standard assertions
- LLM-as-Judge (24%): Needs qualitative assessment
- Simulation (11%): Needs multi-step environment
- Proxy Metric (4%): Can only be measured indirectly
-
Build the matrix:
| ID | Scenario | Expected Behavior | Test Approach | Status |
|---|---|---|---|---|
| AUTH-001 | User logs in with valid credentials | Redirect to dashboard, session created | Deterministic | PASS |
| AUTH-002 | User enters wrong password 5 times | Account locked for 30 minutes | Deterministic | NOT_IMPL |
| TONE-001 | System responds empathetically to frustration | Response acknowledges emotion without dismissing | LLM-as-Judge | PARTIAL |
- Track status: PASS / PARTIAL / FAIL / NOT_IMPLEMENTED / DEFERRED
Output Format
Scenario Acceptance Matrix: [Feature/Product]
Total Scenarios: X Coverage: Y% (PASS or PARTIAL)
| Status | Count | % |
|---|---|---|
| PASS | X | X% |
| PARTIAL | X | X% |
| NOT_IMPLEMENTED | X | X% |
| DEFERRED | X | X% |
By Testing Approach
| Approach | Count | Tooling Needed |
|---|---|---|
| Deterministic | X | Standard test framework |
| LLM-as-Judge | X | Evaluation framework |
| Simulation | X | Environment setup |
| Proxy Metric | X | Metrics pipeline |
Full Matrix
[Table as above]
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?