Interview Your Code Requirements Like a Senior Architect

Conducts a rigorous interview on your requirement before you write code, asking hard questions about assumptions, edge cases, and security concerns. When you build alone, there's no one to challenge your thinking, so requirements stay vague, edge cases surface in production, and security gets treated as an afterthought. This skill forces those decisions upfront.

You invoke it with a file path or written requirement. It analyzes your codebase to understand existing patterns, then asks one question at a time using a coverage tracker to ensure all key areas (problem definition, users, technical approach, risks, security) are addressed. It pushes back on contradictions and over-engineering, then outputs a production-grade spec with a decisions log showing every debate and resolution. Optionally generates an interactive HTML preview for annotated visual review before finalizing. Output: a comprehensive specification with implementation order and security hard blocks resolved.

You catch architectural problems and security gaps before code review, because the hard questions get answered upfront.

Claude reads SKILL.md and STYLE_PRESETS.md from the skill directory to configure the interview behavior and HTML template. The skill uses the Task tool with subagent_type: Explore to fork analysis in parallel, and AskUserQuestion for every interview prompt, so it requires Claude Code's multi-turn agent capabilities and tool access.

Requires Claude Code environment (supports Cursor, Claude.app, or other Claude Code clients). Security hard blocks will pause the interview until explicitly addressed or risk accepted, so expect the interview to take time if major security gaps exist. Multi-file or very large codebases may require longer analysis time.