trail-blazer-flow

Onboards a repository onto the issue workflow harness (planner → implementer → verifier). Use when the user asks to "set up the harness", "onboard this repo", "check the harness installation", or right after installing the plugin in a repo. Runs the mechanical preflight (doctor script), audits the repo's CLAUDE.md against the harness contract (drafting one if needed), establishes a green verification baseline on the default branch, and reports readiness. Advisory only — it never gates the other skills, never commits, and never overwrites project-owned files without explicit human approval.

Runs one full pass of the steady-state workflow: post-merge cleanup → plan (and revise, propose answers, policy auto-approve) → implement approved issues → report what now waits on the human. Use when the user asks to "run the cycle", "process everything pending", "run the harness", "do a full pass", or wants unattended/scheduled operation (pair with /loop or a scheduled routine). It composes the issue-planner and issue-implementer skills and adds no authority beyond what the repo's CLAUDE.md delegates.

Implements approved GitHub issues end to end, producing a pull request for each. Use when the user asks to "implement the approved issues", "run the implementer", "build the approved plans", or similar. Finds issues labelled plan-approved (excluding pr-open / impl-blocked), processes them ONE AT A TIME (never in parallel — they share a working tree), and for each: branches off the default branch, dispatches a single `implementer` subagent to write and verify the code, then commits, pushes, and opens a PR for review. Never merges.

Generates and revises implementation plans for open GitHub issues in this repo. Use when the user asks to "plan the issues", "run the planner", "draft plans for new issues", or similar. Finds open issues that need an initial plan (no plan-* label) or a revision (a plan-proposed issue with maintainer feedback comments posted after the latest plan), dispatches a read-only `planner` subagent for each, then posts each plan as an issue comment and sets labels. Planning only.

Kicks off a brand-new project from scratch onto the issue workflow harness. Use when the user wants to "start a new project", "set up a new project from scratch", "kick off a project", or says "I want to build ..." in an empty or near-empty repo. Interviews the user to capture the vision (document-first if they have one, a fuller interview if they don't), helps them settle on scope, architecture, and methodology, then emits the artifacts the rest of the harness consumes: a project brief, a drafted CLAUDE.md, a connected GitHub repo, and an initial issue backlog whose first item is a walking skeleton. Greenfield only — for an existing codebase use harness-setup. Never writes feature code; never commits without approval.

Files coverage-increasing GitHub issues under the repo's CLAUDE.md "Test-suite ratchet policy". Use when the user asks to "run the test ratchet", "propose coverage work", "find the untested code", or when the issue-cycle's ratchet pass invokes it. Runs the measurement command the policy names, picks the largest gaps that tests alone can close, and files up to a capped number of evidence-backed, test-only issues labelled `test-ratchet` — the planner's auto-approval hard floor refuses that label outright, so these plans always wait for a human. Files issues only — it never plans, approves, implements, or merges.