DeliveryAgent systems topic

Plans

A plan translates approved intent into technical decisions, dependencies, sequencing, migration strategy, and verification. Strong plans preserve the why behind choices and identify uncertainty before work is fragmented into tasks.

Apply the lifecycleReview sources

Questions to answer

Resolve these before adding tools, frameworks, or automation.

  • Which technical decisions and dependencies determine the implementation order?
  • What can proceed in parallel and what has a hard dependency?
  • How will migration, rollback, observability, and validation work?

Implementation lifecycle

Build the evidence in this order

  1. 01

    Design

    Map each requirement to a technical decision and an explicit rationale.

  2. 02

    Sequence

    Order work around contracts, risk reduction, and independently verifiable increments.

  3. 03

    Review

    Challenge assumptions, missing dependencies, rollout risk, and validation coverage.

Artifacts to maintain

  • plan.md
  • architecture decisions
  • dependency graph
  • rollout plan

Continue through AgentAtlas

Evidence ledger

Primary documentation behind this guide

GitHub

Agentic SDD workflow

The ordered specification, clarification, planning, tasking, analysis, implementation, and convergence workflow.

Anthropic

Building effective agents

Planning transparency, composable workflow patterns, and matching orchestration complexity to task requirements.

Next topic

Tasks