Install
$ agentstack add skill-peeyushmeher-agent-agile-aa-grill ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
aa-grill
Resolve the Agent-Agile playbook root: use the first of these that exists — (1) ${CLAUDE_PLUGIN_ROOT}/playbooks, (2) ./.claude/agent-agile/playbooks, (3) ./.agents/agent-agile/playbooks, (4) ~/.claude/agent-agile/playbooks, (5) ~/.agents/agent-agile/playbooks, (6) ./playbooks.
Read playbooks/planner.md section The Grill in full, including the Grill → intake mapping table inside it, and follow it exactly — do NOT re-derive or improvise the system. The interrogation script, its handling rules, and the valid "recommend not building it" outcome are all defined there; use them as written.
How this skill runs
This is a live conversation, not a subagent job — it runs in the main loop. Ask the seven grill questions from the playbook one at a time, in order. Never dump the list at once. Apply the playbook's handling rules on every answer: a vague answer gets narrowed into a forced choice built from the answer's own words before moving on; "everyone" and "it'd be cool" are rejected outright per the playbook.
If the idea fails its own questions — no real user, no real switch reason, no number that would move — say so plainly, name which questions it failed, and recommend against building it. Stop there; do not write IDEA.md for an idea you've just recommended against.
Closing the grill
Once all seven questions produce real answers:
- Write
.planning/IDEA.mdfrom the template atplaybooks/templates/IDEA.md, filling Problem, Exact user, The one action, Why now / why switch, Non-goals, and Success signal from the grill answers. Once written, IDEA.md is locked — do not reinterpret it later. - Update
.planning/STATE.mdfrom the template atplaybooks/templates/STATE.md: set Project to a short working name for the idea (confirm it with the user in one breath before writing it), Phase togrill, Now to "grill complete, IDEA.md locked", Next to "run /aa-new-project", Pointers to.planning/IDEA.md, and Blockers tonone. - Tell the user the grill is done and offer
/aa-new-projectas the next step. State, using the Grill → intake mapping table, exactly which of the 8 intake questions are already pre-filled from this conversation and which three (hard constraints, riskiest unknown, review-batch appetite) will still be asked fresh.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Peeyushmeher
- Source: Peeyushmeher/agent-agile
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.