tasks

name	tasks
description	Task breakdown — dependency-ordered work list from an approved plan
when_to_use	Use when an approved implementation plan (from /plan) needs to become an ordered, dependency-aware checklist on the GitHub issue before /schema, /code, or /wire run — the pipeline Tasks stage, not spec writing (/spec) or architecture (/plan). Triggers on: break it down, ordered task list from an approved plan, task breakdown, decompose the plan, pipeline Tasks stage.
argument-hint	<feature>|#N [product]

Tasks — Dependency-Ordered Breakdown

Turn an implementation plan into an ordered, dependency-aware task list mapped to pipeline stages — so /schema → /code → /wire execute against a concrete checklist. Sits between /plan and /schema. Resumable; skippable for trivial work.

Usage

• /tasks #42 — breakdown from issue number
• /tasks billing — breakdown from feature name
• /tasks billing hogwarts — product-scoped

Argument: $ARGUMENTS

Instructions

1. READ — Load the plan

gh issue view <N> --repo <repo> --comments

Require an ## Implementation Plan comment (from /plan). If missing, stop and route back to /plan. Extract: pattern choices, architecture decisions, mirror target, file plan (from the spec).

2. DECOMPOSE — Order the work

Break the plan into atomic tasks, each:

• mapped to its pipeline stage (schema, code, wire, check)
• ordered so dependencies come first (schema before actions before UI)
• carrying its own verify step (the stage's exit gate)

Use .claude/templates/tasks.md as the shape.

3. PUBLISH — Write the checklist to the issue

gh issue comment <N> --repo <repo> --body "<task breakdown>"

Header ## Task Breakdown, render as a GitHub checklist (- [ ]) grouped by stage so progress is trackable on the issue. End with *Generated by tasks stage. Ready for implementation.*.

4. EXIT GATE

Task-breakdown comment exists on the issue: every task mapped to a stage, ordered by dependency, each with a verify step. Ready for /schema.

When to skip

A one- or two-file change doesn't need a breakdown — go straight to /schema or /code. The pipeline is a menu, not a mandate.