← ClaudeAtlas

afk-speclisted

Turns an app idea into a repo afk can work on alone — picks the stack, writes docs/spec.md where every criterion carries the command that proves it, builds the skeleton that starts, the CI, the .afk.env, and sets up the milestones. Run once, at the very beginning, before the first wave. Triggers: /afk-spec, "I want to build <idea>", "set up the repo for this idea", "write the spec", "wave 0".
Warshoow/afk.sh · ★ 3 · AI & Automation · score 69
Install: claude install-skill Warshoow/afk.sh
# /afk-spec An idea is not executable. This skill makes it executable: a repo that starts, a gate that passes, and a list of criteria where **each one names the command that proves it**. After that, `/afk-wave` and `/afk-merge` loop with nobody watching. It is the only step of the loop worth reviewing awake: it picks the stack for everything else, and it writes the only judge the loop will ever have. ## The rule that holds up all the rest **`docs/spec.md` is written here and never changes again.** The later waves are only allowed to check boxes — not to add, not to reword, not to remove a criterion. Otherwise the loop declares itself the winner all by itself: whoever writes the criteria and whoever fills them are the same model. It is the only failure mode that shows up nowhere in the summary. ## 1 — The idea, and what it excludes One sentence for what the app does. Then, explicitly, **what it will not do**: anything not in the spec will never be built, and that is deliberate — the agent will not catch an omission, it will invent. Too big for a spec ("a Notion", "a CRM") → say so and propose the first slice that stands on its own. A loop over fifty criteria spends its nights piling up code nobody reviews. ## 2 — The stack The most boring one that holds. Two constraints, in this order: - **the gate runs with no external service.** Each ticket runs in a throwaway worktree: a live Postgres, a Redis, a `docker compose` and every ticket dies red for a reason that is