Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
日本語の概要は準備中です。原文の説明を表示しています。
ash1794/vibe-engineering1642026年10月8日 更新
無料GitHub で公開
vibe-scenario-matrix
Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning. Maps user scenarios to acceptance criteria with stable IDs. Use when planning test coverage for a complex feature, before a release or milestone review, or when someone asks what is tested.
含まれるファイル（1）
- SKILL.md2.7 KB
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]
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.
日本語の概要は準備中です。原文の説明を表示しています。
ash1794/vibe-engineering1642026年10月8日 更新
Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.
日本語の概要は準備中です。原文の説明を表示しています。
ash1794/vibe-engineering1642026年10月8日 更新
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
日本語の概要は準備中です。原文の説明を表示しています。
ash1794/vibe-engineering1642026年10月8日 更新
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
日本語の概要は準備中です。原文の説明を表示しています。
ash1794/vibe-engineering1642026年10月8日 更新
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
日本語の概要は準備中です。原文の説明を表示しています。
ash1794/vibe-engineering1642026年10月8日 更新