Decision 0021 · Accepted
Autonomous explore and ship: GitHub issues, grouped
pull requests
Dogfooding spec 010 showed two frictions. The work shipped as five pull requests for small, coupled skill edits, and every step stopped for confirmation or a permission prompt.
- Status
- Accepted
- Built from:
- da88c48
Status: Accepted (2026-10-28). Amends 0019 (push confirmation). Amended by 0024 (a final gate before merging into or pushing main). Amended by 0028 (no push confirmation; ship merges after review and green checks). Related: 0004, 0015. Spec: 010.
Context
Dogfooding spec 010 showed two frictions. The work shipped as five pull requests for small, coupled skill edits, and every step stopped for confirmation or a permission prompt. to-tasks published issues only on request, so tasks lived in chat unless someone asked.
Decision
- Files and issues by default.
explore, once spec-ready with a brief, writes the spec todocs/specs/and publishes tasks as GitHub issues throughto-tasks. Research stays indocs/research/.to-taskspublishes GitHub issues by default; another tracker only when the project already uses one, and a local draft without GitHub access. - Grouped pull requests. Tasks are not pull requests.
shipputs an exploration's research, spec, and root-context changes on one branch and pull request, and a spec's tasks on one branch and pull request. Split only large, independently shippable work or work that needs separate review. - Autonomous runs.
exploreandshipsuggest the host's autonomous permission mode before multi-step runs (for example Claude Code auto mode). Skills keep their own gates: thePRODUCT.mdtext yes, and one push confirmation per run that states the pull request and merge plan. Merging still requires the user's authorization.
Rationale
One pull request per coherent change keeps review proportional and avoids rebasing chains of tiny branches. Issues give tasks a durable home that pull requests can close. Suggesting the host's autonomous mode removes permission-prompt friction without giving skills authority the user did not grant.
Consequences
explore,ship,to-tasks, andto-specchange together; smoke contracts cover the new rules.- Hosts without an autonomous mode run with ordinary prompts.
- Adopters without GitHub get local task drafts.