action-tasklisted

Use when the user wants Claude to actually DO / execute / action / run / work on / pick up / start / tackle a SPECIFIC task that already lives in the claude-tasks queue — e.g. "action the staging task", "do the onboarding brief", "work on the billing one", "pick up X from the queue", "start the migration task". Resolves the phrase to a single brief, moves it to in-progress, executes it end-to-end against its success criteria, and marks it done (or escalates if it hits something only the user can decide). NOT for adding a task (use queue-task / raw-capture) or offloading the current session's loose ends (use handoff).
kmmwren/claude-tasks · ★ 0 · AI & Automation · score 70

Install: claude install-skill kmmwren/claude-tasks

# action-task — execute one specific brief from the queue The user names a task; you find it, do it, and close it out. The must-be-consistent mechanics (frontmatter edits, the file move, the locked commit, the `ESCALATED —` token) live in the tested `scripts/transition.py` — **always go through it; never hand-edit `status:` or run raw git** in the queue (that bypasses the cross-process lock and can corrupt concurrent writes). All commands below resolve the queue via `$CLAUDE_TASKS_DIR` → nearest `.tasks/` → `~/tasks`, or pass `--root <path>`. ## The flow ### 1. Resolve the phrase to ONE brief ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/transition.py" resolve "<what the user said>" ``` Ranks actionable briefs (ready / in-progress / parked — never inbox) by relevance; exact id wins outright. Then: - **One clear top hit** → use it, name it back ("Actioning `<id>` — <title>"), continue. - **Several close hits** → show the top 3–4 (id + title + status) and ask which. - **No hits** → say so, show the closest if any, and offer to add it (`queue-task`). Don't invent a brief and execute it. ### 2. Load the full brief + its context Read the resolved file in full, then pull the context it points to (parent/related briefs, linked repos, PRs, docs) so you execute with zero guesswork. The **Success criteria are the contract** — that list is what "done" means. ### 3. Gate on autonomy + blockers (before touching anything) - `autonomy: full`, no unmet `blockers:` → proceed. - `auto