grill-with-docs

Run a grilling session that systematically questions assumptions, edge cases, and trade-offs in the design. The session resolves open questions through dialogue and records each settled decision as an Architecture Decision Record.

The session produces Architecture Decision Records capturing each resolved design decision and a glossary defining domain terms. Both artifacts are written incrementally as the interview progresses rather than afterward.

An ADR (Architecture Decision Record) documents a significant design choice, its context, and its rationale. Write one whenever a non-obvious trade-off is settled, which this skill automates during the grilling session.

Yes, the grilling session explicitly uses the domain-modeling skill to ground questions in a shared model of the problem space. This keeps terminology consistent between the discussion and the generated glossary.

Avoid it for trivial changes with no meaningful trade-offs, where the interview overhead exceeds the value of documented decisions. It is most useful for designs with ambiguity, multiple stakeholders, or long-lived architectural impact.