Task Graphs

Purpose

Task graphs are for opt-in control-plane, slicing, multi-agent, or staged work. Normal Direct Implementation Mode work does not start with a dated task graph.

Task graphs turn raw intent into hard-scoped work before agents edit files.

Naming

YYYY-MM-DD-short-kebab-title.md

Template

# YYYY-MM-DD Short Title

Task Graph ID:
Prompt ID:
Date:
Owner:
Status:

## Mission

## Background

## Scope

## Non-goals

## Tasks

| Task | Agent | Mode | Allowed Paths | Forbidden Paths | Depends On |
| ---- | ----- | ---- | ------------- | --------------- | ---------- |

## Parallelizable Tasks

## Serial Dependencies

## Agent Assignment

## Acceptance Checks

## Validation Commands

## Risk Register

## Integration Plan

## Follow-up Backlog

Rules

• If opt-in work touches more than one ownership area, assign separate workers.
• If a task needs app contract, API, DB, auth, billing, deployment, or shell routing changes, consider RFC or ADR first.
• Integrator Agent should review multi-worker output before merge.