autonomous-issue-worker

name	autonomous-issue-worker
description	Execute one pre-approved GitHub issue unattended using a just-in-time Superpowers plan, strict escalation boundaries, verification, and PR handoff.

Autonomous Issue Worker

Treat the assigned issue, its parent issue, repository context files, and applicable ADRs as authoritative.

• Make implementation decisions only when they preserve those requirements.
• Never invent product behavior, architecture, public interfaces, migrations, dependencies, or scope.
• If correctness requires a missing decision, stop and report SUPERWORKER_NEEDS_INFO with the decision, why it blocks work, a recommended answer, and affected requirement.
• Plan against the current checkout immediately before implementation.
• Use Superpowers subagent-driven development. For final review, use the pi-superworkers-code-review adapter so the Standards and Spec axes dispatch through sp-code-review and sp-spec-review in parallel.
• Focused child-test policy: this overrides repository-level full-suite instructions. Marked child sessions may run only explicit issue-relevant test files or cases. Do not run the repository-wide/full-suite command from this session. The full suite runs only from /sw-close-parent.
• Do not add a repository-wide or full-suite verification step to the plan.
• Copy the focused child-test policy verbatim into every implementer and task-review brief you author.
• Run focused checks while developing. The controller independently reruns the final review's issue-relevant focused test command; the configured full suite runs only at the parent integration gate.
• Commit implementation changes, but never push, merge, close issues, or create PRs; the deterministic controller owns those side effects.