autopilot

Orchestrate a product development workflow from a specified input folder.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end product development workflow, from requirement analysis to sprint planning and publishing, by orchestrating other skills based on folder inputs.

Core Features & Use Cases

  • Folder-based Automation: Processes instructions and team data from a specified input folder.
  • Workflow Orchestration: Executes a predefined sequence of skills for product development phases.
  • Use Case: Imagine you have a folder containing a brief.md and a team CSV. Running the autopilot skill will analyze the brief, generate user stories, plan the sprint, and prepare for publishing, all with minimal user intervention.

Quick Start

Run the autopilot skill on the folder located at '/path/to/your/product/brief'.

Frequently Asked Questions about autopilot

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

FAQPage Schema
How do I automate product development workflow from a requirements brief?

To automate product development workflow, you can execute the autopilot skill on a specified input folder containing your brief.md and team CSV, orchestrating requirement analysis, backlog generation, and sprint planning linearly without manual intervention.

Can I generate user stories and plan sprints automatically from a folder input?

Yes, you can generate user stories and plan sprints automatically by processing folder-based inputs; the workflow orchestrates requirement analysis, user story creation, validation, team assignment, and dependency mapping sequentially to prepare for remote publishing.

What is workflow orchestration for sprint planning and how does it handle dependencies?

Workflow orchestration for sprint planning executes a predefined skill chain that analyzes requirements, generates backlogs, creates user stories, and maps dependencies linearly, ensuring runtime context management without deviating from the defined execution flow.

Do I need a specific folder structure to run automated sprint planning and user story generation?

You need an input folder containing a brief.md file with requirements and a team CSV for assignments; the automation strictly adheres to its predefined execution chain to process these inputs and output sprint plans.

Can I manually intervene or change the execution order during automated product development orchestration?

No, the workflow orchestration ensures linear execution without manual intervention or deviation from the predefined skill execution chain, managing runtime context automatically throughout the requirement analysis to publishing phases.

Why use folder-based workflow orchestration instead of manual product backlog generation?

Folder-based workflow orchestration automates the end-to-end product development sequence from requirement analysis to remote publishing, reducing manual effort by handling backlog generation, team assignment, and dependency mapping in a single linear execution.