DeliveryAgent systems topic

Specifications

Specifications convert intent into reviewable requirements, acceptance scenarios, constraints, and non-goals. For agent-assisted delivery, a specification should be precise enough to guide planning and validation without pretending that uncertain decisions are already settled.

Apply the lifecycleReview sources

Questions to answer

Resolve these before adding tools, frameworks, or automation.

  • What user outcome and acceptance scenarios define completion?
  • Which constraints and non-goals prevent plausible but wrong implementations?
  • How will requirement changes propagate to plans, tasks, tests, and documentation?

Implementation lifecycle

Build the evidence in this order

  1. 01

    Define

    Capture outcomes, actors, scenarios, constraints, non-goals, and unresolved questions.

  2. 02

    Refine

    Remove ambiguity and contradictions before generating detailed implementation work.

  3. 03

    Verify

    Trace tests and shipped behavior back to explicit acceptance scenarios.

Artifacts to maintain

  • spec.md
  • PRD
  • acceptance scenarios
  • non-functional requirements

Continue through AgentAtlas

Evidence ledger

Primary documentation behind this guide

GitHub

GitHub Spec Kit

The specification-driven workflow from intent through specification, plan, tasks, implementation, and quality checks.

AGENTS.md

AGENTS.md specification

Portable repository-level instructions that keep implementation constraints and verification commands available to coding agents.

Next topic

Plans