vc:scenario

Decompose features across 12 dimensions to generate edge-case scenarios with severity categorization.

Updated May 10, 2026

Search Tags:#testing #scenarios #risk-assessment #generate #edge-case

Ready to run

npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-scenario

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vc:scenario
Source: https://github.com/cryborg1211/quant_trading_telegram_bot/tree/main/.agents/skills/vc-scenario
Command: npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-scenario

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

vc:scenario helps teams surface edge cases and testing targets by decomposing features across 12 dimensions, enabling earlier risk detection before implementation.

Core Features & Use Cases

Decomposes features along 12 dimensions to surface relevant edge cases.
Generates 3–5 scenarios per applicable dimension and categorizes severity.
Outputs a structured scenario report that guides testing, API design, and planning.

Quick Start

Provide a target feature file path or description to generate edge-case scenarios.

Frequently Asked Questions about vc:scenario

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate edge-case test scenarios for a feature?▼

Edge-case test scenarios are generated by parsing a target feature file and decomposing it across 12 predefined dimensions. This process produces a structured report containing 3–5 categorized scenarios per relevant dimension to guide testing.

What is feature decomposition for risk assessment in testing?▼

Feature decomposition for risk assessment is a technique that breaks down a feature across 12 dimensions to identify edge cases. It enables earlier risk detection before implementation by categorizing scenario severity for testing and API design.

Can I use this to generate test scenarios for API contract design?▼

Yes, you can generate test scenarios for API contract design. The tool applies dimension-based decomposition to API contracts, producing 3–5 edge-case scenarios per dimension with severity categorization to guide API planning.

What's the best way to identify edge cases before implementation?▼

The best way to identify edge cases before implementation is to decompose the feature across 12 dimensions. This approach surfaces 3–5 scenarios per applicable dimension with severity categorization, enabling earlier risk detection during feature design.

How many testing scenarios does it generate per dimension?▼

It generates 3–5 testing scenarios per applicable dimension. Each scenario includes severity categorization to help prioritize testing targets and guide the structured scenario report output.

Does it require any specific testing framework to run?▼

No specific testing framework is required to run it. The tool operates by parsing a target feature file path or description and using a predefined dimension set to produce a structured scenario report, independent of testing dependencies.