grill-with-docs
SkillCommunicationGrill a new feature before any code is written, recording the decisions as an ADR and the vocabulary in GLOSSARY.md as we go. Use when the user asks to build a new feature, starts designing one, or says "grill", "let's design", "nouvelle feature". Not for bug fixes or small changes.
Then ask your AI: use the grill-with-docs skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.
What this skill tells your AI
The instructions your AI receives, as published by badsender-com/lepatron.email in .claude/skills/grill-with-docs/SKILL.md and read by Ahel’s review.
This is step 1 of the new feature workflow described in AGENTS.md (section "New Feature Workflow"). No production code is written during this step.
- Read
GLOSSARY.md(if it exists) and the ADRs indocs/adr/that touch the area of the feature. Then look for overlapping work as described inAGENTS.md, section "Parallel Work": an open PR, an epic or a recently merged change on the same subject is the first thing to put to the user. - Call the Skill tool twice, for "grilling" and "domain-modeling", and run the interview with both disciplines at once.
- During the interview, agree on the seams the feature will be tested at (the public interfaces: an API route, a service function, a Vue component's props and events). Prefer existing seams and the highest one possible; the fewest seams is best. They become the tests of the first PR.
- When the user confirms the shared understanding, make sure the feature has its ADR in
docs/adr/, withStatus: proposedand the main design decisions of the feature. A new feature always ends with at least one ADR; the domain-modeling criteria decide which decisions deserve to be in it. - Hand over to the next step: tell the user the next one is the epic, and call the Skill tool with "to-prd".
If the effort turns out too big to settle in one session (several epics, a greenfield module), say so and propose to split it into several features, each grilled on its own.
Signals
- GitHub stars
- 91
- Forks
- 16
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
grill-with-docs-badsender-com- Source
- github.com/badsender-com/lepatron.email
github.com/badsender-com/lepatron.email
Related picks
Skill · onweekendd
The pick for Vuevue-page-composition
Skill · esposter
The pick for Vueslack-gif-creator
Skill · anthropics
More in Communicationerror-handling
Skill · affaan-m
More in Communicationemails
Skill · coreyhaines31
More in Communicationwait-what
Skill · mattpocock
More in Communication