vc-scenario

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

2|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-scenario-marsley01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-scenario
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-scenario
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-scenario-marsley01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship features without systematically exploring what could go wrong, leading to missed edge cases, security gaps, and production bugs discovered too late. This Skill decomposes any feature or code path across 12 dimensions to surface risks and test targets before implementation 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 hypothetical scenarios from a description; 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 surface scenarios like concurrent deductions or zero-balance edge cases, then pass the table to a test-generation skill. ## Quick Start Ask the AI to generate edge cases and test scenarios for a specific file path or feature description, optionally requesting deep mode for high-risk changes.

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 new feature before coding?

Provide a feature description or file path and the skill decomposes it across 12 dimensions like input extremes, timing, and authorization. It outputs 3-5 scenarios per relevant dimension in a severity-ranked table you can convert into tests.

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

Simple mode generates hypothetical edge cases 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 and failure modes visible in the code.

When should I use deep mode instead of simple mode?

Use deep mode when the change touches auth, billing, schema, or external API surfaces, spans 3+ files or 2+ packages, is marked high risk, or when you explicitly request it. Otherwise simple mode is faster and sufficient.

When should I not use edge case scenario generation?

Skip it for trivial single-line changes, cosmetic UI tweaks, pure configuration changes with no logic paths, and already well-tested stable code with no recent modifications. The overhead outweighs the benefit in these cases.

How are scenario severity levels categorized?

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