pdd-autopilot

Installation
SKILL.md

PDD Autopilot

Before you start or use Autopilot, confirm the repo. If this folder is in no Git repo, the person named another repo or it is unclear, ask one plain question with the repos you see and wait; never pick one. Run pdd autopilot in that repo's folder.

Read root pdd.json: {"autopilot":{"mode":"off|observe|auto","trust":[...]}} and checker. If autopilot.mode is absent or off, do nothing; a person leads. observe: do all the work; a person merges. auto: $pdd-merge merges under its delegation and merge rules. pdd autopilot start runs a tick with no AI that starts this skill only when there is work.

GitHub labels pdd:working, pdd:stuck, pdd:no-verdict, pdd:code-pending: add with gh issue edit N --add-label NAME (or gh pr edit); create a missing one with gh label create NAME.

  1. Check repo, account, native agent and CLI readiness. On a first visit, use pdd-prompting verification-setup.md to find or create and keep the repo’s start-up recipe for install, test and running a changed path; report gaps. Run only documented bounded startup before dependency review and selection. After selection, use the available recipe to build, verify and test the chosen path or Story. Workers follow repo repro/tests.
  2. Trust: trusted = the repo owner + write access + people added with pdd autopilot trust. Read only trusted people's text: the issue body and comments. On a public repo, do not read an issue from another author until a trusted person comments on it.
  3. Read sort before dependency review. Ready: open, eligible under dependency review; human ownership comes from the current GitHub Assignees field, which must be known and empty; no live pdd:working claim; and not owned elsewhere. Include old and new backlog; a related PR or saved run alone is not ownership. Missing assignment or eligibility data waits. In a launcher packet, eligible: false is monitoring context and never fresh work.
  4. Follow handoff. Own it: one owner per issue. Give the owner the issue link and a note of at most 30 words; for a Story, use pdd-prompting. Give goal, scope and repro. Stop with one comment if it is not a bug, has no repro or someone else owns it. For a product call no test settles, ask one question on the issue; that issue waits and the others go on. In observe mode, an existing owned workflow with an open PR waits for the person to review or merge it while its current pdd:working claim remains. Verify the claim owner before any continuation or resume.
  5. Run it with pdd-bug, pdd-feature or pdd-small-change. In auto, start the code PR as soon as PR 1 is open, in every repo. In observe, a repo with a release does the same; a new product waits for a person's "code now". One code PR per prompt file closes every issue that waits on it.
Installs
10
GitHub Stars
937
First Seen
Nov 6, 2026