メニュー
Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions. Use for pre-implementation risk discovery, QA planning, regression design, and iterative saturation when coverage must be exhaustive.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/hoanghd218/ZaloCRM --skill ak-scenarioコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.
Interview-driven advisory skill. Analyzes a prompt or URL (GitHub issue, spec, doc), scouts the codebase, interviews the user one question at a time to reframe the problem into exact requirements and goals, then delivers honest advice: what to do, what to avoid, better alternatives, benefits and trade-offs. Use when the user asks for advice, a second opinion, a sanity check, requirement reframing before committing to a direction, or wants an existing plan or design pressure-tested (grilled) one question at a time.
Browser and desktop automation through the agent-browser CLI. Use for long autonomous browsing, compact page snapshots, screenshots, form filling, login/test flows without real Chrome profile state, scraping, exploratory QA, cloud browsers, Electron apps, Slack automation, and bug hunts.
| name | ak:scenario |
| description | Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions. Use for pre-implementation risk discovery, QA planning, regression design, and iterative saturation when coverage must be exhaustive. |
| user-invocable | true |
| when_to_use | Invoke to expand requirements into edge cases and QA scenarios. |
| category | utilities |
| keywords | ["edge-cases","test-scenarios","dimensions","saturation","iterations"] |
| argument-hint | <file path or feature description> [--iterations N] [--saturation] |
| metadata | {"author":"agentkit","attribution":"Scenario exploration pattern adapted from autoresearch by Udit Goenka (MIT)","license":"MIT","version":"1.1.0"} |
Decompose any feature or code path across 12 dimensions to surface edge cases, risks, and test targets before implementation begins.
Supports two modes:
--iterations N or --saturation): loop until bounded count or novelty exhausted.--saturation)| Flag | Default | Purpose |
|---|---|---|
--iterations N | — | Bounded loop: run exactly N iterations, then stop with summary |
--saturation | off | Saturation loop: keep iterating until 2 consecutive iterations produce no novel scenarios |
--domain <type> | auto | Domain hint: software, product, business, security, marketing |
--focus <dim> | auto | Prioritize dimension: edge-cases, failures, security, scale |
--format <type> | table | Output format: table, use-cases, test-scenarios, threat-scenarios |
When neither --iterations nor --saturation is set: one-shot mode (original behavior, default).
Not all 12 apply to every feature. Identify relevant dimensions first, then generate scenarios only for those.
| # | Dimension | What to Look For |
|---|---|---|
| 1 | User Types | admin, guest, banned, new user, power user, bot/scraper |
| 2 | Input Extremes | empty, null, max length, unicode, special chars, SQL/script injection |
| 3 | Timing | concurrent access, race conditions, timeout, slow network, retry storms |
| 4 | Scale | 0 items, 1 item, 1M items, pagination boundary, cursor wrap |
| 5 | State Transitions | first use, mid-flow abort, resume after crash, partial completion |
| 6 | Environment | mobile/low-end CPU, no JS, screen reader, proxy/VPN, different timezone/locale |
| 7 | Error Cascades | DB down, API timeout, disk full, OOM, network partition, partial write |
| 8 | Authorization | expired token, wrong role, shared/public link, CORS, CSRF, privilege escalation |
| 9 | Data Integrity | duplicate entries, orphan references, encoding mismatch, concurrent schema migration |
| 10 | Integration | webhook replay, API version mismatch, third-party outage, contract drift |
| 11 | Compliance | GDPR deletion request, audit logging gap, data retention, accidental PII exposure |
| 12 | Business Logic | edge pricing (zero/negative), coupon stacking, refund after partial delivery, free tier limits |
--iterations N or --saturation)Iterative mode runs this saturation loop:
scenario-results.tsv
f. Every 5 iterations: print progress summary (see format below)--iterations N: stop after N iterations--saturation: stop when 2 consecutive iterations produce zero New classificationsForce dimension rotation after 3 consecutive same-dimension iterations. Rotate through: Dimension walk → Combination → Negation → Amplification → Persona shift → Temporal shift
| Level | Meaning |
|---|---|
| Critical | Data loss, security breach, auth bypass, silent corruption |
| High | Feature broken for a subset of users, data inconsistency |
| Medium | Degraded UX, recoverable error not surfaced to user |
| Low | Minor visual glitch, non-blocking warning |
## Scenario Report: [target]
Dimensions analyzed: [list]
Dimensions skipped: [list + reason]
| # | Dimension | Scenario | Severity | Expected Behavior |
|---|-----------|----------|----------|-------------------|
| 1 | Input Extremes | Empty string for required name field | High | Return 400 with field error |
| 2 | Authorization | Expired JWT accessing protected route | Critical | Redirect to login, invalidate session |
| 3 | Timing | Two users submit same form simultaneously | High | Idempotency key or conflict error |
### Summary
- Critical: N
- High: N
- Medium: N
- Low: N
- Total: N scenarios across X dimensions
=== Scenario Progress (iteration 15) ===
Scenarios kept: 12 (8 new, 4 variants)
Discarded: 3 (2 duplicates, 1 out-of-scope)
Dimensions covered: 7/12 (58%)
Edge cases found: 18
Severity: 2 Critical, 4 High, 8 Medium, 4 Low
Coverage gaps: scale, temporal, recovery
scenario-results.tsv)iteration dimension classification severity title description parent
1 happy_path new - Successful checkout User completes standard checkout -
2 error_path new HIGH Payment declined Card rejected during checkout -
3 edge_case duplicate - Empty cart Already covered by #1 #1
## Scenario Report: [target] (iterations: N)
[Full table of kept scenarios, grouped by dimension]
### Coverage Matrix
[dimension × severity grid]
### Composite Score: NNN
scenarios_generated * 10 = X
edge_cases_found * 15 = X
dimensions_covered * 30 = X
unique_actors * 5 = X
high_severity * 3 = X
### Saturation
Halted: [after N iterations — bounded] | [saturation — 2 consecutive iterations with no novel cases]
| Next Step | Skill | How |
|---|---|---|
| Generate test cases from scenarios | ak:test | Pass scenario table as input context |
| Inform implementation plan risks | ak:plan | Paste Critical/High rows into risk assessment |
| Deep persona debate on top risks | ak:predict | Feed Critical scenarios as the change proposal |
Saturation loop mechanics, novelty detection, and generation strategy are embedded in the iterative-mode instructions above.
# One-shot (default — backwards compatible)
/ak:scenario src/api/payment.ts
/ak:scenario "User registration with OAuth providers"
# Bounded iterative — exactly 25 iterations
/ak:scenario src/api/payment.ts --iterations 25
# Saturation — stop when coverage exhausted
/ak:scenario "Add multi-tenancy to the database layer" --saturation
# Saturation with domain hint for priority dimension ordering
/ak:scenario src/middleware/auth.ts --saturation --domain security
Faithful absorption (in scope) of upstream /autoresearch:scenario (uditgoenka/autoresearch, MIT). The local version supports both one-shot generation and the iterative saturation loop (closed in #729).
See /ak:autoresearch for the full family map.