Enrich Release Roadmap
trickle-labs/pg-trickle
Enrich a pgtrickle release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage.
Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning.
Install Vibe Scenario Matrix
$ npx skills add ash1794/vibe-engineering --skill vibe-scenario-matrix -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ash1794/vibe-engineering vibe-scenario-matrix --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-scenario-matrix .claude/skills/vibe-scenario-matrix && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vibe-scenario-matrix" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-scenario-matrix into .claude/skills/vibe-scenario-matrix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-scenario-matrix", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-scenario-matrixType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ash1794/vibe-engineering --skill vibe-scenario-matrix -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ash1794/vibe-engineering vibe-scenario-matrix --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-scenario-matrix .agents/skills/vibe-scenario-matrix && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-scenario-matrix" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-scenario-matrix into .agents/skills/vibe-scenario-matrix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-scenario-matrix", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ash1794/vibe-engineering --skill vibe-scenario-matrix -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ash1794/vibe-engineering vibe-scenario-matrix --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-scenario-matrix .cursor/skills/vibe-scenario-matrix && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibe-scenario-matrix" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-scenario-matrix into .cursor/skills/vibe-scenario-matrix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-scenario-matrix", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ash1794/vibe-engineering.git --path plugins/vibe-engineering/skills/vibe-scenario-matrix--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ash1794/vibe-engineering --skill vibe-scenario-matrix -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ash1794/vibe-engineering vibe-scenario-matrix --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-scenario-matrix .gemini/skills/vibe-scenario-matrix && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibe-scenario-matrix" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-scenario-matrix into .gemini/skills/vibe-scenario-matrix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-scenario-matrix", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ash1794/vibe-engineering vibe-scenario-matrixInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ash1794/vibe-engineering --skill vibe-scenario-matrix -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-scenario-matrix .github/skills/vibe-scenario-matrix && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibe-scenario-matrix" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-scenario-matrix into .github/skills/vibe-scenario-matrix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-scenario-matrix", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ash1794/vibe-engineering --skill vibe-scenario-matrix -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ash1794/vibe-engineering vibe-scenario-matrix --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-scenario-matrix .opencode/skills/vibe-scenario-matrix && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibe-scenario-matrix" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-scenario-matrix into .opencode/skills/vibe-scenario-matrix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-scenario-matrix", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vibe-scenario-matrix- GitHub stars
- 163
- Token cost
- ~695 tokens
- SKILL.md length
- 270 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning.
- Works in 4 steps: Gather scenarios from → Assign stable IDs -- Use format… → Classify testing approach → …
- Planning test coverage for a complex feature
- SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Steps and Output Format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vibe Scenario Matrix is an agent skill from ash1794/vibe-engineering. 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.
Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Test coverage, Project management and User stories. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.
When your agent uses it
- Planning test coverage for a complex feature
- Before a release
- Milestone review
- Someone asks what is tested
Example prompts
- “Use the vibe-scenario-matrix skill to generate a behavioral scenario acceptance matrix for comprehensive test coverage planning”
- “/vibe-scenario-matrix”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Gather scenarios from
- Assign stable IDs -- Use format [Section]-[Number]
- Classify testing approach
- Build the matrix
What it can do on your machine
Read from SKILL.md and the folder at commit 8f1d71b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vibe Scenario Matrix loads about 695 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 270 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 270 words, ~695 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-scenario-matrix/SKILL.md (or your agent's skills folder).- name
- vibe-scenario-matrix
- description
- 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.
- user-invocable
- true
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]
© ash1794, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/vibe-engineering/skills/vibe-scenario-matrix of ash1794/vibe-engineering.
Open the folder on GitHubat commit 8f1d71b
Compare with similar skills
Vibe Scenario Matrix next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibe Scenario Matrix this skillash1794/vibe-engineering | 163 | — | ~695 | Automated safety check: Pass | MIT | |
| Enrich Release Roadmaptrickle-labs/pg-trickle | 148 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Verification Gatesrohitg00/skillkit | 1.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Project Planneradrianpuiu/claude-skills-marketplace | 100 | 1 repos | ~6k | Automated safety check: Pass | None | |
| Invokta Deliveryvinilana/invokta | 139 | — | ~894 | Automated safety check: Pass | MIT | |
| Bmad Sprint Planningdelorenj/mcp-server-trello | 445 | 5 repos | ~3k | Automated safety check: Pass | MIT |
Similar skills
Verification Gates
rohitg00/skillkit
Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding.
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
Invokta Delivery
vinilana/invokta
Deliver Invokta milestones and work items with TDD, adherence to versioned contracts and architecture, complete validation, and one cohesive commit per work item.
Bmad Sprint Planning
delorenj/mcp-server-trello
Generate sprint status tracking from epics. An agent skill from delorenj/mcp-server-trello.
Levyra Project Manager
LUC4N3X/Levyra-deepsound
Turn Levyra requirements and roadmap outcomes into one reviewable active phase using docs/project/SPEC.md, docs/project/ROADMAP.md, docs/project/TASKS.md, acceptance criteria, validation, owner…
More from ash1794/vibe-engineering
All 33 skills in this repoVibe Concurrent Test Safety
ash1794/vibe-engineering
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.
Vibe Fuzz Parser Inputs
ash1794/vibe-engineering
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).
Vibe Golden File Testing
ash1794/vibe-engineering
Implements snapshot/golden file tests with temporal normalization so tests don't break daily.
Vibe Parallel Task Decomposition
ash1794/vibe-engineering
Analyzes large tasks for independent subtasks that can be safely parallelized.
Vibe Slop Filter
ash1794/vibe-engineering
Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).
Vibe Spec Sync
ash1794/vibe-engineering
Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.
Related
Categories
Questions about Vibe Scenario Matrix
What does Vibe Scenario Matrix do?
Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning. Vibe Scenario Matrix is an agent skill from ash1794/vibe-engineering. Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning.
When should I use Vibe Scenario Matrix?
Vibe Scenario Matrix fits situations like: planning test coverage for a complex feature; before a release; milestone review; someone asks what is tested.
How do I install Vibe Scenario Matrix in Claude Code?
Run `npx skills add ash1794/vibe-engineering --skill vibe-scenario-matrix -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-scenario-matrix in ash1794/vibe-engineering) into .claude/skills/vibe-scenario-matrix in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Scenario Matrix in Codex?
Run `npx skills add ash1794/vibe-engineering --skill vibe-scenario-matrix -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-scenario-matrix in ash1794/vibe-engineering) into .agents/skills/vibe-scenario-matrix in your project. Codex loads it when a task matches its description.
Can I use Vibe Scenario Matrix in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ash1794/vibe-engineering --skill vibe-scenario-matrix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-scenario-matrix, .gemini/skills/vibe-scenario-matrix, .github/skills/vibe-scenario-matrix and .opencode/skills/vibe-scenario-matrix in your project.
What does Vibe Scenario Matrix need to run?
SKILL.md names no scripts, command-line tools or credentials: Vibe Scenario Matrix is instructions for the agent only.
Does Vibe Scenario Matrix access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vibe Scenario Matrix safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vibe Scenario Matrix use?
Vibe Scenario Matrix is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibe Scenario Matrix use?
About 695 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vibe Scenario Matrix?
Skills that share tags, products or a category with Vibe Scenario Matrix: Enrich Release Roadmap (trickle-labs/pg-trickle, 148 stars), Verification Gates (rohitg00/skillkit, 1.5k stars), Project Planner (adrianpuiu/claude-skills-marketplace, 100 stars) and Invokta Delivery (vinilana/invokta, 139 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe Scenario Matrix?
ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.
Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.