autopilot

Orchestrate multi-TODO feature implementations into worktree branches and a final integration PR.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sujithatzackriya/skills --skill autopilot-sujithatzackriya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autopilot
Source: https://github.com/sujithatzackriya/skills/tree/main/skills/autopilot
Command: npx skills add https://github.com/sujithatzackriya/skills --skill autopilot-sujithatzackriya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Autopilot turns a feature spec into an end-to-end, multi-TODO implementation workflow that produces final code changes packaged in a human-reviewable pull request.

Core Features & Use Cases

  • Autonomous spec-to-PR orchestration: Plans via /tdd-workflow and drafts one richly-contexted TODO per worktree for parallelized development.
  • Per-TODO worktree execution with verification gates: Runs implementation plus think regression and deep review, then enforces a dual gate (review clean + build green) before committing.
  • Safety and harness hard-guardrails: Blocks user prompting during execution, prevents destructive git operations, disallows em dashes and secret-path reads, and enforces consistent build/testing via cargo-serial.sh.
  • Circuit breaker resilience: Tracks repeated failures per TODO and skips after persistent OPEN state to prevent infinite loops.

Quick Start

Use the autopilot skill to implement and open a final PR from a multi-step feature spec by running: /autopilot "add support for <feature>".

Frequently Asked Questions about autopilot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate feature implementation from a spec to a reviewable pull request?

Autonomous spec-to-PR orchestration plans feature implementation via worktrees and drafts one richly-contexted TODO per branch, culminating in a final integration pull request awaiting human review.

How do worktrees help parallelize multi-TODO feature development?

Worktrees enable parallelized development by isolating each TODO into its own branch, allowing the orchestrator to author, verify, and commit changes independently before final integration.

What is a circuit breaker in autonomous pull request orchestration?

A circuit breaker tracks repeated verification failures per TODO and skips the task after a persistent OPEN state, preventing infinite loops and ensuring resilient autonomous orchestration.

How do safety guardrails prevent destructive git operations during autonomous implementation?

Safety guardrails block user prompting during execution, prevent destructive git operations, disallow secret-path reads, and enforce consistent build testing via a portable shared-target cargo build wrapper.

Does autonomous PR generation work with compiled repositories requiring build verification?

Yes, the workflow enforces dual-gate verification requiring build green status using a portable shared-target cargo build wrapper specifically designed for compiled repositories.

What is dual-gate verification for multi-TODO pull requests?

Dual-gate verification enforces both a clean deep review and a green build before committing any TODO branch, ensuring each per-TODO worktree passes structured quality checks before integration.