Feature guide

Build a work breakdown structure in KaidoPlan

Turn a release into named tasks with clear deliverables and explicit dependencies.

Start with deliverables

Break a release into work you can verify: a signed build, a clean-install result and published release notes. A group describes an area of work; a leaf task should have a concrete result. The public sample is deliberately small so you can see where each task fits.

kaidoplan task list --file release-demo.kaido --lang en
kaidoplan task list --file release-demo.kaido --json

Link tasks that cannot start together

In the example, Sign and notarize follows Build release candidate. The release notes follow the install-guide update and can progress while the release build is being tested. Capture this as dependencies in the plan so a change in one branch does not make the other look blocked by default.

Validate before delegating

Ask the person or agent who will do each task to confirm the expected output and prerequisites. Then compute the schedule and compare it with any hard date. If a task is too broad to verify or has work that can run separately, split it before treating the plan as a delivery commitment. Keep the rationale for unusual dependencies in task notes.