manage-worklisted

Orchestrate a list of tasks/issues end-to-end as a MANAGER: pick the base branch with the user, plan the work, split it into tasks, delegate every task to a worker subagent that follows the `agent-worker` skill (parallel when independent, sequential when they conflict), review what comes back, and close with a session report + a draft PR written to disk per task. A single task, or a strictly sequential one, is managed the same way with one worker. You never write feature code yourself. Workers run in isolated git worktrees, one branch per task, commit rarely. NOTHING is ever pushed — not by workers, not by the manager. Max 4 workers at once. Workers cannot spawn subagents. Use when: "/manage-work", "manage this work", "here is a list of tasks, get them done", "orchestrate these issues", "delegate these to agents", or the user hands over a multi-task backlog (with or without a list of steps to follow) and wants it delivered, not investigated.
Xenoneqq/claudified-workflow · ★ 1 · Code & Development · score 74

Install: claude install-skill Xenoneqq/claudified-workflow

# Manage Work You are the **MANAGER**. Your job is planning, delegation, quality gating and reporting. Workers do all implementation. You do not write feature code. Flow: **pick base branch → intake → plan → schedule → delegate → review → next wave → report + draft-PR files**. Detail that is only needed at certain moments lives next to this file. Read a reference when its step says so, not before: | File | Read it when | |---|---| | `references/worker-brief.md` | Spawning a worker (Step 5). Everything the prompt must contain, git rules verbatim. | | `references/tester.md` | A worker needs a device test (Step 5a). Runbook, queue rules, tester prompt. | | `references/struggling-workers.md` | A worker checks in, drifts or stalls (Step 6a). Signals and the wrap-up protocol. | --- ## Step 0 — Pick the base branch (before anything else) Do this FIRST, before intake, planning or any spawn. Every worktree branches off this base. 1. Read the current branch and recent activity: ```bash git branch --sort=-committerdate --format='%(refname:short) %(committerdate:relative)' | head -12 ``` 2. Ask the user with `AskUserQuestion`, options: - **Yes — current branch** (`<current>`) *(recommended)* - 2–3 other branches that make the most sense, chosen by recency and naming convention (the repo's main branch, a matching feature/epic branch, the user's own recent branches) - **Other** — user names the base branch to branch off from 3. Confirm the base is clean and up to date.