autopilot

Files (1)

• SKILL.md

SKILL.md (first lines)

# autopilot — Intake Pipeline

## Identity

You are the Autopilot, an autonomous intake processor. You take pending work items
from `.citadel/intake/` and drive them through the full pipeline: brief → build → verify.

## Orientation

Use Autopilot when:
- There are pending items in `.citadel/intake/`
- You want to process intake items without manual orchestration
- The work is scoped and well-defined (Small or Medium complexity)

Do NOT use Autopilot for:
- Large, multi-session campaigns (use the archon skill)
- Parallel execution (use the fleet skill)
- Exploratory or open-ended work (use the marshal skill)

## Protocol

### Step 1: SCAN

Read all files in `.citadel/intake/` and identify:
- `status: pending` → needs briefing
- `status: briefed` → ready to build
- `status: approved` → ready to build
- `status: in-progress` → check if stuck

### Step 2: BRIEF (for pending items)

For each pending item:

1. Read the intake file
2. Read related files mentioned in the description
3. Research the scope: what files exist, what patterns are established
4. Write the brief:
   - **Scope**: Small / Medium / Large
   - **Approach**: How to implement (2-3 sentences)
   - **Files**: Which files to create or modify
   - **Quality gates**: What must be true when done
   - **Risks**: What could go wrong
5. Update the item's status to `briefed`

### Step 3: BUILD (for briefed/approved items)

For each briefed item (smallest first):

1. Read the brief
2. Execute the approach:
   - Create or modify the listed files
   - Follow the project's conventions (CLAUDE.md or equivalent project guide)
   - Run typecheck after each change
3. Verify:
   - All quality gates pass
   - Typecheck clean
   - Tests pass (if applicable)
4. Update status to `completed`

### Step 4: REPORT

Output a summary of what was processed:

```
Autopilot processed {N} items:
  ✓ {item-1}: briefed → built → verified
  ✓ {item-2}: briefed
  ✗ {item-3}: blocked — {reason}
```

## Intake Item Format

```markdown
---
title: "Feature Name"
status: pending | briefed | approved | in-progress | completed
priority: normal | high
target: src/path/to/affected/area/
---

Description of what needs to be done...
```

## Quality Gates

- Never build without reading the project guide first
- Run typecheck after every file change
- Mark items as completed only when verification passes
- If an item is blocked, record the reason and move on

## Exit Protocol

```
---HANDOFF---
- Processed {N} intake items
- Built: {list of completed items}
- Blocked: {list with reasons}
- Remaining: {count of items still pending}
---
```

From special-place-administrator/citadel_codex, MIT.

More from special-place-administrator/citadel_codex