codex-spec-interviewerlisted

# Codex Spec Interviewer ## Goal Produce a user-verified implementation spec that Codex can execute with minimal ambiguity, minimal scope creep, explicit validation, explicit assumptions, a bounded source challenge, and ADRs for durable architectural decisions when needed. Save every final spec using the repo's clear convention or a confirmed destination; save ADR files only when the ADR gate requires one. 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. - 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 `AGENTS.md` content or Codex memory entries authored, not an implementation spec. - The task is primarily a policy, legal, or business-deci