← ClaudeAtlas

afk-workflowlisted

The shared mental model the AFK orchestrator drives — decompose → plan → implement → review → PR → wait CI → PR-review → merge → document. Use whenever an AFK prompt mentions a phase, branch naming, sentinels, locks, or the lifecycle of a child issue / PRD.
Mo-Tamim/afk-agent · ★ 0 · AI & Automation · score 72
Install: claude install-skill Mo-Tamim/afk-agent
# Skill: afk-workflow This skill is the shared mental model for every phase the AFK orchestrator runs. Each prompt under `.afk/prompts/` corresponds to exactly one phase. ## Lifecycle of a PRD ``` PRD issue (label: afk-prd, ready-for-agent) └─ decompose ──> N child issues (label: afk-child + ready-for-agent) │ │ orchestrator picks unblocked children (resume `afk-in-progress` first, else `ready-for-agent`) up to max_parallel ▼ plan → implement → review ▼ pr (push branch, open PR/MR, link to child issue) ▼ pr_wait_ci (poll until green / red / timeout) ▼ pr_review (fresh agent, separate context) ▼ pr_merge (squash-merge, close child issue) ▼ next child … ▼ when the last child of a PRD is closed: document ──> dev docs + user docs (mermaid required) ▼ close PRD issue, label afk-done ``` ## Branching rules - Branch name from the planner: `{{branch_prefix}}-{{ISSUE_ID}}-{{kebab-slug}}` (≤ 60 chars). Defaults to prefix `afk/issue` from `config.yml`. - Always derive from the repo's default branch, detected via `git symbolic-ref refs/remotes/origin/HEAD`, falling back to the value in `con