skills.rest
bbolek-ap
bbolek-apCOMMUNITY
Explore all skills by this author →
GitHub

validate-backlog

Cross-check WBS items against proposals, ADRs, and project context to produce a structured validation report.

Updated Apr 29, 2026
Search Tags:#validation#adr#backlog#traceability#epic#wbs
One-click install
npx skills add https://github.com/bbolek-ap/new-ai-native --skill validate-backlog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-backlog
Source: https://github.com/bbolek-ap/new-ai-native/tree/main/.claude/skills/validate-backlog
Command: npx skills add https://github.com/bbolek-ap/new-ai-native --skill validate-backlog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill verifies that a project's backlog is complete and consistent by cross-checking WBS items against proposals, architecture documents, ADRs, and project context, ensuring every item is traceable to work items and coverage is complete before estimation.

Core Features & Use Cases

  • Performs traceability, coverage, and structural checks against the backlog to identify gaps and misalignments.
  • Produces a structured validation report with findings classified as Blocking (must resolve before estimation) or Non-blocking.
  • Reads WBS summary, EPICs, ADRs, features, and context to validate alignment with architecture and proposal scope.

Quick Start

Run the backlog validation after producing or updating the WBS to generate a structured report of findings.

Frequently Asked Questions about validate-backlog

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

FAQPage Schema
How do I validate my WBS backlog for traceability and coverage gaps?▼

To validate your WBS backlog for traceability and coverage gaps, cross-check WBS items against proposals, architecture documents, and ADRs to identify inconsistencies and ensure full traceability before estimation.

What is backlog validation and when should I run it?▼

Backlog validation is the process of verifying completeness and consistency by checking WBS items against project context. You should run backlog validation after producing or updating a WBS, or before estimation, to ensure full coverage.

How do I check if my epics and WBS items align with architecture decisions?▼

To check if your epics and WBS items align with architecture decisions, cross-reference the WBS summary, EPICs, and ADRs to validate alignment with architecture and proposal scope, identifying any structural misalignments.

Can I automate backlog completeness checks before project estimation?▼

Yes, you can automate backlog completeness checks before project estimation by applying predefined traceability and coverage rules to the WBS, which produces a structured validation report classifying findings as Blocking or Non-blocking.

What is the difference between blocking and non-blocking backlog validation findings?▼

Blocking findings are gaps or inconsistencies in the backlog that you must resolve before estimation, while non-blocking findings are structural issues that do not prevent estimation but should still be addressed for full coverage.

Related Skills

Explore More Software Engineering Skills→
bbolek-apbbolek-ap

create-work-breakdown

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

Community
Advanced
ducminhgdducminhgd
3

project-planning

Decomposes product visions into hierarchical Agile execution plans with dependencies and estimates.

Community
Advanced
softsparksoftspark
161

documentation-standards

Validate KB Markdown files for frontmatter, naming, and English content.

Community
Intermediate
dannys-code-cornerdannys-code-corner
92

review-test-style

Review touched tests for style issues and coverage gaps.

Official
Intermediate