Grill and document
Start a focused one-question-at-a-time interview that also preserves resolved domain vocabulary and genuinely consequential architectural decisions without creating tickets or implementing the plan.From its SKILL.md
npx -y skills add martonpaulo/skills --skill grill-and-documentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 205 tokens by cl100k_base, as published. Nobody here has run it
Grill and Document
Apply grilling for the interview and domain-model for terminology, business rules, and domain decisions.
Workflow
- Inspect repository guidance and existing glossary or ADR conventions directly. Respect configured paths when present; otherwise use the defaults defined by
domain-modelonly when an artifact becomes useful. - Ask one material question at a time through
grilling. - When terminology becomes canonical, write the glossary entry promptly. Keep glossary content limited to domain vocabulary, states, rules, and relationships.
- Record an ADR only when the resolved decision is difficult to reverse, surprising without context, and based on a real tradeoff.
- Continue until the remaining uncertainty is reversible and implementation-safe.
Do not turn CONTEXT.md into a specification. Do not create planning or work-management artifacts, and do not start implementation after the interview.
Completion
End with the agreed understanding, files written, unresolved decisions, and recommended next action.