rc-tasks-workflow

# Execute RC tasks as a Claude Workflow Run every `task_NN.md` of a feature slug through the Claude Code **`Workflow`** tool — each task implemented, verified, and tracked, orchestrated by Claude one task at a time. **Invoking this skill is the explicit opt-in to call the `Workflow` tool.** Never call it for unrelated work. This is **Claude Code only** — the `Workflow` tool does not exist in other agents (Codex, Droid, Cursor). On those hosts, run each task through the `rc-execute-task` skill in dependency order instead. ## When to stop and defer - **No `Workflow` tool available** (non–Claude Code host) → stop and tell the user to run each task via the `rc-execute-task` skill in dependency order. Do not emulate the workflow by hand. - **Tasks not yet authored** (`.rc/tasks/<slug>/` missing, or no `task_NN.md`) → stop; point at `/rc-create-tasks`. ## Phase 1 — Resolve the slug 1. If the argument is a **slug**, use `.rc/tasks/<slug>/` directly. 2. If it is a **Linear key** (the rc-board gancho), grep `linear_key:` across `.rc/tasks/**/task_*.md`; the matching files share one directory — that directory name is the slug. No local match → stop and say so (local task files are the source of truth; never reconstruct tasks from Linear text). 3. Confirm `.rc/tasks/<slug>/` holds `_tasks.md` and `task_01.md … task_NN.md`. ## Phase 2 — Validate & order 1. Run the bundled task validator: `node "$CLAUDE_PLUGIN_ROOT/scripts/validate-tasks.mjs" --slug <slug>`; if it exits non-zero, ...