Jordan Leigh

You can route substantive engineering work through a structured loop, build and sharpen a project's domain model, write CONTEXT.md files, record Architecture Decision Records, and stress-test plans or designs through relentless questioning that generates ADRs and glossaries as documentation byproducts.

Software engineers and technical leads facing consequential decisions, investigations, or strict structural code reviews benefit most. They suit developers who want their plans and designs rigorously challenged before execution, and teams maintaining explicit domain terminology and decision records.

It routes between direct implementation, pstack poteto-mode, grill-with-docs, and pstack thermo-nuclear-code-quality-review based on whether the work requires investigation, consequential decisions, execution, or strict structural review. The nature of the task determines the routing path.

Grill-with-docs creates Architecture Decision Records and a glossary during its relentless interview process. Domain-modeling supports writing or editing CONTEXT.md files and recording or editing ADRs, keeping codebase terminology and design decisions explicitly documented.

Trigger grilling when you want to stress-test your thinking about a plan, decision, or idea, or whenever you use any 'grill' trigger phrases. It relentlessly interrogates your reasoning to expose weaknesses before you commit to execution.