Flow
Plan first, work second
Most failures come from weak planning or drifting from the plan. Flow fixes both with structured research upfront, explicit plan reuse, and plan re-read between tasks.
Two commands. Five specialized agents. One disciplined workflow that actually ships.
NOTE — This isn't strictly an app, but it belongs here given my focus on AI-native software development. Flow represents how I think about structured agent workflows.
THE PROBLEM
Most agent failures aren't about model capability. They're about process:
- ×Starting to code before understanding the codebase
- ×Reinventing patterns that already exist in the repo
- ×Forgetting the original plan mid-implementation
- ×Missing edge cases that were obvious in hindsight
Flow enforces the discipline that makes agents reliable.
TWO COMMANDS
/flow:planProduces plans/<slug>.md with references and acceptance checks.
- 01Run three research agents in parallel
- 02Run flow gap check
- 03Write plan with references + acceptance checks
- 04Offer next step (open, work, create issue)
/flow:workTakes a plan file and executes it with discipline.
- 01Confirm plan + clarify blockers
- 02Setup branch or worktree
- 03Turn plan into TodoWrite tasks
- 04Execute task loop with plan re-read
- 05Test + optional audit
- 06Ship
SPECIALIZED AGENTS
repo-scoutSearches your codebase for reusable code, established patterns, and conventions to leverage.
practice-scoutResearches community best practices and proven approaches for your specific task.
docs-scoutFetches relevant official documentation for frameworks, libraries, and APIs involved.
flow-gap-analystIdentifies edge cases, missing user flows, and potential gaps in your specification.
quality-auditorOptional security and quality review to catch issues before they ship.
worktree-kitGit worktree management for isolated development without polluting your main branch.
INTEGRATION
If you use gmickel/claude-code-config, chain Flow with RepoPrompt review commands:
/flow:plan Add OAuth login for users then review the plan using /rp-plan-review/flow:work plans/add-oauth-login.md then review using /rp-impl-reviewRepoPrompt commands are powered by rp-cli—the same tool used throughout this site.
INSTALLATION
/plugin marketplace add https://github.com/gmickel/gmickel-claude-marketplace/plugin install flowclaude --plugin-dir ./plugins/flowClone the marketplace repo and point Claude Code at the plugin directory for development.
- ›Plan files live in
plans/ - ›Prefer reuse of centralized code
- ›Tests and linting are part of the plan
- ›Issue creation auto-detects GitHub/Linear/Beads
Developers who want Claude Code to ship reliably, not just generate code. If you've ever had an agent "finish" a task only to realize it forgot half the requirements—this is for you.
Flow doesn't make Claude smarter. It makes the workflow disciplined enough that capability translates to results.