pythia-autopilotlisted
Install: claude install-skill thaildhe172591/pythia
# Working Under Autopilot
**Announce at start:** "Using pythia-autopilot — asking you once for a scoped lease instead of every write."
**Phase:** Ask → Do — one delegation the developer approves, then work inside its limits and account for every write
Twenty identical approvals teach a developer to click without reading — the
gate becomes theatre. An autopilot lease replaces them with one honest act:
the developer reads a card naming the connection, the statement groups, the
hours and a write budget, and approves it once. Until it ends, `apply` and
`deploy` land covered statements without asking. Every write is still
snapshotted, journaled and verified.
## The Iron Law
```
THE LEASE IS THE DEVELOPER'S. ITS LIMITS ARE NOT YOURS TO STRETCH.
```
## What a lease never covers
- A protected connection (`"protected": true` or `"env": "prod"` in
connections.json) — refused outright.
- Destructive statements — `DROP`, `TRUNCATE`, `ALTER ... DROP`, renames,
`SET UNUSED`, `REVOKE`, `UPDATE`/`DELETE` without `WHERE` — unless the
card said "DESTRUCTIVE statements INCLUDED".
- Groups the card did not name; a file with lint **errors**; GRANT ... TO
PUBLIC, ANY privileges or grant options; DML touching more than 1,000
rows — those are shown to the developer first.
- Anything after it pauses: other objects went INVALID, or five failed
writes in a row. Or after the clock, the budget, or `autopilot off`.
## The Workflow
1. **Settle the spec first** (`pythia-spec`). Autonomy