Build a work breakdown structure with AI
Turn an agreed project scope into a numbered outline and a companion dictionary that explains what each team is expected to deliver.
Build a work breakdown structure with AI when a project charter has been signed off but a broad deliverable still means different things to different people. Give create-work-breakdown-structure the agreed outcomes. It draws up a hierarchy and a separate dictionary for the team that has to deliver them.
Consider a handbook revision: a print-ready file and an approved manuscript belong in the same project, but accepting one does not mean the other is ready. Numbering them separately lets the editor and designer agree on their handover before either estimates the work.
What it does
- Group the charter’s deliverables into branches and spot work that none of the branches covers.
- Give each work package a code that stays the same in the outline and dictionary.
- Record who owns the result and what the reviewer will check before accepting it.
- Mark estimates as provisional where the team lacks a reliable comparison.
- Map which package supplies an input to another before proposing a delivery date.
Install and use
- Install the skill in a file-capable agent and supply an approved charter. No scheduling account is required.
- Ask: “Break this handbook project into deliverables and show what the printer needs from the editor.”
- Review the outline beside its dictionary. Ask the people doing the work to confirm assumptions and correct dependencies.
FAQ
Source
Made by Philipp Thoss. Original skill: create-work-breakdown-structure, published on GitHub under the MIT licence.
View on GitHub