Demo Prep
Create a demo script for "$ARGUMENTS". Define the audience, build a narrative flow, write talking points for each feature, prepare for questions, and create a fallback plan.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"project-management-demo-prep","workflow":"project-management","phase":3,"project":"<project>","event":"skipped","artifact":"03-review.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 3 (Review) of the Scrum workflow (project-management); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or project-management when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"project-management-demo-prep","workflow":"project-management","phase":3,"project":"<project>","event":"refused","artifact":"03-review.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"project-management-demo-prep","workflow":"project-management","phase":3,"project":"<project>","event":"started","artifact":"03-review.md","note":""}.
Check that .singularskills/project-management/<project>/00-initiate.md exists. If it does not, tell the user to run an Initiate skill first (e.g., project-charter) and stop.
Process
Read existing context:
- Read
.singularskills/project-management/<project>/00-initiate.mdfor stakeholder map and project context - Read
.singularskills/project-management/<project>/03-review.mdif it exists (for sprint review and completed features) - Read
.singularskills/project-management/<project>/02-sprint.mdif it exists (for sprint state and delivery details) - Read
.singularskills/project-management/<project>/01-plan.mdif it exists (for backlog and feature descriptions)
- Read
Define demo audience and what they care about:
- Identify who will attend the demo (executives, engineers, users, product team, external stakeholders)
- For each audience segment, define what they care about:
- Executives: outcomes, business impact, timeline, budget implications
- Engineers: how it works, architecture decisions, technical trade-offs
- Users: what it does for them, workflow improvements, ease of use
- Product team: alignment with roadmap, user feedback, next priorities
- Choose a primary audience to optimize the framing for (adjust depth and language accordingly)
Create demo flow:
- Select features to demo and order them to build a narrative (do not just list features randomly)
- Start with the most impactful or visible feature to hook the audience
- Build logically: show features in the order a user would encounter them, or by theme
- End with a forward-looking item (what is coming next) to maintain momentum
- Allocate time per feature: 2-3 minutes each, total demo 15-20 minutes
- Leave 10 minutes for questions and discussion at the end
Write talking points for each feature:
- For each feature in the demo flow, write:
- Opening line: benefit-first statement ("This lets users do X 50% faster")
- What to show: specific actions to perform in the demo (click here, enter this, see that)
- Key takeaway: the one thing the audience should remember about this feature
- Transition: how to smoothly move to the next feature
- Keep talking points concise — bullet points, not paragraphs
- Avoid jargon for non-technical audiences; use precise terms for technical audiences
- For each feature in the demo flow, write:
Prepare for common questions and objections:
- Anticipate 5-10 questions the audience is likely to ask
- For each question, prepare a concise answer (2-3 sentences maximum)
- Common categories: timeline ("when will this be in production?"), scope ("can it also do X?"), risk ("what if Y fails?"), comparison ("how is this different from Z?")
- Prepare deflection responses for questions that need follow-up ("Great question — let's schedule time to dig into that")
- Identify any sensitive topics to avoid or handle carefully
Create fallback plan if live demo fails:
- Prepare screenshots or screen recordings of the demo flow as backup
- If using a staging environment, have a local or pre-recorded backup ready
- Know which features are most stable and which are risky to demo live
- Have a recovery script: if something breaks mid-demo, what do you say and do?
- Test the demo environment before the meeting (connectivity, data, credentials)
Time the demo:
- Target total time: 15-20 minutes for demo, 10 minutes for questions (30 minutes total)
- Allocate time per section: intro (2 min), features (2-3 min each), wrap-up (2 min), Q&A (10 min)
- Mark optional features that can be skipped if running long
- Mark must-show features that cannot be cut
Write the artifact — append to
.singularskills/project-management/<project>/03-review.mdunder a## Demo Prepsection. Create the file with a# Review — <project>heading if it does not exist; if a## Demo Prepsection already exists, replace only that section. The section contains:- Audience — who is attending and what they care about
- Demo Flow — ordered list of features with time allocation
- Talking Points — per-feature opening line, what to show, key takeaway, and transition
- Q&A Preparation — anticipated questions with answers
- Fallback Plan — backup strategy if live demo fails
- Timing — total time, per-section allocation, must-show vs. optional features
Output
Demo prep appended to .singularskills/project-management/<project>/03-review.md. Present a summary highlighting:
- Target audience and framing approach
- Number of features in the demo flow
- Total demo time and Q&A allocation
- Top 3 anticipated questions
- Fallback plan status (screenshots/recordings ready or needed)
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"project-management-demo-prep","workflow":"project-management","phase":3,"project":"<project>","event":"finished","artifact":"03-review.md","note":""}.
This artifact is shared by every skill of phase 3 (Review). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Review
workflow: project-management
phase: 3
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Demo Prep section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is project-management-demo-prep).
End your section with ### Decisions and ### Open questions (one level under your ## Demo Prep heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>