Validate epics

Validate YAML epic backlogs against concept summaries for gaps and overlaps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Darkpunkki/v-forge --skill validate-epics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Validate epics
Source: https://github.com/Darkpunkki/v-forge/tree/main/.claude/skills/epic-validator
Command: npx skills add https://github.com/Darkpunkki/v-forge --skill validate-epics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate epic backlogs against the concept summary to ensure complete, non-overlapping scope and correct boundaries.

Core Features & Use Cases

  • Validates mapping between epics and core capabilities described in concept_summary.
  • Checks for coverage gaps, overlaps, and mis-scaled scope; reports inconsistencies across backlog and related artifacts.
  • Generates a validation report to docs/forge/ideas/<IDEA_ID>/runs/... and can patch backlog when allowed.

Quick Start

Execute the epic validator to compare the backlog against the concept summary and produce a report for review.

Frequently Asked Questions about Validate epics

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

FAQPage Schema
How do I validate epics against a concept summary for gaps and overlaps?▼

To validate epics, map the backlog capabilities against the concept summary to detect coverage gaps, overlaps, and mis-scaled scope, then generate a structured validation report for review.

What format is required for epic backlog validation?▼

Epic backlog validation requires a parseable epics file in YAML format with mandatory fields: id, title, outcome, description, in_scope, out_of_scope, release_target, priority, and tags.

Can I automatically patch backlog inconsistencies found during epic validation?▼

Yes, epic validation can generate optional backlog patches to fix inconsistencies, but it will only apply these patches when explicitly allowed by the user during execution.

How do I check epic boundaries and scope consistency across product artifacts?▼

Checking epic boundaries and scope consistency involves mapping capabilities to epics and comparing the backlog against related artifacts to identify mis-scoped work and boundary issues.

Where does the epic validation report get saved?▼

The epic validation report is saved to a specific directory path: docs/forge/ideas/<IDEA_ID>/runs/..., organizing outputs by the idea identifier for traceability.