vc-scenario

Identify edge cases and test scenarios using a 12-dimensional approach.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/lovecrushfamily/Manga2Anime --skill vc-scenario-lovecrushfamily
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-scenario
Source: https://github.com/lovecrushfamily/Manga2Anime/tree/main/.claude/skills/vc-scenario
Command: npx skills add https://github.com/lovecrushfamily/Manga2Anime --skill vc-scenario-lovecrushfamily

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of missing critical edge cases and test scenarios early in the development process, helping prevent costly errors and failures later on.

Core Features & Use Cases

  • Feature Decomposition: Break down features into 12 dimensions to identify potential issues before implementation.
  • Mode Selection: Choose between Simple and Deep modes to generate scenarios based on the complexity of the feature.
  • Risk Assessment: Surface edge cases and risks to inform implementation, testing, and planning.
  • API Design Review: Identify contract edge cases early in the API design process.

Quick Start

Run the 'vc-scenario' Skill with a feature description, like 'Automate the user login process', to generate potential edge cases.

Frequently Asked Questions about vc-scenario

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

FAQPage Schema
How do I identify edge cases and test scenarios for a new software feature?

You can identify edge cases and test scenarios by inputting a feature description into a tool that uses a 12-dimensional decomposition approach. This proactively surfaces potential implementation risks and API design contract issues early in software development.

What is the best way to uncover API design risks before implementation?

The best way to uncover API design risks is by performing an API design review using a 12-dimensional feature decomposition. This process identifies contract edge cases early, preventing costly errors and failures during later software development stages.

How do I generate simple versus deep test scenarios for complex code paths?

You can generate simple or deep test scenarios by selecting between Simple and Deep modes based on your feature's complexity. This mode selection tailors the risk assessment and edge case generation to match the specific requirements of your code paths.

Can I use feature decomposition for risk assessment in software development?

Yes, you can use feature decomposition for risk assessment by breaking down features into 12 distinct dimensions. This approach surfaces edge cases and potential risks to directly inform your implementation, testing, and project planning phases.

When do I need a 12-dimensional approach to find missing test scenarios?

You need a 12-dimensional approach when standard reviews fail to capture missing critical edge cases early in development. It systematically breaks down features to ensure comprehensive risk assessment and prevents costly failures later.