task-workflowlisted

Core loop for executing tasks from the tasks.md board — claim, plan checkpoint, worktree, implement, quality gates, draft PR, bounded review-and-fix rounds, optional gated merge, human notification. Use whenever asked to work the task board, run the next task, or continue a task in progress.
digitaldreams/tuhin · ★ 0 · AI & Automation · score 72

Install: claude install-skill digitaldreams/tuhin

# Task Workflow The process for taking one task from `tasks.md` to a reviewed draft PR. One run of this skill advances exactly one task as far as it can go, then stops. ## Board rules (non-negotiable) 1. **tasks.md has one writer.** All board edits (claims, status changes, plan comments) happen in the MAIN repo checkout, in manager context. Implementation agents working in worktrees NEVER edit tasks.md — their copy is stale by design. 2. **No agent-to-agent conversation.** Agents communicate only through artifacts: task status, plan comments on the board, the PR diff, and PR review comments. 3. **PRs are always draft, and merging is off by default.** Never mark a PR ready for review, never push to the base branch. Merge only when `AUTO_MERGE=gated` and every condition in step 9 holds — otherwise the human merges. 4. **Every stop notifies the human** (see Notification below). 5. **One driver at a time.** `/task-next` and `/task-auto` both claim "the first actionable task". Running both against one board is a claim race. Pick one. ## Knobs `workflow/.env` at the repo root holds the developer's preferences. Read it at the start of every run; missing or unparseable → use these defaults, always with `AUTO_MERGE=off`. The `requirement-intake` skill creates the file on first run. | key | default | effect | |---|---|---| | `PLAN_GATE` | `medium` | which plan sizes stop for approval | | `AUTO_MERGE` | `off` | `off` \| `gated` — see step 9 | | `MERGE_TARGET` | `