# TASKS.md

> Decompose the plan into dependency-ordered work units with explicit inputs, scope, outputs, acceptance checks, ownership, status, and integration evidence suitable for people or delegated agents.

**Decision rule:** Create a separate task only when its output can be verified independently or its ownership and dependencies need explicit coordination. Avoid task fragmentation without a review boundary.

## How to use this template

- Replace every angle-bracket placeholder with project-specific evidence.
- Remove sections that do not apply instead of leaving ambiguous boilerplate.
- Link decisions to their specifications, tasks, tests, traces, and owners.
- Re-review this file when the workflow, authority boundary, or primary source changes.

## Task contract

> Use the same minimum outcome, scope, and verification contract for every work item.

- **Outcome:** <State the artifact or state change that completes the task>
- **Inputs and scope:** <List required context, allowed paths, dependencies, and explicit exclusions>
- **Acceptance:** <Define commands, tests, inspection, or evidence that verifies the output>

## Phases and dependencies

> Keep the executable queue aligned with the plan and specification.

- **Setup:** <List environment and harness tasks that unblock later work>
- **Foundational:** <List shared contracts, data, security, and architecture tasks>
- **Delivery phases:** <Group vertical work by user outcome and mark parallel-safe tasks>

## Work queue

> Make state, ownership, and handoffs visible without hiding unfinished work.

- **Ready:** <List unblocked tasks with owner and priority>
- **In progress:** <List active tasks, current evidence, and blocking questions>
- **Done:** <Record verification evidence, integration result, and links to changes>

## Integration and convergence

> Check the complete integrated outcome after every individual task and local verification passes.

- **Integration order:** <State merge, migration, release, and cross-task verification order>
- **Gap analysis:** <Compare completed work with the specification, plan, and acceptance checks>
- **Follow-up:** <Append discovered gaps with owners rather than hiding them in completion notes>

## Related AgentAtlas field guides

- [Tasks](https://agentatlas.dev/topics/tasks)
- [Plans](https://agentatlas.dev/topics/planning)
- [Multi-agent systems](https://agentatlas.dev/topics/multi-agent)

## Primary references

- [Agentic SDD workflow](https://github.github.com/spec-kit/reference/agentic-sdd.html) — The ordered specification, clarification, planning, tasking, analysis, implementation, and convergence workflow.
- [A2A protocol specification](https://a2a-protocol.org/latest/specification/) — Task identity, lifecycle, messages, status, artifacts, cancellation, and communication across agent boundaries.
- [Building effective agents](https://www.anthropic.com/engineering/building-effective-agents) — Planning transparency, composable workflow patterns, and matching orchestration complexity to task requirements.
- [Codex subagents](https://learn.chatgpt.com/docs/agent-configuration/subagents) — Subagent configuration, scoped roles, delegation behavior, and parallel work inside Codex.
- [Create custom subagents](https://code.claude.com/docs/en/sub-agents) — Specialized subagent configuration, context isolation, tools, permissions, and delegation patterns.

---

- Template version: 1.0.0
- Reviewed: 2026-07-26

Generated deterministically from reviewed AgentAtlas records.