Rapid clarification interview for an existing bead (3-10 questions)
Conducts a rapid 3-10 question clarification interview for an existing bead. Use this when you need to quickly refine specifications or requirements for a bead you've already created.
/plugin marketplace add aperepel/claude-spec-builder/plugin install claude-spec-builder@claude-spec-builderWhen the user runs /blitz, conduct a rapid clarification interview on an existing bead.
/blitz <bead-id> # Blitz interview for specific bead
/blitz bd-a3f8 # Example with root bead
/blitz bd-a3f8.2 # Example with subtask
The <bead-id> argument is required and must match valid bead ID format:
bd-xxxx (4 hex characters)bd-xxxx.n (with subtask number)bd-xxxx.n.m (nested subtask)If no argument provided:
Usage: /blitz <bead-id>
Run `bd list` to see available beads, or use /interview for new specs.
If invalid format:
Invalid bead ID format: '<input>'. Expected: bd-xxxx or bd-xxxx.n
/interview --blitz <bead-id>references/bead-context.md for context loadingtts-status skill (see TTS Integration below)bd updateCRITICAL: To detect TTS, invoke the skill - do NOT use curl or HTTP requests.
Invoke skill: claude-mlx-tts:tts-status
DO NOT:
curl to probe HTTP endpointsBehavior:
/say for questions/tts-start, retry⚠️ Visual output is MANDATORY regardless of TTS state.
TTS is SUPPLEMENTARY - it adds voice ON TOP OF visual output. Every message that is voiced MUST also be printed to the terminal. TTS never replaces text output.
/blitz <bead-id> is equivalent to /interview --blitz <bead-id>.
The blitz command exists as a convenient shorthand for the common case of clarifying existing beads. Use /interview for new specs or when you want the full interview experience.
See the interview skill for detailed blitz mode logic.