afk-prdlisted

# Skill: afk-prd Take the conversation context — typically the output of `/afk-grill` — and produce a PRD issue on the project's tracker, labelled so the AFK orchestrator can pick it up. Do **not** re-interview the user. Synthesize what you already know. This skill is the universal counterpart of [`mattpocock/to-prd`](https://www.skills.sh/mattpocock/skills/to-prd): same template, tracker-agnostic, and wired into the AFK label vocabulary. ## Prerequisites This skill assumes `.afk/config.yml` exists. If it doesn't, ask the user to run `/afk-setup` first and stop. Read these values from `.afk/config.yml`: - `tracker:` — `github` or `gitlab` - `repo:` — slug (`<owner>/<repo>`) - `labels.ready_for_agent:` — usually `ready-for-agent` - (look up the `afk-prd` label name; defaults to `afk-prd`) Use the `afk-tracker-issue` skill for the actual issue-create call. Do not invoke `gh` or `glab` yourself. ## Process ### 1. Ground the PRD in the codebase Explore the repo briefly to understand the current state. Use the project's domain glossary (`CONTEXT.md` and any `CONTEXT-MAP.md`) vocabulary throughout. Respect any ADRs in the area you're touching — if a decision contradicts an ADR, surface that and stop. ### 2. Sketch the major modules List the modules you'll need to build or modify. Actively look for opportunities to extract **deep modules** that can be tested in isolation. > A deep module encapsulates a lot of functionality behind a simple, > testable interface that rar