skills.rest
quanganh208
quanganh208COMMUNITY
Explore all skills by this author →
GitHub

ck:scenario

Generate edge case scenarios with severity labels for feature or code path reviews.

1|Updated Mar 6, 2026
Search Tags:#decomposition#edge-cases#risk-assessment#test-planning#scenario-generation#severity-classification
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-scenario-quanganh208
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:scenario
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/ck-scenario
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-scenario-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and engineers systematically surface hidden edge cases, risks, and test targets by decomposing a feature or code path across twelve dimensions so issues are caught earlier in design, implementation, and review.

Core Features & Use Cases

  • Dimension-driven decomposition: Walk through user types, input extremes, timing, scale, state transitions, environment, error cascades, authorization, data integrity, integration, compliance, and business logic to identify relevant failure modes.
  • Scenario generation: Produce 3–5 concrete scenarios per relevant dimension with clear severity classification (Critical / High / Medium / Low).
  • Structured output for handoff: Emit a tabular scenario report with expected behavior and a severity summary suitable for test plans, risk logs, or as input to downstream skills like ck:test and ck:plan.

Quick Start

Use ck:scenario to analyze "User registration with OAuth providers" and generate a scenario table with relevant dimensions and severity labels.

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 and identify edge cases for a new feature?▼

To generate test scenarios and identify edge cases, decompose the feature across twelve dimensions including user types, input extremes, timing, scale, and environment. This produces a structured scenario table with severity labels and expected behaviors for comprehensive test planning.

What is feature decomposition for risk assessment and when do I need it?▼

Feature decomposition for risk assessment systematically breaks down a code path across twelve dimensions like state transitions, error cascades, and data integrity to surface hidden failures. You need it during pre-implementation reviews, test design, and code review to catch issues early.

Can I use scenario generation for test planning on complex integrations and compliance logic?▼

Yes, scenario generation for test planning covers integration and compliance dimensions specifically. It evaluates failure modes across authorization, data integrity, and business logic, outputting a severity summary suitable for risk logs and downstream test automation.

What's the best way to structure test cases by severity for downstream automation?▼

The best way to structure test cases by severity is using a tabular scenario report that classifies each case as Critical, High, Medium, or Low. This structured output includes expected behaviors and severity summaries, making it ideal for direct handoff to test automation.

Does scenario-based risk assessment work without external dependencies or specific frameworks?▼

Scenario-based risk assessment works standalone without requiring external dependencies or specific testing frameworks. It analyzes the feature logic directly to produce structured severity labels and expected behaviors, requiring only the feature description or code path as input.

Related Skills

Explore More Software Engineering Skills→
Intense-VisionsIntense-Visions
18

harness-product-spec

Generate structured product specifications with EARS acceptance criteria from GitHub issues.

Official
Advanced
hidonguyenhidonguyen

ck:scenario

Generate edge case lists and test scenarios with severity labels.

Community
Intermediate
NeoLabs-SystemsNeoLabs-Systems
23

subagent-driven-development

Dispatch fresh subagents for task execution and two-stage code review.

Official
Advanced
AZANIRAZANIR
2

qa-manual-test-designer

Design manual test cases and exploratory testing charters using specification-based techniques.

Community
Intermediate