Stats
Actions
Tags
From oh-my-claude
Interviews user on spec file path, feature description, or URL to clarify requirements, refine specs, and create coding plans.
How this command is triggered — by the user, by Claude, or both
Slash command
/oh-my-claude:spec-interview <spec-file-path | feature-description>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
@include(${CLAUDE_PLUGIN_ROOT}/.commands-body/spec-interview.md)@include(${CLAUDE_PLUGIN_ROOT}/.commands-body/spec-interview.md)
npx claudepluginhub 2lab-ai/oh-my-claude --plugin oh-my-claude/big-features-interviewConducts in-depth interview via AskUserQuestion to flesh out a plan file into detailed feature spec on implementation, UI/UX, tradeoffs, then writes it back to the file.
/reviewReviews spec file at <spec-file-path> via exhaustive interview session, identifying ambiguities and gaps, iteratively updating until complete and unambiguous.
/archStarts collaborative feature specification process: investigates codebase for patterns and constraints, proposes design with reasoning and file paths, resolves ambiguities via conversation, saves Markdown spec with behavior, architecture, constraints, and related files.
/specStarts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.
/interview-specConducts deep iterative interviews with non-obvious questions and proactive research to create comprehensive spec documents for AI implementation.
/specsGenerates collaborative specifications for a feature, producing Intent, BDD scenarios, architecture notes, and acceptance criteria.