agentleFS
anivaranivar/agentic-sdlc/skills/grill-plan/SKILL.md

grill-plan

Skill0 starsChanged 37 days agoMITView on GitHub

Interrogate a plan, design or decision until nothing is silently assumed: map the decisions as a tree, ask the whole settled frontier in one numbered round with a recommended answer per question, look facts up instead of asking for them, put only decisions to the decider, and record each settled decision in the plan or as a decision record. Triggers on: "grill me", "grill this", "stress-test", "poke holes", "interrogate the plan", "what am I missing", "challenge this", "before I commit to this".

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Grill a plan

Interview until there is a shared understanding and nothing is left assumed. The decisions form a tree: every decision branches into the decisions that hang off it. Work the tree in rounds.

The rules

IdRuleIn practice
GRILL-1Rounds over the frontierThe frontier is every decision whose prerequisites are settled. Ask the whole frontier in one round: number each question, give a recommended answer, word the question so "yes" accepts the recommendation. A question that depends on another one still open waits for the next round.
GRILL-2Facts are the agent's jobAnything the filesystem, the repository, a document or a tool can answer is looked up, never asked. A running lookup is an unsettled prerequisite: ask the rest of the frontier now, hold only the questions downstream of it.
GRILL-3The session ends when the frontier is emptyEvery branch visited, nothing silently assumed. Act on nothing until the decider confirms the shared understanding. Each settled decision goes into the plan's Decisions table (PLAN-7) or, when it is hard to reverse and surprising, a decision record (DECIDE-1); when there is no plan, the conversation summary.

A round

Q1. <title>: <the question, with the options when there are several>
    Recommended: <answer>. Yes accepts it.

Q2. <title>: <question>
    Recommended: <answer>.

Plain text, no emoji, no decoration. After the answers, recompute the frontier: settled decisions unblock the questions that depended on them. Ask the next round.

What a good question does

  • It separates a decision (the decider's) from a fact (yours to find).
  • It names the consequence of each option in one line, tagged Verified, Measured or Inferred (EVID-1).
  • It is specific enough that "yes" is an answer.

Companion skills

NeedSkill
Where the settled decisions goplan-project, decision-records
The vocabulary for interface and seam questionsdeep-modules
Calibrating the consequences you stateevidence

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.