AgentStack
SKILL verified MIT Self-run

Vibe Scenario Matrix

skill-ash1794-vibe-engineering-scenario-matrix · by ash1794

Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning. Maps user scenarios to acceptance criteria with stable IDs.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-ash1794-vibe-engineering-scenario-matrix

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Vibe Scenario Matrix? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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
  1. Assign stable IDs -- Use format [Section]-[Number]:
  • Example: AUTH-001, PAYMENT-015, ONBOARD-003
  • IDs never change once assigned (even if scenario text changes)
  1. 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
  1. 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 |

  1. 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]

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.