# Autopilot Issue Delivery Worker

Use this skill to implement ONE microsoft/apm issue already selected by...

- Repository: https://github.com/microsoft/apm (4171 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add microsoft/apm --skill autopilot-issue-delivery-worker -g -a claude-code -y`
Codex: `npx skills add microsoft/apm --skill autopilot-issue-delivery-worker -g -a codex -y`
Cursor: `npx skills add microsoft/apm --skill autopilot-issue-delivery-worker -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/apm --skill autopilot-issue-delivery-worker -g -a gemini-cli -y`

## Description

Use this skill to implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler. Queue signal is `status/accepted` or a named bounded accept; that is not permission. Requires fresh human-scope evidence from scripts/governance before any mutate. May reproduce a bug, implement the accepted change, and open a fix PR. Not a queue manager and not a triage scheduler. Works in the scheduler's session, a child session, Cloud Agent, Remote Agent, or Agentic Workflow.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# autopilot-issue-delivery-worker

Per-issue implementation worker. The parent
`autopilot-issue-delivery-scheduler` owns the queue and the
fan-out pool. You own exactly one `ISSUE_NUMBER`.

Do not pick more issues. Do not fill other slots.

## Activation card

`activation_card: on`. Before any issue read or GitHub write, emit
this Enter card with every field filled. Missing field -> stop.

```text
skill: autopilot-issue-delivery-worker
skill_path: <resolved directory of this SKILL.md>
mode: run
subject: microsoft/apm#<issue-number>
path: delivery
intent: implement one already-selected issue
origin: unattended | actor-session
write: on | off
repo: microsoft/apm
issue: <positive integer>
invocation: agentic-workflow | actor-session
```

Rules:

- `write` defaults to `on` when the caller omitted it.
- `write: off` returns the filled template only. Do not assign,
  comment, label, edit, or open a PR.
- `write: on` may assign `@me` (actor-session only) and implement
  inside the accepted scope. Unattended never assigns and never
  implements.
- `origin` fail-closed unknown -> `unattended`.
- One issue. Do not nest a scheduler path.

After the run, emit this Exit receipt:

```text
skill: autopilot-issue-delivery-worker
subject: microsoft/apm#<issue-number>
path: delivery
write: on | off
assigned: yes | no | skipped
pushed: yes | no
approved: n/a
```

## Inputs

- `ISSUE_NUMBER` -- required
- `SELECTOR` -- `all` (default) or `bugs`
- `REPO_ROOT` -- required
- `ORIGIN` -- if the parent passed it, honor it; else resolve
- `TRUSTED_GOVERNANCE_ROOT` -- trusted default-branch copy
- `APPROVAL_URL` -- nominated scope-comment URL
- `HUMAN_SCOPE_RECEIPT` -- current human confirmation, not a stored grant

## ORIGIN and assignment

Resolve ORIGIN before any GitHub write:

1. Caller ORIGIN / INVOCATION_MODE
2. `GH_AW_*` or `GITHUB_ACTIONS` -> `unattended`
3. `gh api user --jq .login` succeeds -> `actor-session`
4. Else `unattended` (fail closed)

INTENT is `implement`.

The rest: https://github.com/microsoft/apm/blob/HEAD/.agents/skills/autopilot-issue-delivery-worker/SKILL.md