Mo-Tamim

afk-amend

Re-propagate a decision that changed after it was recorded — an ADR that turned out wrong, a PRD that misstated the work, a misunderstanding baked in at ADR-creation time, or a designer who simply changed their mind. Routes the fix to the correct action based on how far the decision has already travelled down the pipeline, and guarantees the corrected ADR/CONTEXT lands on the default branch before any agent re-runs. Use when the user says "/afk-amend", "the ADR is wrong", "I need to change a decision", "the PRD misunderstood X", or "I changed my mind about <decision>".

afk-decompose

Convert one PRD issue into vertical-slice child issues using the tracer-bullet pattern. Use only inside the decompose phase prompt of the AFK orchestrator.

afk-document

Write developer-facing and user-facing documentation for a completed PRD, with mandatory mermaid diagrams. Use only inside the document phase prompt, after every child issue of a PRD has been merged.

afk-grill

Stress-test a design idea against the existing domain model, sharpen vocabulary, and capture decisions as ADRs and CONTEXT.md entries inline. Use when the user wants to "grill" a plan, design a new feature, or get challenged on a sketch before writing code. The output of this skill is what /afk-prd consumes next.

afk-prd

Take the current conversation context (typically from afk-grill) and synthesize a PRD, then publish it as an issue on the configured tracker (GitHub or GitLab) with the labels the AFK orchestrator expects. Use when the user has finished sketching a feature and says "/afk-prd", "write a PRD", or "publish this as an issue for AFK".

afk-run

Drive the AFK orchestrator from inside the IDE chat window — kick off a decompose, run one issue end-to-end, or process one batch — without the user having to leave chat for a terminal. Use when the user says "/afk-run", "run AFK on PRD N", "drive issue N", "let's process the queue", or generally wants to orchestrate AFK work without switching to a shell.

afk-setup

Scaffold the per-repo .afk/ orchestrator (config, labels, prompts, scripts, templates) and wire it into the repo's agent rules file. Use after installing the afk-agent skill bundle, when the user says "set up afk", "install afk in this repo", "/afk-setup", or wants to start using the AFK orchestrator on a new project.

Testing & QA Listed

afk-tdd

Vertical-slice red→green→refactor for AFK implementation phases. Use whenever the implement prompt is active and the touched code has a test runner.

afk-tracker-issue

Tracker-agnostic CRUD on a single issue — fetch, comment, label, close — wrapping `gh` (GitHub) or `glab` (GitLab) behind the same verbs. Use whenever the active AFK phase needs to read or write an issue and you don't want to hardcode the tracker.

Code & Development Listed

afk-tracker-pr

Tracker-agnostic PR/MR operations — push, open, poll checks, diff, review, merge — wrapping `gh` (GitHub) or `glab` (GitLab) behind one set of verbs. Use whenever the active AFK phase pushes a branch, opens a PR/MR, polls CI, performs a self-review, or merges.

afk-workflow

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.