delivery-plan

To convert a task packet into a delivery plan, the Skill splits multi-domain work into single-domain subtasks, sequences them with dependencies and blockers, and generates a Definition of Done. This ensures clear handoffs and verifiable execution steps.

A Definition of Done in delivery planning specifies the verifiable criteria for subtask completion. You need it when orchestrating execution across multi-domain tasks to ensure clear sequencing, handoffs, and self-describing steps for Leads.

Splitting multi-domain work into self-describing subtasks involves breaking down a task packet so each subtask contains enough context for a Lead to execute without re-examining the repository, ensuring safe excerpting and clear orchestration.

Yes, the sectioned-v1 output format supports dependency and blocker tracking. It structures the ordered delivery plan by wrapping subtasks and metadata into a prescribed format that facilitates safe excerpting and orchestration.

Yes, you can use this delivery planning approach for multi-domain tasks without external dependencies. It operates independently to convert task packets into ordered subtasks with dependencies and a Definition of Done.

Delivery planning requires sequencing subtasks with blockers and dependencies to establish clear execution order and handoffs. This allows Delivery PMs to orchestrate work safely and ensure each step is verifiable against the Definition of Done.