tdmcp-backlog-campaign

Backlog campaign delivery is automated using a ledger-driven, wave-driven workflow that coordinates discovery, design, build, QA, and release phases while preserving state across sessions. This enables resumable, multi-wave shipping for long-running feature backlogs.

A wave-driven workflow computes the next release wave and orchestrates the delivery pipeline foundations-first, then executes parallel work. It structures backlog campaigns into manageable phases to ship features cohesively across multiple releases.

Backlog orchestration supports idempotent restarts by relying on a backlog ledger file to preserve progress. You can re-run the campaign from the last checkpoint, ensuring no completed wave or phase work is duplicated.

Yes, a backlog ledger file is required to manage wave progression and release state. The campaign uses this ledger to seed the workspace with policies, track progress, and enable checkpoint-driven shipping.

To start a backlog campaign, create a backlog discovery file and run the campaign tool. This seeds the workspace with a ledger and policy, then begins Phase 0 to locate, plan, and run delivery waves.

Yes, backlog orchestration coordinates planning, design, building, integration, QA, and release roles. It drives a guided campaign that spans all these phases to ship features cohesively across multiple releases.