Use when asked to implement a planned Linear ticket on a schedule, "implement the next ticket", "boss-build", or given a ticket ID to implement. Unattended cron-safe sibling of boss-plan — it consumes agent-friendly planned tickets and ships review-ready PRs.
Orchestrate an entire epic of planned Linear tickets to merged PRs, unattended. Assembles the epic's sub-issues (or an explicit ticket list), computes a dependency-ordered schedule, spawns parallel boss-build sessions, drives repair on failures, serializes…
End-of-session workflow ensuring all work is committed and pushed. Use when ending a work session or when asked to "land the plane".
Plan a tracker backlog ticket. Grabs the next unplanned issue by priority (or a ticket ID you provide), resolves drafting through boss-plan draft extensions or portable fallbacks, attaches the plan natively to the tracker issue, then writes a summary, labels,…
Automated PR repair — fixes conflicts, failing checks, and review feedback
Multi-lens, subagent-driven code review for the current branch. Runs the conditional lenses the repo's registry defines (golang-pro / impeccable / database-review / api-review by default), discovered whole-branch round extensions with a host/inline fallback…
Complete reference for all boss CLI commands. Use to run boss operations from within a Claude Code session.
Runs spec-driven verification at the end of a flight leg. Plans tests from the spec, runs quality gates, executes tests in a fix-and-retry loop, and confirms confidence before handoff.