ck:scenario

Decompose features into 12 dimensions and generate severity-labeled edge-case scenarios.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/mafvietnam/mafapp --skill ck-scenario-mafvietnam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:scenario
Source: https://github.com/mafvietnam/mafapp/tree/main/.claude/skills/ck-scenario
Command: npx skills add https://github.com/mafvietnam/mafapp --skill ck-scenario-mafvietnam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Devising thorough test coverage and design risk assessment early by enumerating edge cases across multiple dimensions.

Core Features & Use Cases

  • Systematic edge-case generation across 12 dimensions to surface gaps before implementation.
  • Generates 3–5 scenarios per relevant dimension with severity labels to guide testing.
  • Provides a structured, portable scenario report to feed into test planning and risk assessment.

Quick Start

Analyze a feature description or code path and generate 3–5 edge-case scenarios across applicable dimensions, returning a structured table as output.

Frequently Asked Questions about ck:scenario

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

FAQPage Schema
How do I generate edge-case scenarios for feature testing?

Decomposing a feature into 12 dimensions provides systematic edge-case scenario generation, producing 3 to 5 scenarios per dimension with severity labels. This structured approach surfaces testing gaps and design risks early in the development lifecycle.

What is the best way to assess design risks during early planning?

Generating a portable scenario report across 12 dimensions provides 3 to 5 edge-case scenarios per relevant dimension, labeled by severity, to guide risk assessment workflows. This approach systematically identifies design risks during early planning stages.

Can I use generated edge-case scenarios for test planning?

Generated edge-case scenarios can be integrated into test planning by utilizing the structured table output directly within your workflows. The scenarios include severity labels to help prioritize testing efforts across applicable dimensions.

How many testing scenarios are generated per dimension?

The generation process produces 3 to 5 edge-case scenarios per relevant dimension. Each scenario is assigned a severity label to help prioritize testing and risk assessment efforts across the 12 identified dimensions.

Does systematic scenario generation work without external dependencies?

Systematic scenario generation works without external dependencies, requiring only a feature description or code path to analyze. It outputs a structured table of edge-case scenarios suitable for immediate integration into testing workflows.