ck:scenario

Generate severity-ranked edge-case scenarios across 12 dimensions for features.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-scenario-dthuy62
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:scenario
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/ck-scenario
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-scenario-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you uncover hidden edge cases, failure modes, and test gaps before implementation or release, reducing the chance of late-stage bugs and missed risks.

Core Features & Use Cases

  • 12-Dimension Decomposition: Breaks a feature or code path into user types, input extremes, timing, scale, state transitions, environment, error cascades, authorization, data integrity, integration, compliance, and business logic.
  • Severity-Ranked Scenarios: Produces Critical, High, Medium, and Low scenarios so you can prioritize the most dangerous risks first.
  • Practical Use Cases: Ideal for planning a new API, reviewing a stateful workflow, designing tests for a complex UI, or stress-checking a third-party integration before launch.

Quick Start

Ask the ck:scenario skill to analyze your feature or file path and produce a structured edge-case report with ranked scenarios and expected behavior.

Frequently Asked Questions about ck:scenario

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

FAQPage Schema
How do I find edge cases for an API before implementation?

Edge case analysis works by applying a 12-dimension decomposition to user flows, stateful logic, and integrations. It evaluates input extremes, timing, and error cascades to produce a structured report with severity-ranked scenarios and expected behavior.

What is the best way to identify test scenarios for stateful workflows?

The best way to identify test scenarios for stateful workflows is breaking the logic into state transitions, data integrity, and timing dimensions. This yields Critical, High, Medium, and Low severity scenarios to prioritize dangerous risks first.

Can I use scenario decomposition for code review of complex integrations?

Yes, you can use scenario decomposition during code review for complex integrations. It analyzes authorization, data integrity, and error cascades to uncover hidden failure modes and test gaps in third-party integrations before release.

Does edge case generation work for pre-implementation planning of user flows?

Edge case generation works for pre-implementation planning by analyzing user types, business logic, and compliance dimensions. It produces a structured report that highlights missed risks and expected behavior before you write any code.

How do you prioritize risk analysis when designing tests for a new feature?

You prioritize risk analysis by generating severity-ranked scenarios categorized as Critical, High, Medium, and Low. This structured reporting exposes the most dangerous risks early, ensuring test design focuses on high-priority failure modes first.

What limitations should I consider when analyzing edge cases for compliance and scale?

When analyzing edge cases for compliance and scale, consider that scenario coverage depends on the provided feature context. The 12-dimension decomposition relies on your input accuracy to effectively expose risks across environment and scale dimensions.