router

One entry point for the team-workflow pack: a portable discipline for running tracked, multi-session, agent-assisted development — pressure-testing and decision-making before building, throwaway prototyping, autonomous research, filing the work that comes out of it, wizards for the steps only a human can take, session handoffs, orchestration of parallel lanes, and tracker hygiene that keeps parallel sessions from colliding. Everything repo-specific lives in one binding doc seeded by the setup skill; every skill defers decisions to the decider, the role that doc names.

First run in a repo? Run setup before anything else. The other skills read the bindings it seeds.

The skills

Skill	Reach for it when
setup	Installing the pack into a repo, or refreshing its bindings. Once-per-repo interview: confirms the tracker, verify commands, the decider, and the binding-doc home; seeds the binding doc, templates, and the session-start handoff hook; re-runs are idempotent diffs, never overwrites.
grilling	An idea or plan is half-formed and nobody has pressure-tested it. Interviews the decider in rounds over a design tree — the frontier is every decision whose prerequisites are settled — until nothing load-bearing is still assumed. Facts are the agent's job; decisions are the decider's. Run it before charting a map or writing a spec off a conversation.
decision-map	The work is genuinely foggy — open questions gate each other and nobody can spec it in one sitting. Charts a map (destination, clusters, two ledgers), files gate-decision tickets, and runs briefed decision rounds with the decider. Not for work you could already spec: a map with nothing undecided is overhead.
prototype	The question is "how should this look / behave / feel in action" and discussion or static artifacts can't settle it. Throwaway code on a prototype/<name> branch — UI variants on the live route, or a terminal UI over a pure logic module; the verdict is the deliverable and the winner is re-implemented properly.
research	A question is answerable from primary sources and should run fire-and-report. Autonomous investigation ending in a cited findings file — and a questionnaire when the missing facts are human-held.
to-tickets	The decision is made and the work needs to be on the board. Turns a plan, a closed decision map, or a pressure-tested conversation into tracer-bullet items — issue-as-spec bodies filed in one pass, blocking edges wired in a second. Files and labels; never claims, never decides.
wizard	The next step is one only a human can take — a vendor dashboard, a registrar's DNS panel, a credential that must not enter an agent's context. Generates an interactive bash wizard that opens each URL, says what to click, captures the values, verifies what it can, and reports what still needs doing by hand.
handoff	Context is filling (around half the window), the session is wrapping up, or someone says "checkpoint" / "save state". Writes the structured session handoff — overwrite-don't-append, pointer-not-transcript, NEXT points at the tracker query — so a fresh session resumes losslessly.
orchestrate	One session should coordinate several — routing tracked items into parallel working lanes, auditing results, owning integration — instead of implementing. Principles plus per-repo binding slots; the single-orchestrator rule applies.

Not skills, but in the pack

• Tracker discipline — the claim / frontier / blocking recipes and the issue-as-spec shape live in setup's references and get bound to the repo via the binding doc. There is nothing to invoke; sessions follow the recipes.
• Templates — work-item spec and lane brief are templates the setup skill seeds into the consuming repo; the session-handoff template ships inside the handoff skill.

Review discipline: the meta-rule

The pack ships no review checklist, on purpose. The rule that travels: derive your own defect classes from your own defect history, and admit a class to the checklist only via a live reproduction — a checklist imported from someone else's war record checks for their bugs, not yours. Start the repo's own list the first time a real defect escapes, and grow it only from evidence.

A sibling of the same meta-rule: institutional review memory — review verdicts recorded as per-repo decision entries that later reviews (human and automated) consult before commenting, so settled decisions reopen on new evidence, not on repetition. Repos that already run such a system — a review-response skill with a decision wiki — have the review-RESPONSE stage covered, and this pack deliberately stays out of it: planning, research, prototyping, handoff, and orchestration are the pack's territory; review response belongs to the resident system, and pack outputs should cite that repo's precedent store rather than create a second one.