create-work-breakdown

Generate and extend backlog files under .project/backlog/ using canonical WBS templates.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/bbolek-ap/new-ai-native --skill create-work-breakdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-work-breakdown
Source: https://github.com/bbolek-ap/new-ai-native/tree/main/.claude/skills/create-work-breakdown
Command: npx skills add https://github.com/bbolek-ap/new-ai-native --skill create-work-breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define a consistent hierarchical backlog structure (EPICs > Features > Business Stories) using canonical templates, depth rules, and a standard numbering scheme to ensure clarity and traceability.

Core Features & Use Cases

  • Canonical templates for EPIC, Feature, and Story files to enforce structure and consistent naming.
  • Depth and numbering rules to ensure predictable backlogs and easy cross-reference.
  • Backlog file generation and guidance for Delivery Lead workflows under .project/backlog/.

Quick Start

Create a new WBS using the canonical templates to generate backlog files under .project/backlog/

Frequently Asked Questions about create-work-breakdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a project backlog with EPICs, Features, and Business Stories?

Structure a project backlog by defining a consistent hierarchical WBS using canonical templates for EPICs, Features, and Business Stories. This enforces standard naming conventions and predictable depth rules to ensure clarity and traceability across projects.

What is a Work Breakdown Structure and when do I need it for backlog planning?

A Work Breakdown Structure (WBS) is a hierarchical decomposition of project deliverables. You need it for backlog planning to apply depth rules, generate organized files under .project/backlog/, and ensure traceability across your EPICs and Business Stories.

How do I generate backlog files and enforce naming conventions for Delivery Lead workflows?

Generate backlog files by applying canonical WBS templates to create or extend files in .project/backlog/. This guides Delivery Lead workflows by enforcing standard numbering schemes and content depth for each Business Story and Feature.

What is the best way to ensure traceability and completeness for business stories in a WBS?

Ensure traceability and completeness by applying a Story Coverage Checklist to your WBS. Canonical templates specify content depth and standard numbering schemes, making cross-referencing predictable across EPICs, Features, and Business Stories.

Can I extend an existing backlog structure instead of creating a new WBS from scratch?

Yes, you can extend an existing backlog structure. The canonical templates apply to backlog planning across projects to generate new files or extend existing ones within .project/backlog/ while maintaining consistent depth and numbering rules.