description: Validate epic implementation against specifications and technical design after story completion.

The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).

User input:

$ARGUMENTS

Comprehensive validation that the epic delivers on its promises and integrates properly with the system.

Subagent Parallelization

This command benefits from parallel validation checks:

code

├── [Parallel] speck-auditor: "Verify all story validations pass"
├── [Parallel] speck-auditor: "Check epic goals from epic.md are achieved"
├── [Parallel] speck-auditor: "Verify architecture matches epic-architecture.md"
├── [Parallel] speck-auditor: "Test integration with other epics works"
├── [Parallel] speck-auditor: "Check code quality, tests, and docs"
├── [Parallel] speck-auditor: "Verify Cursor rules compliance"
└── [Wait] → Synthesize into epic-validation-report.md

Each auditor returns PASS | FAIL | PARTIAL with evidence.

Speedup: 5-6x compared to sequential validation.

•
Load epic completion status:
- •Original specs: epic.md, epic-tech-spec.md
- •Story status: Check epic-breakdown.md completion
- •Story validations: Check each story directory
- •Integration with other epics
- •If files missing: ERROR "Epic planning artifacts not found"

•

Story completion verification:

code

For each story in epic-breakdown.md:
- Check stories/[story-id]/validation-report.md
- Verify implementation matches spec
- Confirm tests passing
- Note any deviations

•
Multi-level validation:

Epic Vision Validation
- •Original value proposition achieved?
- •All user stories implemented?
- •Success criteria met?
- •Business value delivered?
Technical Implementation Validation
- •Architecture as designed?
- •All APIs implemented correctly?
- •Data models match spec?
- •Performance targets met?
Integration Validation
- •Works with dependent epics?
- •Provides promised interfaces?
- •No breaking changes?
- •End-to-end flows work?
Quality Standards Validation
- •Code quality gates passed?
- •Test coverage adequate?
- •Documentation complete?
- •Security requirements met?
- •Cursor rules compliance across stories?
•
Cursor rules compliance aggregation:
- •Check if .cursor/rules/ directory exists
- •If exists, load all rule files (*.mdc or *.md)
- •
  Aggregate rule compliance from story validation reports:
  - •For each story in epic, check if validation-report.md includes Cursor Rules section
  - •Collect compliance status for each applicable rule across all stories
  - •Identify patterns: rules consistently passed vs consistently violated
- •
  For epic-level validation, check rules that apply to epic scope:
  - •Cross-story integration patterns
  - •Epic-wide architectural rules
  - •Consistency rules (e.g., same patterns used across stories)
- •
  Generate epic-level rules compliance summary:
  code
  ## Cursor Rules Compliance (Epic Summary) **Rules Directory**: `.cursor/rules/` [exists/not found] **Total Rules**: [X] **Applicable to Epic**: [Y] | Rule File | Stories Using | Pass Rate | Common Issues | |-----------|---------------|-----------|---------------| | [rule.mdc] | 8/8 | 100% (8/8) | None | | [rule.mdc] | 5/8 | 60% (3/5) | [pattern] violated in S002, S005, S007 | **Epic-Level Rule Checks**: - Consistency across stories: [✅/⚠️/❌] - Integration patterns: [✅/⚠️/❌] - Cross-story architectural compliance: [✅/⚠️/❌]
- •If no .cursor/rules/ directory: Note "No project-specific rules found"
- •If patterns of violations across stories: Flag for epic-level retrospective

4.5. Visual Design Validation (if epic has UI components):

Reference: .cursor/skills/visual-testing/SKILL.md

Load Epic-Level Visual Artifacts:

•[EPIC_DIR]/wireframes.md → Layout expectations
•[EPIC_DIR]/user-journey.md → Touchpoint visual requirements
•specs/projects/[PROJECT_ID]/design-system.md → Tokens, patterns
•specs/projects/[PROJECT_ID]/ux-strategy.md → Voice/tone, accessibility

Aggregate Story Visual Results:

•Collect screenshots from all stories/[STORY_ID]/screenshots/
•Check each story's validation-report.md for visual validation section
•Aggregate design token compliance percentages
•Aggregate accessibility audit results

Wireframe Adherence Check:

•Compare implemented screens against wireframes.md layouts
•Check grid alignment, spacing, hierarchy
•Verify responsive breakpoints match wireframe variants
•Note deviations with justification

User Journey Visual Completion:

•
For each touchpoint in user-journey.md:
- •Verify screen exists and is implemented
- •Check visual treatment matches emotional goals
- •Verify transitions/animations between touchpoints
•Flag missing or incomplete touchpoints

Cross-Story Visual Consistency:

•Same components look identical across stories
•Consistent spacing, typography, colors
•No one-off styling deviations
•All use design system tokens (no hardcoded values)

Design System Adoption:

•Calculate % of components using design-system.md patterns
•Flag custom components that should use existing patterns
•Note design system gaps (patterns needed but not defined)

Voice/Tone Consistency:

•Aggregate voice/tone compliance from story validations
•Check consistency across epic (same voice everywhere)
•Flag mixed messaging or tonal inconsistencies

•
Execute validation suites:

Automated Testing
- •Run all story unit tests
- •Run epic integration tests
- •Run cross-epic tests
- •Performance benchmarks
- •Security scans
Manual Validation
- •User acceptance scenarios
- •Epic-level user journeys
- •Edge case verification
- •Stakeholder demos
•
Generate validation report:

CRITICAL: Load and follow the template exactly:
code
```
.speck/templates/epic/epic-validation-report-template.md
```
Write output to: [EPIC_DIR]/epic-validation-report.md
•
Generate punch list:

CRITICAL: Load and follow the template exactly:
code
```
.speck/templates/epic/epic-punch-list-template.md
```
Write output to: [EPIC_DIR]/epic-punch-list.md
•
Save validation artifacts:
- •Report: [EPIC_DIR]/epic-validation-report.md
- •Punch list: [EPIC_DIR]/epic-punch-list.md
•
Update epic status:
- •Update epic.md status field
- •Note completion date
- •Link validation report
•
Output summary:

code

✅ Epic Validation Complete!

Epic: [Name]
Status: [COMPLETE/PARTIAL/FAILED]

Results:
- Stories Complete: [X of Y]
- Tests Passing: [A]%
- Performance: [Met/Not Met]
- Quality Gates: [Passed/Failed]

Outstanding Issues: [Count]
- Critical: [X]
- Important: [Y]
- Minor: [Z]

[If APPROVED]:
Epic ready for production!
Next: Integration with other epics

[If CONDITIONAL]:
Fix required items, then re-validate

Reports:
- epic-validation-report.md
- epic-punch-list.md

Note: Epic validation ensures the feature set works as a cohesive whole.