Agent skill · duc01226
demo-guide
[Documentation] Use when you need to generate a step-by-step demo guide (demo script / walkthrough) covering all main user stories and their test cases — scope from a named feature, else the current working context, else confirm with the user — explaining for each case how the domain data is stored/changed and how the domain solves the feature. Triggers: demo guide, generate demo guide, demo script, demo walkthrough, how to demo, prepare demo, sprint demo, user story demo.
What it needs
About 12k tokens when loaded.
What this skill does
<!-- PROMPT-ENHANCE:STEP-TASK-ANCHOR:START --> [BLOCKING] Execute skill steps in declared order. NEVER skip, reorder, or merge steps without explicit user approval. [BLOCKING] Before each step or sub-skill call, update task tracking: set inprogress when step starts, set completed when step ends. [BLOCKING] Every completed/skipped step MUST include brief evidence or explicit skip reason. [BLOCKING] If Task tools are unavailable, create and maintain an equivalent step-by-step plan tracker with the same status transitions. <!-- PROMPT-ENHANCE:STEP-TASK-ANCHOR:END --> Quick Summary Goal: UNDERSTAND the feature first, then script it — investigate the capability end-to-end until you can answer the comprehension bar with file:line, and only then produce a stakeholder-ready demo guide that lists every main user story with its REAL test-case IDs, gives a step-by-step demo flow per case, explains how the domain stores/changes the data and how that solves the feature, and places every case on the proof ladder — so the presenter can show the behaviour, explain the data behind it, and never claim proof that was not earned. Summary — read this if nothing else. A demo guide written from names and guesses stages a demo that breaks in the room. So: investigate first, prove every claim, then write. Main steps, in order: 1. RESOLVE scope — prompt → current working context → AskUserQuestion. NEVER invent the feature silently. 2. LOAD the contract (references/demo-guide-template.md) and SIZE the target into a tier S0–S4; announce both in one line. 3. DECOMPOSE into story groups (≥2 from tier S2) and BREAK THE WORK INTO TASKS before the first deep read — TaskList first; a group task completes only when its block is on disk. 4. [BLOCKING GATE] UNDERSTAND the feature — clear the 6-question comprehension bar with file:line each, delegating to read-only investigation skills (/scout, /investigate, /debug-investigate, /graph-trace, /spec-index) when a direct read cannot answer one. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills duc01226/demo-guide--f59650