← ClaudeAtlas

claude-spec-interviewerlisted

Interview fuzzy Claude Code coding requests into user-verified implementation specs with source challenge, ADR gate, validation plan, and execution prompt. Use when the user asks for /claude-spec-interviewer, a Claude Code implementation plan, PRD, requirements, plan before coding, Plan Mode planning, persisted spec, ADR decision, CLAUDE.md evidence, or .claude/rules evidence. Do not use for direct implementation, pure brainstorming, memory cleanup, or authoring Claude instruction files only.
stark-ai-de/agent-skills · ★ 5 · AI & Automation · score 80
Install: claude install-skill stark-ai-de/agent-skills
# Claude Spec Interviewer ## Goal Produce a user-verified implementation spec with bounded scope, explicit assumptions and validation, a source challenge, and ADRs for durable decisions when needed. Save it using the repo's confirmed convention; save ADRs only when the ADR gate requires them. This is one end-to-end outcome, not a public multi-workflow skill. Do not invent review/save variants or add a workflow-selection checkpoint. ## When to use - The user has a rough idea but not a production-ready implementation spec. - The task spans multiple files or concerns, or requires tradeoff decisions. - The request needs acceptance criteria, validation commands, rollout notes, or risk handling. - The user wants a reusable written artifact before implementation begins. - The user invokes `/claude-spec-interviewer` or asks Claude Code to plan before coding. - Requirements, feature shape, ADR assumptions, or the implementation approach should be challenged against repo reality and current external sources before coding. ## When not to use - The user already provided a complete implementation spec with files, constraints, tests, and acceptance criteria. - The task is a tiny one-file edit without meaningful ambiguity. - The user wants brainstorming only and no concrete implementation artifact. - The user only wants a Claude Code rule, command, or other prompt-scope file authored, not an implementation spec. - The task is primarily a policy, legal, or business-decision document.