afk-decomposelisted

# Skill: afk-decompose Break one PRD into N vertical-slice child issues, each one independently implementable end-to-end. The runner parses your `<children>` payload and creates the issues on the tracker; you do **not** call the tracker CLI yourself in this phase. ## Vertical-slice rules - A slice **cuts through every layer** of the change — schema, API, UI, tests — for one narrow capability. - A slice is **demoable on its own**: shipping just this PR moves the product forward observably. - Prefer many thin slices over few thick ones. A child should fit in ≤ ~300 LOC of diff and one PR review. - A slice is **AFK-implementable** by default. Use `needs-human` only when the slice genuinely needs a human (visual approval of a generated mockup, license decision, secret rotation, infra change that requires admin credentials). ## Process ### 1. Read the parent PRD Use the `afk-tracker-issue` skill to fetch the PRD by `ISSUE_ID`. Read its body and any clarifying comments. Read referenced ADRs and `CONTEXT.md` from the package the PRD touches (`Package path:` field in the PRD). ### 2. Draft slices For each slice, decide: | Field | Constraint | |--------------|----------------------------------------------------------------------| | Title | Imperative, one line, ≤ 80 chars. Includes package / module. | | Body | What to build, acceptance criteria, blocked-by, parent.