grill-with-docs

Run a structured interview that challenges each design decision with probing questions about assumptions, trade-offs, and failure modes. This Skill guides that interrogation and records the outcomes as ADRs and a glossary.

Architecture Decision Records are created incrementally as the interview surfaces each significant decision. Instead of writing ADRs after the fact, the documentation emerges naturally from the questioning process.

The interview produces two documentation artifacts: Architecture Decision Records capturing key decisions and their rationale, and a glossary defining the terms used throughout the plan or design.

Use it before committing to implementation, when a plan feels vague or untested. It is most valuable early in a project when changing decisions is still cheap and assumptions have not yet hardened into code.

The interview approach targets plans and designs generally, but its outputs (ADRs and glossaries) are conventions from software architecture practice, so it fits engineering and technical planning contexts best.