task-group-workflows

name	task-group-workflows
description	Create or update Linear-style task group trackers from specs, audits, reviews, plans, user requests, or implementation findings. Use when Codex needs to maintain a .tasks/YYYY-MM-DD-{task-group}-TASKS.md file.

Task Group Workflows

Core Workflow

1. Identify repository and task group.
2. Read source artifact: spec, plan, audit, review, issue, or user request.
3. Reuse existing .tasks/YYYY-MM-DD-{task-group}-TASKS.md when it matches.
4. Otherwise create one from .tasks/_template/TASKS.md.
5. Keep that file as the single source of truth.
6. Convert findings into task rows with ID, status, priority, owner, dependencies, task, acceptance criteria, and progress.
7. Add subagent/model routing only when it materially improves speed, quality, or parallelism.
8. Record verification commands, risks, and progress updates.

Task File Rules

• Name files as .tasks/YYYY-MM-DD-{task-group}-TASKS.md.
• Use stable IDs derived from the group.
• Use statuses: todo, doing, waiting, blocked, review, done.
• Use priorities: P0, P1, P2.
• Make dependencies explicit by task ID or none.
• Acceptance criteria must be externally checkable.
• Progress must be short and factual.
• Append Progress Log entries instead of relying on chat history.

Runtime Roles

• Main Integrator
• Explorer
• Worker
• QA

Handoff Contract

Every delegated task must include:

• Task ID and objective.
• Owned files or modules.
• Role and model tier.
• Inputs to inspect.
• Expected output or changed files.
• Exit criteria and verification command.
• Coordination note: do not revert unrelated edits.

Cost Controls

• Read only current task file and necessary source artifacts.
• Prefer one focused Explorer over overlapping explorers.
• Use summaries for large artifacts.
• Close subagents after their outputs are integrated.
• Record role/model/outcome in Progress Log.