vc-scenario

Generates edge cases and test scenarios by decomposing features across 12 risk dimensions.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-scenario-hyusecs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-scenario
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-scenario
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-scenario-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship features without systematically exploring what could go wrong, leading to missed edge cases, late-discovered bugs, and incomplete test coverage. This Skill decomposes any feature, file, or checklist item across 12 dimensions (input extremes, timing, authorization, data integrity, and more) to surface risks before implementation or testing begins. ## Core Features & Use Cases - 12-Dimension Decomposition: Analyzes features across user types, input extremes, timing, scale, state transitions, environment, error cascades, authorization, data integrity, integration, compliance, and business logic. - Simple and Deep Modes: Simple mode generates scenarios from descriptions alone; Deep mode spawns a research subagent to read actual source code and produce scenarios referencing real function signatures and failure modes. - Severity-Ranked Output: Produces a structured scenario table categorized as Critical, High, Medium, or Low, ready to feed into test generation or risk assessment. - Use Case: Before implementing a credit-deduction feature touching billing code, run Deep mode to uncover scenarios like concurrent deductions or partial balance states that generic brainstorming would miss. ## Quick Start Ask the assistant to run vc-scenario on a file path or feature description, for example to explore edge cases for the user registration flow before writing tests.

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 cases for a feature before implementation?

Provide a file path or feature description and the skill decomposes it across 12 dimensions such as input extremes, timing, and authorization. It outputs a severity-ranked table of scenarios you can use directly as test targets.

What is the difference between simple mode and deep mode for scenario generation?

Simple mode generates hypothetical scenarios from the description alone, while deep mode spawns a research subagent that reads the actual source files and tests. Deep mode produces scenarios referencing real variable names, function signatures, and visible failure modes.

When should I use deep mode instead of simple mode?

Deep mode triggers automatically when a change touches auth, billing, schema, or external API surfaces, spans 3 or more files, or is marked high risk. You can also request it explicitly for any change where reading the real code matters.

When should I not use edge case scenario generation?

Skip it for trivial single-line changes, cosmetic UI tweaks, pure configuration changes, and already well-tested stable code. The 12-dimension analysis adds no value when there are no meaningful logic paths to explore.

How are scenario severity levels determined?

Scenarios are ranked Critical for data loss or security breaches, High for broken functionality or data inconsistency, Medium for degraded UX or unhandled recoverable errors, and Low for minor visual or non-blocking issues.