epic-validate

Validate epic implementation against specifications and technical design.

2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/telum-ai/speck --skill epic-validate-telum-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-validate
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/epic-validate
Command: npx skills add https://github.com/telum-ai/speck --skill epic-validate-telum-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that an epic's implementation meets its original specifications, technical designs, and quality standards, preventing integration issues and ensuring business value delivery.

Core Features & Use Cases

  • Comprehensive Validation: Checks story completion, architectural adherence, integration points, and quality gates.
  • Automated Reporting: Generates detailed validation and punch list reports.
  • Use Case: After all stories for a new feature epic are completed, run this Skill to get a go/no-go decision on whether the epic is ready for release, highlighting any remaining issues.

Quick Start

Run the epic-validate skill to check the implementation of the 'User Authentication' epic.

Frequently Asked Questions about epic-validate

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

FAQPage Schema
How do I validate epic implementation against technical design after story completion?

Epic validation checks completed stories against original specifications and technical designs. It orchestrates parallel subagent execution to verify story completion, epic goal achievement, architecture adherence, integration testing, code quality, and Cursor rules compliance.

What is included in an epic validation report for quality assurance?

An epic validation report includes detailed checks for story completion, architecture verification, integration testing, code quality, and Cursor rules compliance. It generates a detailed validation report and a punch list of remaining issues.

When should I run epic validation checks in my software engineering workflow?

Run epic validation after all stories for a new feature epic are completed. This ensures the implementation meets original specifications, technical designs, and quality standards, preventing integration issues and ensuring business value delivery.

Does epic validation check architecture verification and integration testing together?

Yes, epic validation performs architecture verification and integration testing concurrently. It orchestrates parallel subagent execution for comprehensive checks including story validations, epic goal achievement, code quality, and Cursor rules compliance.

Can I get a go/no-go release decision for a feature epic automatically?

Yes, running epic validation provides an automated go/no-go decision on whether your epic is ready for release. It evaluates implementation against specifications and generates a punch list report highlighting any remaining issues to address.

What are the limitations of automated epic validation for integration testing?

Automated epic validation focuses on checking implementation against specifications, technical designs, and Cursor rules compliance. It generates a punch list of remaining issues but requires completed stories and existing technical design documentation to function effectively.