Interactive specification interview workflow for Claude Code
npx claudepluginhub blencorp/lisaInteractive specification interview workflow that conducts in-depth feature interviews using AskUserQuestion and generates comprehensive specs. Lisa plans. Ralph does.
Claude Code marketplace entries for the plugin-safe Antigravity Awesome Skills library and its compatible editorial bundles.
Production-ready workflow orchestration with 79 focused plugins, 184 specialized agents, and 150 skills - optimized for granular installation and minimal token usage
Curated collection of 141 specialized Claude Code subagents organized into 10 focused categories
Lisa plans. Ralph does.
Interactive specification interview workflow that conducts in-depth feature interviews and generates comprehensive specs. Available as both a Claude Code plugin and a standalone CLI that works with multiple AI providers.
Based on the technique described by @trq212:
My favorite way to use Claude Code to build large features is spec based. Start with a minimal spec or prompt and ask Claude to interview you using the AskUserQuestion tool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. Then make a new session to execute the spec.
Lisa automates this workflow by:
# Add the marketplace
/plugin marketplace add blencorp/lisa
# Install the plugin
/plugin install lisa
The CLI works with multiple AI providers. Run it directly with npx:
npx @blen/lisa "user authentication"
Prerequisites: At least one AI CLI tool must be installed:
| Provider | CLI Command | Installation |
|---|---|---|
| Claude Code | claude | anthropic.com |
| OpenCode | opencode | opencode.dev |
| Cursor | cursor or agent | cursor.sh |
| Codex | codex | codex.dev |
| GitHub Copilot | gh with Copilot extension | github.com/copilot |
Plugin (Claude Code):
/lisa:plan "user authentication"
CLI:
npx @blen/lisa "user authentication"
/lisa:plan <FEATURE_NAME> [OPTIONS]Start a specification interview for a feature.
Arguments:
FEATURE_NAME (required) - Name of the feature to spec outOptions:
| Option | Description | Default |
|---|---|---|
--context <file> | Initial context file (PRD, requirements, etc.) | none |
--output-dir <dir> | Output directory for generated specs | docs/specs |
--max-questions <n> | Maximum question rounds (0 = unlimited) | 0 |
--first-principles | Challenge assumptions before detailed spec gathering | false |
-h, --help | Show help | - |
Examples:
# Basic interview
/lisa:plan "user authentication"
# With existing context
/lisa:plan "payment processing" --context docs/PRD.md
# Custom output location
/lisa:plan "search feature" --output-dir specs/features
# Limit to 15 questions
/lisa:plan "caching layer" --max-questions 15
# Challenge assumptions first
/lisa:plan "new dashboard" --first-principles
# Combined options
/lisa:plan "api gateway" --context docs/arch.md --first-principles --max-questions 20
/lisa:resumeResume an interrupted specification interview.
/lisa:resume
If you have interviews that were interrupted (session ended mid-interview), this command will:
/lisa:cleanupClean up all Lisa interview state files.
/lisa:cleanup
Removes all interview state files from .claude/lisa-*.md. Use this to:
Note: This does NOT delete completed specs in docs/specs/.
/lisa:helpDisplay help documentation about the Lisa workflow.
npx @blen/lisa "user authentication system"
Usage: npx @blen/lisa [options] [feature]
Arguments:
feature Feature description to plan