autogrilllisted
Install: claude install-skill vladimir-voinea/autogrill
A vague idea arrives. Autogrill runs **wayfinder → to-spec → to-tickets** to completion without a human at the wheel: it asks the grilling questions and answers them too, and resolves each wayfinder ticket in a fresh **subagent**, which is what dissolves wayfinder's one-ticket-per-session limit — the subagent *is* the session. The run ends with the map fully resolved, the spec published, and tracer-bullet tickets on the tracker that the user can implement as-is — plus, for an iOS app, the deployment ticket that ships it.
The human's only input is the **constraints** given at invocation (stack, deadline, budget, taste, forbidden moves). Record them verbatim in the map's Notes; every answer below must honor them.
Invoke the sibling skills — `wayfinder`, `to-spec`, `to-tickets`, `grilling`, `prototype`, `research`, `domain-modeling` — via the Skill tool; if one can't be invoked programmatically, read its SKILL.md and follow it. Sibling rules bind autogrill *except* where this file explicitly substitutes one thing for another: the human.
**No files on disk.** The entire run — the map, every decision record, the spec, and the tickets — lives in the issue tracker. Nothing is written to disk, no scratch branch, no checked-in artifact. The spec is itself a wayfinder ticket on the map, so the whole effort is readable in the tracker and a run leaves no files behind.
## Proxy answers
Everywhere the siblings demand a human — a HITL ticket, a grilling round, to-spec's seam check, to-