# Grill With Tree

> Interview the user through a visible decision tree, inspect available evidence before asking questions, trace downstream and cross-branch consequences, and produce an implementation-ready decision brief with assignable tasks. Use when a user asks to grill, challenge, stress-test, align, or de-risk a product, architecture, migration, or implementation plan before work begins, especially when they…

- **Type:** Skill
- **Install:** `agentstack add skill-zhongmaomao-grill-with-tree-grill-with-tree`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [zhongmaomao](https://agentstack.voostack.com/s/zhongmaomao)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [zhongmaomao](https://github.com/zhongmaomao)
- **Source:** https://github.com/zhongmaomao/grill-with-tree/tree/main/skills/grill-with-tree

## Install

```sh
agentstack add skill-zhongmaomao-grill-with-tree-grill-with-tree
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Grill with Tree

Turn ambiguity into explicit, evidence-backed decisions and then into an implementation-ready brief.

Keep this workflow read-only with respect to implementation. Inspect source material freely, and write only decision-state or brief documents unless the user separately authorizes implementation.

## Core rules

- Organize the interview by decisions, not implementation tasks.
- Inspect code, documentation, history, configuration, and other available evidence before asking anything locally discoverable.
- Ask only material questions. Different answers must change observable behavior, an interface or architecture contract, risk, reversibility, compatibility, rollout, or delivery scope.
- Ask exactly one unresolved question at a time. If the user answers several decisions voluntarily, record all of them.
- Include a recommended answer, the reason, and the important tradeoff with every question.
- Distinguish known facts, assumptions, recommendations, and user decisions.
- Add child nodes only when an answer exposes a new material choice. Use cross-links instead of duplicating a decision shared by several branches.
- Reopen earlier nodes when new evidence or a later answer invalidates them.
- Never confuse a ready plan with authorization to implement it.

## Question format

Use stable node IDs such as `D1`, `D1.1`, and `D2`.

```text
Decision D: 

Why this matters: 
Recommendation: 

Options:
A. 
B. 
C. 
```

After the answer, update the affected branch. Show the changed branch and the next open node; show the full tree only when it materially helps or the user asks.

Use these node states:

- `open`: requires a decision
- `decided`: explicitly settled
- `inferred`: settled from evidence; identify the evidence
- `deferred`: intentionally postponed with an owner or trigger
- `blocked`: cannot be resolved without missing authority or information

## Workflow

1. Inspect the available sources and summarize the goal, affected surface, known facts, constraints, and non-goals.
2. Seed the smallest useful set of root decisions and show the initial tree.
3. Walk the highest-impact unresolved branch. Prefer prerequisite decisions before dependent ones.
4. After every answer, audit consequences across the relevant dimensions:
   - observable behavior and failure paths;
   - lifecycle, state ownership, and data flow;
   - interfaces and cross-system contracts;
   - compatibility, migration, security, privacy, and operations;
   - rollout, recovery, and verification.
5. Challenge contradictions, optimistic assumptions, missing failure modes, and decisions that move complexity elsewhere.
6. Before closing, map every requirement to a resolved decision, test the combined design with counterexamples, and list every remaining assumption.
7. Read `assets/decision-tree-brief.md` and use it to produce the final brief. Omit sections that are genuinely irrelevant; do not leave silent gaps.
8. Derive implementation tasks only after the decisions are settled.

## Completion gate

Do not mark the brief ready for implementation until:

- the desired outcome and measurable success criteria are explicit;
- scope, non-goals, and constraints are explicit;
- every material behavior or contract is resolved or visibly deferred;
- ownership, failure handling, compatibility, rollout, and recovery are covered when relevant;
- acceptance criteria and verification are actionable;
- remaining risks and open items have an owner, trigger, or default;
- the execution graph respects real dependencies and shared-write boundaries.

## Task decomposition

Keep coupled changes together. Do not target an arbitrary task count.

For every task, record:

- goal and deliverable;
- dependencies and parallel-safe peers;
- exclusive write ownership;
- settled contracts it must preserve;
- forbidden scope;
- acceptance criteria;
- tests or other verification.

Reserve shared-file changes, cross-task integration, and final validation for one explicit owner.

## Multi-agent handoff

When the execution graph contains genuinely independent tasks, end with a ready-to-copy handoff:

```text
Use $multi-agent to implement this brief. Treat the Locked Contracts as fixed.
Follow the task dependencies and exclusive write ownership below. Return any
behavior-changing conflict for user resolution before continuing.
```

If the host exposes skills as slash commands, `/multi-agent` may be the equivalent invocation.

Do not invoke implementation automatically unless the user has explicitly asked to proceed.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [zhongmaomao](https://github.com/zhongmaomao)
- **Source:** [zhongmaomao/grill-with-tree](https://github.com/zhongmaomao/grill-with-tree)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-zhongmaomao-grill-with-tree-grill-with-tree
- Seller: https://agentstack.voostack.com/s/zhongmaomao
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.