ForgeFlowForgeFlow / Reference
ForgeFlow Wiki
A software delivery workshop for Claude Code and Codex.
ForgeFlow helps turn an idea into a scoped brief, working code, an evidence-backed review, and a shipping handoff. Specialist agents share useful project context, while the local dashboard shows reported activity, project readiness, and recorded review outcomes. Ember, the small robot at the forge, makes the current phase visible.
Start Here
- Visual user guide or 19-page PDF: an illustrated end-to-end walkthrough. On GitHub, download the HTML and open it in your browser; its images and controls work offline.
- Quick Start: install into your host, enable the dashboard, and run one small task in your own project.
- User Paths: choose a workflow for the outcome you need.
- Dashboard and Ember: understand current activity, readiness, evidence, and empty states.
Why ForgeFlow explains the approach. 4.6.3 release notes describe the packaged version. This wiki follows the current source. The visual guide identifies its own source edition.
New in 4.6.2
Local shipping previews now include staged and unstaged edits and nonignored new files alongside committed changes, with one entry per path. Task validation remains tied to current evidence.
Communication guidance from 4.6.1
The communication guide explains the updated writing rules: audience-appropriate detail, useful progress updates, concrete examples, and clear validation limits. Exact technical details and structured output remain intact.
Agent names introduced in 4.6.0
Agent Roles covers Builder, Guardian, Designer, Coordinator, Architect, Product Lead, and Verifier, with their phase responsibilities, host identifiers, and legacy-name mapping. CLI and dashboard messages carry explicit task context, and agent prompts include Orwell's six writing rules. History, context rebuild, cleanup and recovery fixes preserve compatibility across the rename.
For the first upgrade from legacy names, follow the source-checkout procedure. An old installed updater cannot apply the new preservation rules during its own update. Later releases use the newly installed helper.
A First Useful Task
Use Task Evidence and Recovery to connect acceptance criteria, current proof, and resumable phase history across Claude Code and Codex.
| Step | Claude Code | Codex | Result |
|---|---|---|---|
| Design | /consult |
$consult |
A brief with scope and validation |
| Build | /implement |
$implement |
Working changes and focused checks |
| Review | /review |
$forge-review |
Findings supported by evidence |
| Ship | /ship |
$ship |
A reviewable handoff and shipping preparation |
Add a concrete task after the command and run one phase at a time. Request commits, pushes, PRs, or deployment explicitly. Codex's built-in /review is separate from ForgeFlow's $forge-review; the larger Claude slash-command catalog does not imply a matching Codex skill for every entry.
For a small task, start with /quick or $quick. For an uncertain direction, start with discuss, research, and plan. Workflow Commands covers the full reference, and Agent Roles explains who does what.
Install And Operate
- Quick Start, Codex First Run, Template Installer
- Settings and Recovery, Migration Guide
- Dashboard and Ember, Local Data and Privacy
- Demos, Common Stack Examples
Workflows And Project Context
- User Paths, Workflow Commands, Agent Roles
- Review Routing, Research Divergence
- Context Intelligence, Context Budget Examples
- Optional Obsidian Vault Memory
- Implementation Notes, Project Learnings, User Profile Guidance
- Lean Quick Path, Lean Evidence, Lean Portability, Telemetry Readiness
Evaluate And Adopt
These are optional structured trials and evidence tools. You do not need a pilot report or benchmark to complete your first task.
- Try it: Package Release Onboarding, Branch Trial, Maintainer Pilot, Adoption Pack
- Decide as a team: Team Adoption Criteria, Team Privacy Boundaries, Support Triage, CI and Headless Deferrals
- Capture pilot evidence: Evidence Log, Public Summary, Support Rollup, Adoption Comparison, Next Action Decision
- Compare actual outcomes: Workflow Comparison, Evaluation Sharing, Evaluation Summary Collection, Public Examples
- Improve onboarding: First Run Friction, Friction to Fix, Field Validation
Record observed results. Missing optional evidence is not a failed installation, and an animation or live message is not proof that validation passed.
Maintain And Release
- Release Process, Release Gate, Clean Checkout Install Verification
- Maintaining the Wiki
- Roadmap
- Historical 4.3.0 release brief
The editable source for these pages lives in docs/wiki in the repository. The GitHub wiki is a separate published copy. Use the documentation entry for a compact navigation page, or the README for the project overview.