internal-grilling
Skill1 starsChanged 9 days agoMITView on GitHub
Grill a plan internally, answering your own questions down its whole design tree and escalating only what needs the user. Use when the user wants a plan stress-tested without being interviewed.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codebase-designSkill
- code-reviewSkill
- domain-modelingSkill
- grillingSkill
- prSkill
- researchSkill
- tddSkill
- addressing-pr-reviewSkill
- address-pr-reviewSkill
- code-hostSkill
- escalating-to-userSkill
- grill-subagentSkill
- grill-subagent-with-docsSkill
- grill-yourselfSkill
- grill-yourself-with-docsSkill
- landingSkill
- landSkill
- land-ticketsSkill
- lane-landingSkill
- setup-ian-pascoe-skillsSkill
- subagent-grillingSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Run the grilling skill as an internal dialogue: answer your own questions, and put to the user only what the escalating-to-user skill …
- Very specific: line 12
When a load-bearing decision rests on a public fact, find the fact with the research skill and make its findings file the decision's …
- Distinctive: line 16
When the frontier is empty, every node is decided or escalated.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run the grilling skill as an internal dialogue: answer your own questions, and put to the user only what the escalating-to-user skill escalates. Both skills hold except where this skill overrides them.
Answer your own questions
Where grilling puts a decision to the user, decide it yourself. Play devil's advocate: name the strongest alternative answers, argue against your favourite, then decide. Each decision pushes the frontier outward; recompute it and keep walking without pausing between rounds.
When a load-bearing decision rests on a public fact, find the fact with the research skill and make its findings file the decision's artifact.
Present the ledger
When the frontier is empty, every node is decided or escalated. Present the ledger with the design tree as its decisions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.