ck:scenario

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

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/hotriluan/alkana_web --skill ck-scenario
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:scenario
Source: https://github.com/hotriluan/alkana_web/tree/main/.opencode/skills/ck-scenario
Command: npx skills add https://github.com/hotriluan/alkana_web --skill ck-scenario

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose any feature or code path across 12 dimensions to surface edge cases, risks, and test targets before implementation begins.

Core Features & Use Cases

  • 12-dimension edge-case exploration to surface risks
  • Scenario generation for planning, design reviews, and testing
  • Structured output to guide implementation and QA

Quick Start

Decompose a given feature into 12 dimensions and generate 3–5 scenarios per relevant dimension.

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 test scenarios for a new feature?

Edge-case test scenarios are generated by decomposing a target feature across 12 dimensions, including user types, input extremes, timing, and data integrity. This process produces a structured table with 3–5 scenarios per relevant dimension and severity levels to guide QA.

What is feature decomposition for risk assessment in software testing?

Feature decomposition for risk assessment is a testing method that breaks down a target feature across 12 dimensions to surface edge cases. It identifies risks early by analyzing input extremes, timing, data integrity, and integration points before implementation begins.

Can I use this method for pre-implementation test planning and design reviews?

Yes, you can apply this method to planning, design reviews, or pre-implementation testing. It decomposes features into structured scenario tables with severity levels, ensuring coverage of data integrity and integration dimensions to guide implementation and QA efforts.

How do I identify edge cases across different user types and input extremes?

Identify edge cases by evaluating a feature across 12 specific dimensions, targeting user types and input extremes. The method systematically generates 3–5 scenarios for each relevant dimension to ensure comprehensive risk assessment and test coverage.

What is the best way to structure test scenarios for quality assurance?

The best way to structure test scenarios for quality assurance is using a structured table with severity levels. By decomposing features across 12 dimensions, you generate 3–5 scenarios per dimension, creating a clear output to guide implementation and testing.