codex-spec-interviewer

To turn user requests into implementation specs, you need an interview-based process that captures requirements, validates assumptions against source code, and gates architectural decisions. This produces spec artifacts and execution prompts for automated agents.

An architectural decision record (ADR) documents durable design choices made during feature specification. You need ADR integration when planning complex software features to ensure architectural decisions are validated, documented, and aligned with repository context before development begins.

To capture requirements and control scope, conduct structured user interviews to define feature scope, acceptance criteria, and constraints. Validate assumptions through source challenges against repository documentation to ensure all requirements are understood and documented.

Yes, you need active repository context and Plan mode access to draft Codex-executable implementation specs. Access to architectural decision records and existing documentation is also required to validate assumptions and gate design choices during the interview process.

The best way to validate assumptions against repository sources is to perform source challenges during the specification interview. This mechanism cross-references user requests and architectural decisions with existing repository documentation to ensure feasibility and scope control.

Automated specification interviews require active Plan mode, repository context, and accessible architectural decision records. If repository documentation is sparse or inaccessible, the tool cannot effectively validate assumptions or gate architectural decisions, limiting its ability to produce executable specs.