Interview users in rounds to refine feature designs into draft specs.
npx skills add https://github.com/MaxWolf-01/agents --skill grilling-maxwolf-01
Please help me install this Agent Skill. Skill: grilling Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/grilling Command: npx skills add https://github.com/MaxWolf-01/agents --skill grilling-maxwolf-01
(you, rN), (my call), (open → Qn), (fog)) plus targeted questions with recommended options, so the user answers by number instead of reconstructing context. - Living spec generation: Writes and rewrites a draft spec (agent/tickets/<feature>/spec.md) per round following SPEC-FORMAT.md, covering problem statement, user stories, properties, decisions, testing seams, out-of-scope items, and fog. - Cross-session continuity: Persists unresolved questions as decision tickets so a fresh session can resume grilling where the last one stopped, then hands the confirmed design to ticket slicing. - Use Case: A user says "I want a notification system, maybe with email digests." The Skill fans out breadth-first across delivery channels, scheduling, and preferences, presents rival designs with trade-offs, and iterates rounds until every decision is settled and the spec is confirmed. ## Quick Start Ask the agent to grill you on your feature idea before any implementation begins, for example: "Grill me on my plan to add team workspaces to the app."High-intent search queries and answers about installing and using this skill.
Invoke the grilling skill before implementing anything. It interviews you in rounds, presenting the current design with marked open decisions and numbered questions with recommended options, until every ambiguity is resolved and a draft spec exists.
It maps the design as a tree of decisions and works the frontier in rounds. Each question names the decision, lists labelled options with a recommended pick, and explains trade-offs, so you answer by number like "q1 -> a".
Yes. When a session ends with open questions, they are saved as decision tickets carrying the options and recommendations. A fresh session reads the spec and tickets, claims one, and grills it as another round.
Skip it only when the request is fully specified and mechanical, with no design ambiguity. Any intent that is not fully mechanical, such as "I want X, maybe like this", should trigger grilling before implementation begins.
It produces a draft spec at agent/tickets/<feature>/spec.md following SPEC-FORMAT.md, containing problem statement, solution, user stories, properties, decisions, testing seams, out-of-scope items, and fog, confirmed once you ratify all calls.
AAbdulghanyGenerate a structured PRD template from a problem statement or feature idea.
tjmgregoryAutomate ticket-to-merge workflows with branch creation, tests, code, and PRs.
Fr-e-dResearch industry standards and compare viable technical approaches against project constraints.
c-sonnierCoordinate collaborative design sessions and produce a formal design document.