Automates the setup and navigation of the spec-kit demo environment across different project phases.

Install

mkdir -p .claude/skills/demo && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14303" && unzip -o skill.zip -d .claude/skills/demo && rm skill.zip

Installs to .claude/skills/demo

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Bootstrap and navigate the spec-kit demo environment. Use this when asked to set up the demo, bootstrap the demo, jump to a phase, go to a phase, switch phases, or clean up a demo.
180 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Bootstrap a new demo environment using git worktrees
  • Navigate between different demo phases while preserving uncommitted work
  • Reset a demo phase by discarding changes
  • Clean up a demo environment by removing folders, branches, and stashes
  • Create checkpoint worktrees for offline resilience
  • Open the live worktree in a code editor

How it works

The skill manages a staged demo environment by creating git worktrees for each phase, allowing users to set up, switch between, and clean up demo states. It stashes uncommitted changes when switching phases and restores them upon return.

Inputs & outputs

You give it
A request to set up, jump to a phase, or clean up a demo
You get back
A configured demo environment, a switched demo phase, or a cleaned-up environment

When to use demo

  • Bootstrap a new demo instance
  • Switch demo to a new phase
  • Clean up temporary demo environments

About this skill

Demo Skill

This skill manages the spec-kit staged demo environment using git worktrees and phase tags.

When to Use

Use this skill when the user asks to:

  • Set up / bootstrap / prepare the demo
  • Jump to / go to / switch to a phase
  • Clean up / delete / remove a demo
  • Reset the demo

Setup

Run from the repository root to create the demo environment:

# Auto-numbered (demo-01, demo-02, etc.)
.\.github\skills\demo\setup-demo.ps1

# Named demo
.\.github\skills\demo\setup-demo.ps1 -Name mcaps

This creates a demo folder (e.g., ../sdd-health-plan-chat-mcaps/) containing:

  1. live/ — Editable worktree for the demo
  2. phase-00-init/, phase-01-constitution/, etc. — Checkpoint worktrees (for offline resilience)

Setup Options

OptionDescription
-Name <name>Name for the demo (creates <repo>-<name>)
-SkipCheckpointsCreate only the live worktree
-ResetRemove existing worktrees and recreate
-WorktreeRoot <path>Override full path for demo folder

Jump to Phase

From within the live worktree, jump between phases while preserving work:

.\.github\skills\demo\jump-to-phase.ps1 -Phase <phase>

Safety:

  • The script refuses to run on main/master.
  • In a demo worktree, it runs without extra prompts.
  • Outside a worktree, it prints a warning (because changes may affect your main repo).

State preservation: When jumping away from a phase, uncommitted changes are stashed. When returning, they're automatically restored.

Stash identity: Stashes are labeled as demo[<name>]:<phase-tag>.

  • If you are on a demo/<name> branch, <name> comes from the branch.
  • Otherwise (common in spec-kit demos), <name> is derived from the demo folder name (e.g., ../sdd-health-plan-chat-dry-run/livedry-run).

Phase Identifiers

NumberNameTag
0initphase/00-init
1constitutionphase/01-constitution
2specphase/02-spec
3planphase/03-plan
4tasksphase/04-tasks
5.1setupphase/05-implement/01-setup
5.2foundationalphase/05-implement/02-foundational
5.3us1phase/05-implement/03-ask-plan-questions
5.4us2phase/05-implement/04-handle-missing-answers
5.5us3phase/05-implement/05-ui
5.6docsphase/05-implement/06-documentation

Jump Options

OptionDescription
-Phase <id>Phase number, name, or full tag
-ResetDiscard changes instead of stashing; skip restore

Examples

# Jump to plan phase (preserves current work)
.\.github\skills\demo\jump-to-phase.ps1 -Phase plan

# Jump to phase 5.3 and discard changes
.\.github\skills\demo\jump-to-phase.ps1 -Phase 5.3 -Reset

# Jump using full tag name
.\.github\skills\demo\jump-to-phase.ps1 -Phase phase/03-plan

After Setup

  1. Open the live worktree: code ../sdd-health-plan-chat-<name>/live
  2. Jump between phases as needed during the demo
  3. Use -Reset on setup-demo.ps1 to start fresh

Cleanup

Remove a demo environment (folders, branch, and stashes):

# Clean up a specific demo
.\.github\skills\demo\cleanup-demo.ps1 -Name mcaps

# Clean up all demos
.\.github\skills\demo\cleanup-demo.ps1 -All

Cleanup Options

OptionDescription
-Name <name>Name of the demo to remove
-AllRemove all demo environments
-KeepStashesPreserve stashes (only remove folders and branches)

When not to use it

  • When running the `jump-to-phase.ps1` script on `main`/`master` branches

Limitations

  • The `jump-to-phase.ps1` script refuses to run on `main`/`master`

How it compares

This skill uses git worktrees to manage distinct demo phases, preserving work and state across transitions, which is more structured and resilient than manually managing branches or copying directories for each demo stage.

Compared to similar skills

demo side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
demo (this skill)06moNo flagsIntermediate
tmux202moReviewIntermediate
jira116moNo flagsBeginner
triaging-issues52moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry