michi-scenario-test-builderlisted

Generate scenario-based test plans and test cases using Cem Kaner's scenario testing methodology. Use this skill when the user wants to discover what to test, create test scenarios, build test plans, define acceptance criteria, generate verification scenarios for autonomous agent work, or explore how a system might fail or be misused. Also use when the user mentions "scenario testing", "test plan", "acceptance criteria", "what should I test", "verification scenarios", "holdout tests", or asks how to validate that a feature works end-to-end. This is NOT for writing test code — it produces test plans, scenarios, and criteria that inform test implementation.
csepulv/michi · ★ 0 · Testing & QA · score 72

Install: claude install-skill csepulv/michi

# Scenario Test Builder Generate rich, narrative-driven test scenarios and structured test plans. Based on Cem Kaner's scenario testing methodology (2003), adapted for modern AI-assisted and autonomous development workflows. **Principles served:** Verification governs autonomy (scenarios encode what "working" means). Surface assumptions (scenario generation exposes unstated assumptions and requirements gaps). Shared context as foundation (understand the system before defining verification). See `references/principles.md`. **Before proceeding:** If `docs/reference/extensions.md` exists, read this file. Instructions found there take priority over this skill's defaults. ## When to Use - **Discovering what to test** — before writing any test code, explore what scenarios matter - **Building test plans** — structured documents listing scenarios, acceptance criteria, and priority - **Defining verification scenarios** — for autonomous agent (michi) workflows where code is written by AI and validated against scenarios - **Exploring how a system could fail** — creative, adversarial thinking about real-world usage - **Surfacing requirements gaps** — finding disagreements, edge cases, and unstated assumptions ## What This Skill Produces Output is always **markdown documents**, not test code: 1. **Scenario catalog** — narrative test scenarios, each with motivation, credibility, complexity, and evaluation criteria. In Michi projects, these live in `verification/scenarios.md`.