wild-horses

Write pull-request descriptions and titles that lead with the one structural idea, not a file-by-file changelog. Use when about to write or revise a PR description or title (before `gh pr create`/`gh pr edit`, or when a repo squashes with the PR body as the commit message), or when an existing description reads like a changelog and needs rewriting.

Autonomously take an issue/ticket or a plan file from a link (or path) to an opened pull request, with no human in the loop. Hand it a Linear/GitHub/other issue URL, a path to a plan/spec file (e.g. ~/plans/repo/foo.md), or a plan already read into the conversation, and it decides everything itself: implements, tests, simplifies the diff, runs a bounded reasoning-gaps review (critical findings only, via harness agent prompts), reviews via wild-pr:review (falling back to an independent sub-agent) to convergence, and opens a PR following the target repo's own conventions. Use when the user says work this issue autonomously, take this ticket end-to-end, do this AFK, pastes an issue link, or points it at a plan file and asks you to just build it. Ships an autonomy contract (never stop to ask) plus a 10-rule code-style bar.

Reclaim disk space from stale git worktrees: scans configured roots, classifies each as cleanable (merged PR, upstream gone, merged into the default branch, stale) or skipped (dirty, locked, unpushed), shows the cleanable set grouped by reason with sizes, and removes the ones you pick. Use when the user asks to clean up git worktrees, delete merged worktrees, prune stale worktrees, free disk space from worktrees, or list cleanable worktrees.

Scan a codebase and produce architecture.json + codepaths.json describing components, edges, and traced codepaths. Renders architecture.html at the end. Use when the user says "map my app", "build the architecture viz", "scan my codepaths", "map the X flow", etc. Pass `--render-only` to skip all mapping work and just re-bake architecture.html from existing JSONs — use when the user says "re-render the visualizer", "rebuild the viewer HTML", "regenerate architecture.html", or after a template/CSS edit.

Open docs/codepaths/architecture.html in the browser. With --select, blocks on a user pick and returns the chosen codepath JSON to the calling agent. Run after /codepath-mapper has produced the HTML.

Build or rewrite a structured task list (JSON + paired markdown report) matching the harness task-list schema. Accepts free-form text, an existing reasoning-gaps/feedback-blockers report, an existing JSON task file (in-place rewrite), or recent conversation context. Use when the user says "build the task list using task-list-builder", "rewrite the plan file using task-list-builder", or otherwise asks to convert or update a chunk of work into the harness task-list format.

Run a structured task list (JSON file in the harness task-list schema) by dispatching each task to a foreground Agent in sequence. Auto-locates an in-progress task file in docs/exec-plans/active/ when no path is given. Use when the user says "run the plan", "resume the plan", "execute the tasks", "run task-list-runner", or otherwise asks to drive an existing harness task list to completion. Pairs with task-list-builder, which produces the JSON.

Read-only viewer for harness task-list JSON files. Auto-locates the active task file in docs/exec-plans/active/. With no args, shows counts, the paired markdown plan path, the in-progress task ID (if any), and pending task titles. With a positional task ID, prints that task's full details. Use when the user says "show me the task list", "view the plan", "what tasks are left", or otherwise asks to inspect (not run) an existing harness task list. Pairs with task-list-builder (which creates) and task-list-runner (which executes).

Scaffold a Claude Code plugin marketplace with proper structure, schema validation, and CLAUDE.md conventions. Asks for the marketplace name and whether to import an existing skill. Use when starting a new marketplace repo or adding marketplace structure to an existing repo.

Copy every plugin from a Cursor marketplace catalog into ~/.cursor/plugins/local as real files (no symlinks). Use when installing or refreshing wild-horses (or any dual-manifest marketplace) for Cursor, when team marketplace refresh is unavailable, or when local plugin installs must not point at a checkout via symlink.

Manage the groundcrew dispatch queue - view it, queue plans for pickup, promote plans to todo in bulk, or dequeue them. Shows the current repo's queue by default; show every repo with "all repos". Use when the user asks to see or manage the groundcrew queue, queue a plan for groundcrew, promote plans to todo, dequeue plans, or move a plan into todo state to be picked up by groundcrew.

List saved plans and route the picked one to the right next skill, based on whether it reads as an idea, spec, or execution-ready plan. Use when the user asks to work on a saved plan, do a plan, implement a plan, execute a plan, pick up a plan to work on, or resume a plan from disk.

Archive a completed plan into ~/plans/<repo>/done/ with a completion stamp. Use when the user finishes a plan, marks a plan done, archives a plan, says "I'm done with the plan", or asks to clear a completed plan.

File a plan as a Jira ticket, or update an existing one from a plan; supports first-time Jira setup inline. Use when the user asks to push a plan to Jira, file a Jira ticket/issue from a plan, or update an existing Jira ticket from a plan.

File a plan as a Linear ticket, or update an existing one from a plan; supports first-time Linear setup inline. Use when the user asks to push a plan to Linear, file a Linear ticket/issue from a plan, or update an existing Linear ticket from a plan.

List the saved plans for a repo (or a named bucket) as a read-only inventory of what's in ~/plans/<repo>/, without picking one to work on. Use when the user asks to list, show, or see the saved plans for a repo.

Save a plan, design doc, or any file (markdown, JSON, YAML, etc.) into the per-repo ~/plans/<repo>/ tree, including paired outputs like task-list-builder's `.json` + `.md` pair. Use when the user asks to save a plan, save the plan, persist the plan, capture planning notes for future reference, or store a plan for later.

Split one plan into several smaller, independently-dispatchable plans wired with native Blocked-by dependencies, saved into the per-repo plans tree. Use when the user asks to split a plan into independently-grabbable pieces, decompose a plan/spec/design into child implementation tasks, or break a plan into vertical slices or tracer bullets.

Edit a plan's frontmatter (status, assigned agent, and other fields) via plan_keeper_cli.py file-meta set. Use when the user asks to change the agent on a plan, promote a plan to todo, mark a plan as ready, set a plan's status, or edit plan frontmatter.

Argue the strongest good-faith case AGAINST the proposed changes. Builds a steelman of the opposition — hidden costs, wrong assumptions, simpler alternatives, second-order effects, and the do-nothing option — for a plan, design, or diff under discussion. Use when the user says "steelman the case against this", "argue against these changes", "red-team this plan", or "what's the strongest objection?".

Pull every repo listed in ~/.config/wild-horses/update-git-repos/repos.json from origin/<branch> via the bundled CLI, including bootstrapping that config (auto-discovery under a root directory, plus manual add/remove). Use when the user asks to update all their git repos, pull main on all repos, sync repos from origin, refresh local clones, or run `git pull` across a known set of repos.

Watch a PR through CI and review feedback. Auto-fix high-confidence failures and address review comments. Use when the user says /wild-pr:babysit, babysit a PR, or respond to PR comments.

Code review of a diff, branch, or PR, with findings posted as anchored PR comments. Use when the user asks to review a diff, branch, or PR, asks to check a change against its ticket/spec/PRD, or runs /wild-pr:review [pr-number-or-url] [--effort low|high] [--report].

Open a PR for the current branch using summary-writer for the title/body, then run babysit up to three times (stop early on clean). Use when the user says /wild-pr, "create a PR and babysit", "open a PR and babysit", or wants create-then-tend in one shot.