ck:scenario

Decompose features across twelve dimensions to generate edge-case test scenarios.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-scenario-nam3886
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:scenario
Source: https://github.com/nam3886/golang-echo-boilerplate/tree/main/.claude/skills/ck-scenario
Command: npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-scenario-nam3886

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill uncovers hidden edge cases, risks, and test targets by decomposing features and code paths across twelve dimensions so teams catch issues early in planning, design, and before implementation.

Core Features & Use Cases

  • 12-dimensional decomposition covering user types, input extremes, timing, scale, state transitions, environment, error cascades, authorization, data integrity, integration, compliance, and business logic.
  • Structured scenario generation that produces 3–5 concrete scenarios per relevant dimension and assigns severity levels (Critical/High/Medium/Low).
  • Integration-ready outputs formatted as a clear scenario table for use in test generation, risk registers, implementation plans, and code reviews. Use case: Generate a scenario report for a new payment flow to identify concurrency, authorization, and data integrity risks before coding.

Quick Start

Generate a scenario report for "User registration with OAuth providers" covering all relevant decomposition dimensions.

Frequently Asked Questions about ck:scenario

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

FAQPage Schema
How do I generate test scenarios for edge cases and risk assessment?

Generate test scenarios by decomposing features across twelve dimensions like user types, input extremes, and state transitions. This systematic decomposition produces 3 to 5 scenarios per dimension and assigns severity levels to surface hidden risks before implementation.

What is feature decomposition for test planning and when do I need it?

Feature decomposition for test planning breaks down complex code paths across twelve dimensions including timing, scale, and error cascades. You need this during feature planning, API design reviews, and pre-test scenario generation to catch hidden edge cases early.

Can I use scenario generation for complex stateful implementations?

Scenario generation directly supports complex or stateful implementations by analyzing state transitions, data integrity, and integration dimensions. It outputs a structured table of concrete scenarios labeled by severity for downstream test generation.

How do I classify severity for edge cases in code review risk assessment?

Classify edge case severity during code review risk assessment using Critical, High, Medium, and Low labels. The decomposition process assigns these severity levels to each generated scenario, helping prioritize implementation risks across authorization, compliance, and business logic dimensions.

What's the best way to identify concurrency and data integrity risks in API design?

Identify concurrency and data integrity risks in API design by applying 12-dimensional decomposition to generate scenario reports. This approach systematically evaluates timing, scale, and error cascades to produce structured, integration-ready scenario tables for risk registers.