Create a comprehensive, hierarchical Work Breakdown Structure with deliverables, work packages, and clear ownership for any project type.
I need to create a Work Breakdown Structure for [PROJECT_NAME], which is in the [INDUSTRY:select:technology,construction,marketing,healthcare,manufacturing,finance,education,events,consulting,government,retail,other] sector. The primary deliverable or outcome of this project is [PRIMARY_DELIVERABLE]. The project has an estimated duration of [DURATION] and involves [TEAM_SIZE:select:1-5 people,6-15 people,16-50 people,50+ people]. The key objectives we need to achieve are [KEY_OBJECTIVES]. Any major constraints or boundaries I should note include [CONSTRAINTS_OR_BOUNDARIES?]. Please decompose this project to [DECOMPOSITION_LEVEL:select:Level 2 (phases only),Level 3 (phases and deliverables),Level 4 (phases/deliverables/work packages),Level 5 (full decomposition)] depth. For each element in the WBS, use the standard WBS coding system where the project is 1.0, major phases are 1.1/1.2/1.3, and so on. Apply the 100% rule throughout, meaning each parent element must fully encompass all work represented by its children, with no gaps or overlaps. Each work package at the lowest level should represent roughly [WORK_PACKAGE_SIZE:select:8-40 hours,40-80 hours,1-2 weeks,2-4 weeks] of effort and be assignable to a single owner. For the output format, present this as a [OUTPUT_FORMAT:select:hierarchical outline with indentation,table with columns for WBS code/name/description/owner,visual tree diagram in ASCII art,all three formats combined]. Include a brief description for each element that clarifies what work it contains and what completion looks like. If certain elements seem ambiguous or could be interpreted multiple ways based on industry best practices, note those assumptions. At the end, provide a summary showing the total number of work packages, suggested phase sequence or dependencies worth noting, and any recommendations for how this WBS could be further refined once more project details become available.
Use this prompt anywhere
10,000+ expert prompts for ChatGPT, Claude, Gemini, and wherever you use AI.
Get Early AccessA work breakdown structure breaks a project into smaller, manageable pieces. It starts with the final deliverable at the top and decomposes downward through work streams, sub-deliverables, and individual work packages. This hierarchy gives every team member a clear view of what needs to happen and where their tasks fit.
This WBS template generates a structured breakdown for your [PROJECT_NAME] based on your [PRIMARY_DELIVERABLE] and project constraints. You choose the [DECOMPOSITION_LEVEL] to control how deep the hierarchy goes, from high-level phases down to individual work packages. The template follows the 100% rule, which requires that every level captures all the work in scope with nothing missing and nothing extra.
Two main approaches exist for organizing a WBS. Deliverable-based structures group work by what gets produced. Phase-based structures organize around project stages like initiation, planning, execution, and closeout. Your choice depends on whether the project centers on tangible outputs or sequential workflows.
Pair this with a project timeline to schedule your work packages and a scope of work to define boundaries. Use a project management plan for the execution framework. Build your work breakdown structure in Dock Editor to keep scope planning connected to your other project documents.
Enter [PROJECT_NAME] and [PRIMARY_DELIVERABLE] to establish what the WBS will decompose. Add [KEY_OBJECTIVES] to guide which deliverables and work streams the breakdown should emphasize.
Specify [INDUSTRY] and [TEAM_SIZE] so the template scales appropriately for your context. Add [DURATION] to help determine how granular the breakdown needs to be for your timeline.
Choose your [DECOMPOSITION_LEVEL] to control hierarchy depth. Set [WORK_PACKAGE_SIZE] following the 8/80 rule to keep bottom-level items between 8 and 80 hours of effort.
Use [CONSTRAINTS_OR_BOUNDARIES] to define what falls inside and outside the WBS scope. This prevents scope creep by making explicit what the project does not include.
Select your [OUTPUT_FORMAT] for the final structure. Review the generated WBS against the 100% rule to confirm every deliverable is captured and no work falls outside the hierarchy.
A development team uses this template to break down a product release into epics, features, and user stories. The WBS maps every component from API endpoints through UI screens to QA testing, giving sprint planners a complete task inventory.
A general contractor creates a WBS for a commercial renovation. The breakdown decomposes the project from major phases like demolition and framing through electrical, plumbing, and finishing work packages with cost accounts at each level.
A marketing director builds a WBS for a multi-channel product launch. The structure breaks the campaign into content creation, paid advertising, event planning, and analytics work streams with individual deliverables under each.
A management consultant uses the WBS to plan a strategic assessment for a client. The template decomposes the engagement into research, stakeholder interviews, analysis, and final presentation deliverables with clear work packages for each phase.
The 100% rule is the most important principle in WBS construction. It requires that every level of the hierarchy captures all the work defined by the project scope. The sum of child elements must equal exactly 100% of the parent element. No tasks can be missing, and no extra work should appear outside the structure.
The 8/80 rule sets boundaries for work package size. No work package should take less than 8 hours or more than 80 hours of effort to complete. This range prevents packages from being too small to manage individually or too large to track effectively. It keeps your WBS at a practical level of detail.
The most frequent mistake is incomplete breakdowns that violate the 100% rule by missing tasks or deliverables. Other common errors include going too deep and creating unnecessary complexity, allowing overlapping tasks that cause confusion about ownership, and using action verbs instead of nouns. A WBS should describe deliverables, not activities.
A deliverable-based WBS organizes work around what gets produced, grouping tasks by their output. A phase-based WBS structures the project around sequential stages like initiation, planning, execution, and closeout. Deliverable-based works best for projects with tangible outputs. Phase-based suits projects where timing and sequence matter more than individual products.
Most projects work best with three to five levels of decomposition. The top level shows the final deliverable, the next levels break it into work streams and sub-deliverables, and the bottom level contains work packages. Going deeper than five levels often creates unnecessary detail that slows planning without improving clarity.
[DECOMPOSITION_LEVEL] controls how deep the hierarchy goes, from broad phase-level breakdown to granular task-level detail. [WORK_PACKAGE_SIZE] sets the target scope for the lowest-level items, following guidelines like the 8/80 rule. Together these two settings determine whether you get a strategic overview or a detailed task list.
The WBS feeds directly into your project timeline by providing the task list to schedule. It draws boundaries from your scope of work to ensure the 100% rule holds. And it gives your project management plan the structural foundation for resource allocation, cost tracking, and progress reporting across the engagement.
Discover more prompts that could help with your workflow.
Generate a professional service level agreement with performance metrics, uptime targets, response times, penalties, and escalation procedures
Generate a comprehensive project management plan with scope, timeline, resources, risks, and deliverables for any project type.
Generate a structured business case that analyzes costs, benefits, risks, and alternatives to win executive approval for your project or investment
10,000+ expert-curated prompts for ChatGPT, Claude, Gemini, and wherever you use AI. Our extension helps any prompt deliver better results.