grill-with-docs
Grill with Docs
Stress-test the requested plan through conversation and keep agreed domain language and lasting decisions in the project's documentation.
Load the local guidance
Use the grilling skill for questions and decision dependencies, and the domain-modeling skill for terminology and architectural records, when available. Locate these repository-owned skills through the available skill catalog and use its supplied locations or loading mechanism; do not infer sibling directories. If either skill is unavailable, continue with the combined procedure below. Do not fetch or substitute an external skill.
Establish documentation scope
A request to use this workflow includes updating the local glossary and architectural decision records as the user settles decisions. These documentation rules apply when using the supporting skills too. In read-only or proposed-edit mode, keep proposed text in the conversation and do not create or edit files. If the user limits writes to particular documents, update only those documents and keep other proposed records in the conversation.
Inspect the existing glossary, context map, relevant ADRs, and only the code needed to ground the discussion. Follow established documentation locations and formats. When no convention exists, use CONTEXT.md for domain terms and docs/adr/ for qualifying decisions; create them only when there is agreed content to record.