afk-amendlisted
Install: claude install-skill Mo-Tamim/afk-agent
# Skill: afk-amend
All four triggers — a wrong ADR, a wrong PRD, a misunderstanding at the
time the ADR was written, or the designer changing their mind — are the
**same event**: *a recorded decision changed after it was written down*.
AFK is forward-only. There is no "rewind". The correct fix depends
entirely on **how far the decision has already travelled** through the
pipeline, so this skill first classifies the lifecycle state, then
propagates the change from there.
The one rule that holds in **every** branch:
> The corrected ADR / `CONTEXT.md` must land on the **default branch**
> before any `decompose`, `plan`, or `implement` agent runs again. Every
> phase derives its worktree from `origin/main`
> (see [`afk-workflow`](../afk-workflow/SKILL.md) branching rules), so an
> ADR sitting on an unmerged branch is **invisible** to every agent and
> the old, rejected decision gets re-implemented.
## The decision tree
```mermaid
flowchart TD
Q{Where is the changed decision now?}
Q -->|"ADR/CONTEXT only, no PRD yet"| A["Rewrite ADR as superseding + update CONTEXT, merge to main"]
Q -->|"PRD open, not decomposed"| B["Fix ADR on main, then edit the tracker issue body"]
Q -->|"Decomposed, no child started"| C["Fix ADR on main, edit PRD, close+recreate affected children, re-decompose"]
Q -->|"Children in flight"| D["Fix ADR on main, edit/close open children, add corrective children or follow-up PRD, rebase in-flight"]
Q -->|"PRD closed / shipped (afk-done)"| E["Forw