scenario-design-docs

Generates technical design documents and QA scenario appendices through one-question-at-a-time interviews.

1|Updated Dec 18, 2009
One-click install
npx skills add https://github.com/thurn/dotfiles --skill scenario-design-docs-thurn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scenario-design-docs
Source: https://github.com/thurn/dotfiles/tree/main/.llms/skills/scenario-design-docs
Command: npx skills add https://github.com/thurn/dotfiles --skill scenario-design-docs-thurn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Short feature prompts often hide ambiguities that surface only during implementation or QA. This Skill resolves those ambiguities upfront by interviewing the user one question at a time, scenario-testing expected behavior, and producing a standalone technical design document plus a QA-ready scenario appendix before any code is written. ## Core Features & Use Cases - Interview-Led Design Discovery: Asks exactly one substantive question per message with a recommended answer, labeled multiple-choice options, and a marked [SUGGESTED] choice. - Scenario Testing: Simulates realistic usage paths (CLI commands, API requests, UI states, side effects) at empirical verification level to expose hidden decisions. - Dual Document Output: Writes a standalone design document and a cross-linked scenario appendix usable directly for manual QA and acceptance review. - Use Case: Given a prompt like "add a retry mechanism to the upload service", the Skill interviews you through failure modes, backoff behavior, and observability, then delivers a complete design doc and scenario appendix covering retries, partial failures, and edge cases. ## Quick Start Use scenario-design-docs to turn my feature idea into a technical design document and QA scenario appendix through a step-by-step interview.

Frequently Asked Questions about scenario-design-docs

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

FAQPage Schema
How do I write a technical design document from a short feature idea?▼

Invoke this Skill with your feature prompt and it interviews you one question at a time, recommending answers and scenario-testing behavior. It then writes a standalone design document and a scenario appendix to /tmp/docs with dated filenames.

What is scenario testing in software design?▼

Scenario testing walks through realistic usage paths and simulates expected behavior at empirical verification level, including exact commands, outputs, exit codes, and side effects. This Skill uses it throughout the interview to expose ambiguities before documentation.

Does this Skill write implementation code or project scaffolding?▼

No. It is explicitly a design skill, not an implementation skill. It produces a design document and scenario appendix describing what to build and how it must behave, then stops unless you ask for implementation planning.

Can the scenario appendix be used for manual QA testing?▼

Yes. The appendix contains scenario records with preconditions, inputs, actions, expected behavior, side effects, and verification methods detailed enough for manual QA or acceptance review, including negative and edge cases.

When should I not use an interview-led design process?▼

Avoid it for trivial changes where the behavior is already fully understood, or when you need implementation sequencing. The Skill deliberately excludes milestones, phases, and MVP breakdowns, which belong to separate implementation planning.