skills.rest
RDEWAI
RDEWAIOFFICIAL
Explore all skills by this author →
GitHub

validate-stories

Validate sprint backlog completeness and quality before sprint planning.

5|1|Updated Sep 23, 2025
Search Tags:#agile#quality-gates#dependency-check#scrum-master#sprint-backlog#backlog-audit#story-validation
One-click install
npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill validate-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-stories
Source: https://github.com/RDEWAI/Redefining-DataEngineering-With-AI/tree/main/chapter-6/scrum-master-plugin/skills/validate-stories
Command: npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill validate-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

Sprint backlogs with missing sections, broken dependencies, or incomplete closure stories cause blocked sprint execution, rework, and missed delivery commitments. This Skill eliminates those risks by automatically validating backlog artifacts against strict completeness and quality standards.

Core Features & Use Cases

  • Full Backlog Structure Validation: Checks that the backlog index has all 7 required sections, epic directories exist with valid EPIC files, and every epic has at least one story file.
  • Story Quality & Traceability Checks: Validates user story format, minimum acceptance criteria count, upstream artifact references, dependency consistency, sprint allocation, story point estimates, and required sections like Testing and How to Test.
  • Layer Closure & Quality Gate Enforcement: Enforces medallion layer closure rules (performance-optimization, integration-test stories with Airflow DAG and Unity Catalog wording, Spark Expectations end-to-end coverage) and reports issues by severity (CRITICAL/WARNING/INFO) with actionable fix suggestions.
  • Use Case: A Scrum Master can run this validation before sprint planning to catch missing sections, broken dependency edges, or absent closure stories that would otherwise block the development team during execution.

Quick Start

Use the validate-stories skill to review your sprint backlog directory for missing sections, broken dependencies, and quality gaps before committing to sprint planning.

Frequently Asked Questions about validate-stories

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

FAQPage Schema
How do I validate my sprint backlog for missing sections before sprint planning?▼

To validate your sprint backlog, scan your epic directories and backlog index files to ensure all 7 required sections exist and every epic contains at least one story file. This backlog audit prevents blocked sprint execution by catching missing artifacts early.

What is story validation and how does it enforce quality gates in agile?▼

Story validation is the process of checking user story format compliance, minimum acceptance criteria count, and valid dependency edges. It enforces agile quality gates by verifying upstream artifact references and ensuring stories are implementable and testable.

How do I check sprint backlog dependencies and story point estimates?▼

You can check sprint backlog dependencies and story point estimates by scanning story files for valid dependency edges and sprint allocations. This dependency check ensures upstream artifact references are consistent and story points are properly allocated.

Can I use this to enforce medallion layer closure rules and Spark Expectations coverage?▼

Yes, you can enforce medallion layer closure rules by validating integration test stories for Airflow DAG and Unity Catalog wording. It also checks for Spark Expectations end-to-end coverage and valid YAML verification blocks to ensure testability.

What is the best way to audit a sprint backlog for broken dependency edges?▼

The best way to audit a sprint backlog for broken dependency edges is to run an automated validation script that scans epic directories and reports issues by severity. It provides actionable fix suggestions for CRITICAL and WARNING level dependency inconsistencies.

Why does my sprint execution get blocked by malformed backlog artifacts?▼

Sprint execution gets blocked by malformed backlog artifacts because missing sections, broken dependencies, or incomplete closure stories cause rework. Running a backlog audit before planning catches these quality gaps and missing upstream artifact references early.

Related Skills

Explore More Product & Management Skills→
hoavdchoavdc
21

codexkit-backlog-refiner

Transform raw backlog items into INVEST-compliant user stories with acceptance criteria.

Community
Intermediate
xloxn69xloxn69
7

agileflow-sprint-planner

Generate a balanced Markdown sprint plan from backlog stories and team capacity.

Community
Intermediate
RDEWAIRDEWAI
5

create-integration-test

Generates integration tests for Docker-based apps with CI/CD pipelines and automated workflows.

Official
Advanced
SynkraAISynkraAI
3.1k

aiox-sm

Automate Scrum Master tasks from PRD-based user stories to sprint planning.

Official
Intermediate