Repeatable agentic engineering

Flow-Next

Raise the quality bar for AI-assisted software work.

Flow-Next is the workflow layer for agentic engineering: durable specs, context-fit planning, re-anchored worker agents, adversarial review loops, docs drift prevention, and receipts for every serious handoff. Ralph is available when you want autonomous execution, but the core product is repeatable quality across any platform.

Spec-driven Intent survives the chat. Context-fit plan Right-sized task slices. Re-anchored work Fresh context per task. Adversarial gates Fix until SHIP. Multi-harness One workflow everywhere.
$ /flow-next:plan fn-52 && /flow-next:work fn-52
specs/fn-52-quality-gates.md Spec Status Review gated Tasks 4 / 4 Receipts 2 Criteria 6

Task Graph

fn-52-quality-gates Spec
write-spec Task
context-fit-plan Task
worker-reanchor Task
review-loop Task
make-pr-cognitive-aid Handover
Fit 100%

Command Palette

⊙ Plan Spec... /flow-next:plan fn-52 ⌘ Work Ready Task /flow-next:work fn-52 ▣ Impl Review /flow-next:impl-review ↯ Ralph Loop Ready scripts/ralph/ralph.sh

Recent Runs

SHIP fn-52-quality-gates

SHIP docs-site-sync

Terminal / Receipts

$ /flow-next:plan fn-52
✓ sized 4 tasks for focused context
✓ dependencies recorded

$ /flow-next:work fn-52
> Re-anchoring spec + task
+ Running worker subagent
+ Updating flowctl state
+ Evidence recorded

$ /flow-next:impl-review fn-52
✓ verdict: SHIP
Receipt: .flow/review-receipts/fn-52.json
$

Receipts

Receipt
.flow/review-receipts/fn-52.json
Verdict
SHIP
Backend
codex:gpt-5.5:high
Scope
introduced findings only
Open Receipt (JSON) →
Claude CodeOpenAI CodexFactory DroidRepoPromptGitHub CopilotOpenCode community

Spec-driven control

Turn vague requests into durable specs that keep product intent, technical constraints, and review criteria stable.

  • Capture rough intent
  • Clarify business + technical gaps
  • Prevent scope drift through delivery
spec: fn-52-quality-gates
source: .flow/specs/fn-52-*.md

R1: Every task maps to acceptance criteria.
R2: Review receipts gate handoff.
R3: PR body tells reviewers where to look.

Context-fit planning

Automatically split specs into dependency-ordered task slices sized for focused agent context windows.

  • Expose blockers and parallelism
  • Keep each task bounded
  • Avoid one giant prompt becoming the plan
/flow-next:plan fn-52

ready:
  fn-52.1 wire config schema
  fn-52.2 add review receipt gate
blocked:
  fn-52.3 docs sync after API lands

Re-anchored workers

Run each task in fresh execution context, rereading the spec, task, git state, and relevant repo code before editing.

  • Fresh worker per ready slice
  • Subagents for focused investigation
  • Evidence recorded as work moves
/flow-next:work fn-52

> read .flow/specs/fn-52.md
> read ready task + git status
> inspect relevant code
> edit, test, record evidence

Adversarial quality gates

Raise the quality bar with plan review, implementation review, completion review, docs drift checks, and receipts.

  • Cross-model challenge loop
  • Fix until introduced issues are gone
  • Reviewer-ready proof, not promises
/flow-next:plan-review fn-52
/flow-next:impl-review fn-52
/flow-next:spec-completion-review fn-52

verdict: NEEDS_WORK -> fix -> review -> SHIP

Multi-harness by design

Standardize agent workflow across Claude Code, OpenAI Codex, Factory Droid, and review backends.

  • One repo-local state model
  • Native skills per harness
  • CLI only as safe plumbing
Claude Code   /flow-next:work fn-52
OpenAI Codex  /flow-next:work fn-52
Factory Droid /flow-next:work fn-52

RepoPrompt reviews when available

01 / Signal

What people say.

Shared by practitioners, not marketing.
“Flow-next is simply the best coding flow, not even close, and still a side project.”
Tiago Freitas · @tiagoefreitas
@Lat3ntG3nius
“Cross-model review is genius. Different models make different mistakes, so using them as mutual reviewers creates a safety net single-model workflows can’t match.”
@clairernovotny
“I’ve found it generating production-quality code. Far, far better than any of the other tools I’ve tried.”
@BaranGuneysel
“As a designer, flow-next finally lets me ship features with confidence. The review loop catches what I miss.”
@dailyreader
“The re-anchoring is the quiet superpower. After a long session the agent still knows exactly what it’s building.”
@mfeighery
“Ralph mode at night, PRs in the morning. Zero drama. The receipts mean I trust what landed.”
@ben
“A force multiplier. Plan once, then watch a team of scouts and reviewers do their jobs.”
☆ New to Flow-Next? Get your first spec planned, worked, reviewed, and handed off.