Grill with docs
Skill rengwu/wayfinder-maps/skills/.optional/grill-with-docs
A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.From its SKILL.md
npx -y skills add rengwu/wayfinder-maps --skill grill-with-docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.2 KB, 204 tokens by cl100k_base, as published. Nobody here has run it
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. Asking multiple questions at once is bewildering.
If a fact can be found by exploring the codebase or project files, look it up rather than asking me. The decisions, though, are mine — put each one to me and wait for my answer.
Throughout the session, apply the domain-modeling skill: challenge my terms against the glossary in CONTEXT.md, sharpen fuzzy language into canonical terms, stress-test relationships with concrete edge-case scenarios, and update CONTEXT.md and docs/adr/ inline as terms and decisions crystallise — creating those files lazily if they don't exist yet.
Do not enact the plan until I confirm we have reached a shared understanding.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 1 of the 12 instructions most docs writing skills give in 204 tokens
Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06
- Use third-person for skill descriptionsin 54 of 1951, across 35 files
- Start descriptions with Use whenin 43 of 1951, across 29 files
- Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
- Use active voicein 40 of 1951, across 36 files
- Map file responsibilities before defining tasksin 36 of 1951, across 29 files
- Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
- Ask one question at a timehere, and in 35 of 1951
- Offer execution options after saving the planin 33 of 1951, across 24 files
- Include complete code in every stepin 33 of 1951, across 27 files
- Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
- Announce the skill usage at the startin 30 of 1951
- Verify agent compliance after adding the skillin 29 of 1951, across 17 files
Said here and by no other author read
- Look up facts in the codebase
- Stress test relationships with edge cases
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.