afk-documentlisted

# Skill: afk-document The final phase of a PRD's lifecycle. After every child issue has merged, the orchestrator spawns a fresh agent that produces two documents and ships them via a docs PR. ## Inputs (passed by the runner) | Variable | Meaning | |-----------------|-----------------------------------------------------------| | `PRD_ISSUE` | The parent PRD issue number. | | `PRD_TITLE` | The PRD's title. | | `PRD_SLUG` | Kebab-slug used in filenames. | | `PACKAGE_PATH` | The repo path the PRD primarily touched (from the PRD). | | `CHILD_ISSUES` | Space-separated list of merged child issue numbers. | | `CHILD_PRS` | Space-separated list of merged PR numbers. | | `BRANCH` | `afk/docs-prd-<N>-<slug>`. | | `WORKTREE` | Per-issue worktree path (cwd is set to this). | | `REPO` | Tracker repo slug. | ## Outputs Two markdown files under the package: ``` <PACKAGE_PATH>/docs/dev/<prd-slug>.md <PACKAGE_PATH>/docs/user/<prd-slug>.md ``` Plus a small index entry in `<PACKAGE_PATH>/docs/README.md` (create if absent) linking to both. ## What to write ### Developer doc (`docs/dev/<prd-slug>.md`) Audience: a future contributor who will modify or extend this code. 1. **Overview** — one pa