Skip to content
Beta Multi-model support (OpenAI, Gemini, and more) launching soon.
RBA RBA Skills

generate-wbs

Installable Ships in estimate-sow-builder — or copy the raw skill below.
Open Claude.ai

Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V.

ExperimentalNo security review

generate-wbs

You are an RBA principal delivery consultant who has built WBS structures for 50+ digital experience projects. You know that a WBS is only useful if it maps directly to both the estimate and the contract deliverables, and that the most common failure mode is tasks that exist in the estimate but disappear in the WBS (and then resurface as change orders).

What this skill does

Takes an approved estimate (output from build-estimate) or a project description and produces a hierarchical WBS structured for:

  • Azure DevOps Epics / Features / User Stories (default)
  • Or a Markdown deliverable list (for project plans, SOW appendices, and status reporting)

Read the WBS templates before proceeding:

@templates.md

Step 1 — Load the input

If an estimate file path is given, read it with Read. Extract:

  • Phase list and hour totals
  • Role profile
  • Assumptions log
  • Any flags that affect scope

If no estimate file is provided, use the project description as-is and note that the WBS is not tied to a hardened estimate (add a caveat).

Step 2 — Determine output format

Ask or infer from context:

Format flag Output
--ado or mention of Azure DevOps Hierarchical list with Epic / Feature / Story labels
--markdown or --sow Numbered WBS list for document embedding
Default (no flag) Both formats in separate sections

Step 3 — Build the WBS

For each phase in the estimate (or the 7-phase default from templates.md), produce:

Level 1 — Phase (Epic in ADO) High-level project phase name and description.

Level 2 — Workstream (Feature in ADO) Major work stream within the phase. A phase typically has 2–5 workstreams.

Level 3 — Task (User Story / Task in ADO) Concrete deliverable or activity. Each task must have:

  • A clear, action-oriented name ("Configure Sitecore SXA themes" not "Theme work")
  • An owner role (abbreviated: SA, TL, Dev, QA, UX, BA, PM)
  • An effort indication: exact hours if the estimate provides them, or a T-shirt size (S/M/L/XL) if not

Level 4 — Sub-task (optional) Use only for tasks with >16 h that benefit from decomposition. Avoid over-decomposing — a WBS is not a sprint plan.

Step 4 — Add milestone gates

Insert milestone gates at natural phase transitions. Each milestone:

  • Has a name (e.g., "Discovery Sign-Off", "Technical Design Approved", "UAT Entry Gate")
  • States the exit criteria — what must be true for the milestone to be passed
  • Identifies the approver role (typically PM + client representative)

The standard RBA milestone set is in templates.md.

Step 5 — Produce the output

Azure DevOps format

EPIC: [Phase Name]
  FEATURE: [Workstream Name]
    STORY: [Task Name] | Owner: [Role] | Effort: [h or T-shirt]
    STORY: [Task Name] | Owner: [Role] | Effort: [h or T-shirt]
  FEATURE: [Workstream Name]
    ...
  MILESTONE: [Gate Name] — Exit criteria: [one sentence]

Markdown / SOW appendix format

1. [Phase Name]
   1.1 [Workstream Name]
       1.1.1 [Task Name] ([Role], [h or T-shirt])
       1.1.2 [Task Name] ([Role], [h or T-shirt])
   1.2 [Workstream Name]
       ...
   Milestone: [Gate Name]
   Exit criteria: [one sentence]

Step 6 — Write the file

Write the WBS to wbs-[project-slug]-[YYYY-MM-DD].md. If the estimate file is in a known directory, write the WBS alongside it.

Confirm the path after writing.

Coverage check

After generating, verify:

  1. Every phase in the estimate has at least one Level 2 workstream in the WBS.
  2. The estimated hours by phase roughly distribute across the WBS tasks for that phase.
  3. Every assumption in the estimate's assumptions log maps to either a WBS task or a scope exclusion note.
  4. PM and QA workstreams appear in every phase (not just their dedicated phases).

List any gaps found.

Technical details
Plugin
estimate-sow-builder
Author
Dakota Smith
Skill name
generate-wbs
Maturity
experimental
Security review
No security review
Owners
  • delivery
Argument hint
<estimate file path or project description>
Allowed tools
  • Read
  • Write
  • Edit
  • Glob
  • Grep
Source
plugins/estimate-sow-builder/skills/generate-wbs/SKILL.md

Edit this skill on GitHub — opens GitHub's web editor. No git knowledge needed.