autopilot

Automate development loops from ROADMAP.md items and GitHub issues to shipped PRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end development workflow by cycling through roadmap items and standalone GitHub issues to ship features efficiently.

Core Features & Use Cases

  • Supports parsing ROADMAP.md and issues, interactive and thorough modes, and flexible phase navigation.
  • Orchestrates a /next → /ship workflow per item, with /test when needed.
  • Uses specialized agents for sub-skills and maintains a deterministic progress log.

Quick Start

Tell autopilot to process roadmap items and open issues, then apply /next and /ship automatically.

Frequently Asked Questions about autopilot

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

FAQPage Schema
How do I automate the development workflow from roadmap planning to shipping PRs?

You can automate the development loop by processing ROADMAP.md items and standalone GitHub issues. The system orchestrates a /next to /ship workflow for each item, running /tests when needed, and produces a summary with shipped PRs.

Can I use GitHub issues directly for end-to-end development automation?

Yes, standalone GitHub issues are parsed alongside ROADMAP.md items to gather work items. The automation creates a progress tracker and executes the development loop with proper error handling and gating.

What is the best way to orchestrate feature shipping across multiple roadmap items?

Orchestrating feature shipping is handled by cycling through roadmap items with specialized agents. The system supports interactive and thorough modes, applying /next and /ship sub-skills automatically while maintaining a deterministic progress log.

Does the development automation support interactive and thorough modes for processing work items?

Yes, both interactive and thorough modes are supported for processing work items. These modes allow flexible phase navigation and manage a queue with gating and progress tracking to ensure work moves from planning to shipping efficiently.

How do I track progress when automating the development loop across multiple issues?

Progress tracking is managed by creating a deterministic progress tracker during the loop execution. This tracker logs the status of each work item as it moves through the /next, /test, and /ship phases.

What are the limitations of automating the dev loop with roadmap and issue parsing?

The automation relies on parsing ROADMAP.md and standalone GitHub issues to function. If work items are not properly formatted in these sources, the system may fail to gather them or execute the /next and /ship workflow correctly.