zoo-flow

Ask which skill or flow fits your situation. A router over the skills in this repo.

Implement a piece of work based on a spec or set of tickets.

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

Ask which skill or flow fits your situation. A router over the skills in this repo.

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Review a diff, branch, PR, or work-in-progress change against the requested spec, repo standards, architecture, and likely regressions. Use before committing non-trivial work.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets.

Review a diff, branch, PR, or work-in-progress change against the requested spec, repo standards, architecture, and likely regressions. Use before committing non-trivial work.

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Direct implementation mode for small, known fixes or UI updates. Bypasses heavy diagnosis or PRD creation.

Run the smallest useful checks for the current change and report exactly what passed, failed, was partial, or was blocked.

Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Writing, explore — mine raw fragments, no structure yet.

Writing, exploit — shape raw material into an article, paragraph by paragraph.

Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Writing, explore — mine raw fragments, no structure yet.

Writing, exploit — shape raw material into an article, paragraph by paragraph.

Stage selected files, write a Conventional Commit, optionally link a GitHub issue, and append a dated journal entry under docs/journal/. Use when the user wants to commit work and capture a local record of what changed.

Update repo documentation (flow, app map, architecture, README, module docs) so it matches current code. Use when docs are stale and need to be reconciled with the codebase.

Run the smallest useful checks for the current change and report exactly what passed, failed, was partial, or was blocked.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

Explore unfamiliar code and produce a written map. Use when the user wants to understand a new area, map modules and callers, or get a higher-level view before planning a change.

A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Use when you need to resolve an in-progress git merge/rebase conflict.

The same relentless interview as grill-with-docs, but for when you have no codebase. Stateless — it saves nothing locally, builds no CONTEXT.md.