How do I install the Vibe Scenario Matrix skill?

Run npx skillmds@latest add majiayu000/vibe-scenario-matrix in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vibe Scenario Matrix safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vibe Scenario Matrix?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vibe Scenario Matrix free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vibe Scenario Matrix?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vibe Scenario Matrix by majiayu000 — Agent Skill

Name: Vibe Scenario Matrix
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

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)
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]

---name: vibe-scenario-matrixdescription: Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning. Maps user scenarios to acceptance criteria with stable IDs.--- # 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 1. **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 2. **Assign stable IDs** -- Use format `[Section]-[Number]`: - Example: `AUTH-001`, `PAYMENT-015`, `ONBOARD-003` - IDs never change once assigned (even if scenario text changes) 3. **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 4. **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 | 5. **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]

Frequently asked questions

Vibe Scenario Matrix