Add structured sections for 'what-to-do' and 'supporting-info' in SKILL.md

Co-authored-by: Copilot <copilot@github.com>
This commit is contained in:
Matt Pocock
2026-04-30 12:38:11 +01:00
parent 839025ae17
commit b843cb5ea7
@@ -3,12 +3,18 @@ name: grill-with-docs
description: Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
---
<what-to-do>
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing.
If a question can be answered by exploring the codebase, explore the codebase instead.
</what-to-do>
<supporting-info>
## Domain awareness
During codebase exploration, also look for existing documentation:
@@ -78,3 +84,5 @@ Only offer to create an ADR when all three are true:
3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons
If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](./ADR-FORMAT.md).
</supporting-info>