autopilot

Automate intake processing through SCAN, BRIEF, BUILD, and REPORT stages.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/special-place-administrator/citadel_codex --skill autopilot-special-place-administrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autopilot
Source: https://github.com/special-place-administrator/citadel_codex/tree/main/skills/autopilot
Command: npx skills add https://github.com/special-place-administrator/citadel_codex --skill autopilot-special-place-administrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Intake-to-delivery pipeline automation for pending items from .citadel/intake/: briefs new ideas, executes approved work through research → plan → build → verify. Drop a file in .citadel/intake/ and invoke this skill.

Core Features & Use Cases

  • End-to-end intake processing: automatically briefs, plans, builds, and verifies items from intake.
  • Drop-in intake automation: triggers when a file is placed in .citadel/intake/.
  • Deterministic workflow routing: ensures consistent progress through SCAN → BRIEF → BUILD → REPORT.

Quick Start

Drop a pending intake file into .citadel/intake/ and invoke autopilot.

Frequently Asked Questions about autopilot

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

FAQPage Schema
How do I automate intake processing for pending work items?

Intake processing is automated by dropping a pending file into the `.citadel/intake/` directory and invoking the workflow, which then guides items through briefing, planning, building, and verification.

What is the workflow routing mechanism for intake-to-delivery pipelines?

The routing mechanism uses a deterministic four-stage protocol: SCAN, BRIEF, BUILD, and REPORT, ensuring consistent progress and applying status-based item handling with quality gates.

Can I use this pipeline orchestration for large-scale operational workflows?

This pipeline orchestration is designed for small-to-medium-scale operational pipelines from a centralized intake directory, and may not be suitable for large-scale enterprise workflows.

How do I trigger delivery orchestration for approved work items?

Delivery orchestration triggers automatically when a file is placed in `.citadel/intake/`, executing approved work through a sequence of research, plan, build, and verify stages.

What are the limitations of using a centralized intake directory for workflow automation?

Limitations include dependency on the `.citadel/intake/` directory for triggering workflows, meaning items outside this directory are not automatically processed, and scale is constrained to small-to-medium operations.