跳到正文
cccskills
免费在 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(原文)

安装前可以查看交给 AI 代理的指令内容。

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:

IDScenarioExpected BehaviorTest ApproachStatus
AUTH-001User logs in with valid credentialsRedirect to dashboard, session createdDeterministicPASS
AUTH-002User enters wrong password 5 timesAccount locked for 30 minutesDeterministicNOT_IMPL
TONE-001System responds empathetically to frustrationResponse acknowledges emotion without dismissingLLM-as-JudgePARTIAL
  1. Track status: PASS / PARTIAL / FAIL / NOT_IMPLEMENTED / DEFERRED

Output Format

Scenario Acceptance Matrix: [Feature/Product]

Total Scenarios: X Coverage: Y% (PASS or PARTIAL)

StatusCount%
PASSXX%
PARTIALXX%
NOT_IMPLEMENTEDXX%
DEFERREDXX%

By Testing Approach

ApproachCountTooling Needed
DeterministicXStandard test framework
LLM-as-JudgeXEvaluation framework
SimulationXEnvironment setup
Proxy MetricXMetrics pipeline

Full Matrix

[Table as above]

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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日 更新

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日 更新

查看 ash1794 的全部技能

报告此技能的问题