skills.rest
raydocs
raydocsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

flow-next-plan-review

Automate Flow epic plan reviews across RepoPrompt and Codex backends.

Updated Jan 15, 2026
Search Tags:#codex#review#epic#plan-review#repo-prompt#flowctl#flow-next
One-click install
npx skills add https://github.com/raydocs/inktale --skill flow-next-plan-review-raydocs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-next-plan-review
Source: https://github.com/raydocs/inktale/tree/main/plugins/flow-next/skills/flow-next-plan-review
Command: npx skills add https://github.com/raydocs/inktale --skill flow-next-plan-review-raydocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates expert-level plan reviews of Flow epic plans across RepoPrompt and Codex backends, ensuring unbiased, centralized critique and final verdicts.

Core Features & Use Cases

  • Backend-agnostic plan review: seamlessly uses RepoPrompt or Codex to perform structured plan reviews.
  • Session continuity: supports receipts and persistent sessions to track verdicts across re-reviews.
  • Phase-driven workflow: guides from plan reading, augmentation, to final verdict and status updates for epics.
  • Anti-pattern protection: enforces best practices to avoid re-review loops and misconfigurations.

Quick Start

Trigger a Carmack-level plan review for Flow epic specs using RP or Codex backends and obtain a final verdict.

Frequently Asked Questions about flow-next-plan-review

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

FAQPage Schema
How do I automate plan reviews for Flow epic specs?▼

Automate Flow epic plan reviews by triggering a phase-driven workflow that coordinates RepoPrompt and Codex backends, producing a structured final verdict and updating epic status.

Can I use Codex and RepoPrompt interchangeably for Flow epic plan reviews?▼

Yes, the plan review workflow is backend-agnostic, seamlessly detecting and using either RepoPrompt or Codex to perform structured critiques of your Flow epic plans.

How do I track verdicts across iterative plan re-reviews?▼

Track iterative verdicts using session receipts and persistent sessions, which maintain continuity across re-reviews until the epic plan reaches a final SHIP verdict.

Why do my Flow epics keep failing plan reviews and entering re-review loops?▼

Re-review loops are prevented by anti-pattern protection mechanisms that enforce best practices, strict verdict handling, and status updates to keep epics aligned with organizational standards.

What is the best way to enforce strict verdict handling for epic status updates?▼

Enforce strict verdict handling by running an automated plan-review workflow that coordinates backend critiques and directly updates Flow epic statuses based on the definitive final verdict.

Do I need flowctl wrappers to run Codex plan reviews?▼

Yes, flowctl wrappers are required to coordinate the Codex and RepoPrompt backends, handling backend detection, session receipts, and the iterative fix workflow during the plan review.

Related Skills

Explore More Software Engineering Skills→
gmickelgmickel
674

flow-next-epic-review

Orchestrate epic completion reviews against spec requirements using RepoPrompt or Codex backends.

Community
Advanced
ramontramontiniramontramontini

pull

Execute downstream stories from ready_to_pull to done with enforced gates.

Community
Advanced
raydocsraydocs

flow-next-impl-review

Automate implementation reviews of code changes with RepoPrompt or Codex backends.

Community
Advanced
Nairon-AINairon-AI
7

flux-plan-review

Coordinates RepoPrompt and Codex backends to review epic and task specs.flows.

Official
Advanced