skills

Execute, resume, inspect, or safely clean a validated herder-plans/ backlog as a dependency-aware multi-agent run with per-attempt token accounting. Use when the user asks to fire, run, resume, automatically complete Herder plans, clean Herder run worktrees or branches, or report a Fire run's status and token coverage. Do not use to create plans, repair plan formatting, or implement one ordinary task directly.

Survey a codebase as a senior advisor and write prioritized, self-contained Herder plans from verified repository findings without changing source code. Use when asked to audit code, find bugs or improvement opportunities, suggest evidence-backed product direction, review or reconcile existing plans, or produce a herder-plans/ backlog for $herder:fire. Route user-defined new features that require intent clarification to $herder:grill.

Initialize, validate, inspect, and manage Herder Markdown plan backlogs and execution-token ledgers. Use when creating or repairing herder-plans/, checking plan dependencies and readiness, changing plan tracking policy, inspecting execution status, reporting token coverage, or preparing plans for $herder:fire. Do not use to implement plans or orchestrate subagents.

Install or verify the implementer, reviewer, and saver agent profiles required by Herder. Use when setting up the Herder plugin in a repository, when Herder reports a missing Codex role, or when the user asks to refresh Herder's host-native agent definitions.

Validate a Herder plan directory against the canonical mechanical and semantic contracts, report plan/index/dependency/drift issues without changing files, and conservatively repair safe issues with --fix. Use when the user invokes herder:validate, asks whether herder-plans/ is Fire-ready or executable, wants a cold plan-quality audit, or asks to repair malformed, incomplete, or drifted plans. Do not use to execute plans, modify source code, or decide missing product intent.

Interview the user one decision at a time, investigate repository facts, maintain domain-model and ADR obligations, and create one validated Herder implementation plan from confirmed intent. Also refine an existing TODO or decision-blocked plan when invoked with --plan. Use when the user invokes herder:grill, wants to clarify a feature or change before implementation, asks to turn product intent into a plan, or wants to grill or stress-test an existing plan before Herder Fire executes it.