grill-with-context
Skill2 starsChanged 4 months agoMITView on GitHub
Interview the user about a plan or design until decisions are resolved, while updating CONTEXT.md terms and noting ADR candidates. Use before large features, cross-repo integrations, or when requirements feel vague.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Do not start coding until grilling is complete
- Distinctive: line 35
Do not ask five questions in one message
- Distinctive: line 36
Prefer multiple-choice when options are finite
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Grill With Context
Inspired by mattpocock/skills grill-with-docs — org-specific version.
When to use
- New feature spanning multiple stack layers
- Unclear which repo should own the change
- User says "build X" without success criteria
Process
- Restate the goal in one sentence; ask if correct
- Grill — ask one question at a time until resolved:
- Which stack layer? (see governed-ai-stack)
- What defines done? (test, demo URL, metric)
- Side effects? (gateway/HITL required?)
- Stub mode or live API keys?
- Sharpen vocabulary — if the user uses vague terms, propose CONTEXT.md entries
- ADR candidates — flag decisions that need an ADR in ai-architecture-portfolio
- Output — short plan with repo, files, test strategy, out-of-scope list
Rules
- Do not start coding until grilling is complete
- Do not ask five questions in one message
- Prefer multiple-choice when options are finite
After grilling
Suggest tdd-agent-loops for implementation or to-prd equivalent: write plan to docs/plans/<slug>.md
Other versions4 projects use a version of this.
Word for word · 4
- vpeetla-ai/aegisai-enterprise-agent-platform★ 2100% same
- vpeetla-ai/multi-agent-system-pattern★ 2100% same
- vpeetla-ai/reflection-agent-pattern★ 2100% same
- vpeetla-ai/swarm-agent-pattern★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- aegis-gatewaySkill
- agentic-engineeringSkill
- deploy-vercel-renderSkill
- governed-ai-stackSkill
- hitl-side-effectsSkill
- langgraph-orchestrationSkill
- loop-engineeringSkill
- portfolio-adrSkill
- rag-governanceSkill
- repo-fix-prSkill
- setup-vpeetla-skillsSkill
- tdd-agent-loopsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.