flow-next-epic-review

Coordinate cross-backend epic reviews and enforce SHIP/NEEDS_WORK verdicts.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/tiendung/flow-next --skill flow-next-epic-review-tiendung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next-epic-review
Source: https://github.com/tiendung/flow-next/tree/main/skills/flow-next-epic-review
Command: npx skills add https://github.com/tiendung/flow-next --skill flow-next-epic-review-tiendung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Epic completion review coordinates and validates that the combined implementation of all epic tasks satisfies the spec requirements, ensuring cross-task alignment and preventing drift from the intended spec.

Core Features & Use Cases

  • Coordinates multi-backend review workflows (RepoPrompt and Codex) to enforce spec compliance across epics.
  • Orchestrates a structured fix loop with mandatory commits and re-reviews until a SHIP verdict is reached.
  • Handles receipt writing and proper messaging for auditability and traceability.

Quick Start

Start an epic completion review to verify that all epic tasks align with the spec across backends and produce a final SHIP/NEEDS_WORK verdict.

Frequently Asked Questions about flow-next-epic-review

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

FAQPage Schema
How do I verify that all epic tasks collectively satisfy the epic spec requirements?

Epic spec completion review identifies and verifies that combined task implementations satisfy epic spec requirements, coordinating cross-backend review workflows to enforce cross-task alignment and prevent spec drift.

Can I use either RepoPrompt or Codex for automated spec compliance review?

Yes, epic review coordinates multi-backend workflows supporting both RepoPrompt and Codex. It handles backend detection, context gathering, and selection augmentation to enforce spec compliance across epics.

How does the fix loop work during an epic completion review?

The fix loop orchestrates mandatory commits and re-reviews until a SHIP verdict is reached. It enforces receipt handling and strict verdict interpretation to produce a final SHIP or NEEDS_WORK outcome.

What is the difference between a SHIP and NEEDS_WORK verdict in spec compliance automation?

A SHIP verdict indicates all epic tasks satisfy the spec requirements, while NEEDS_WORK triggers the structured fix loop with mandatory commits for re-review until spec compliance is achieved.

How do I ensure auditability and traceability when reviewing epic tasks across backends?

The epic review workflow handles receipt writing and proper messaging during the cross-backend review process, ensuring auditability and traceability for the final SHIP or NEEDS_WORK outcome.