-
Notifications
You must be signed in to change notification settings - Fork 0
Roadmap
Cory Ebert edited this page Sep 11, 2026
·
5 revisions
ForgeFlow is a software delivery workshop for Claude Code and Codex. This page records product direction; it does not promise dates or imply that deferred work is implemented.
The core delivery phases, specialist agents, local project memory, and evidence-based review are joined by the workshop dashboard and Ember. The dashboard balances reported activity, project readiness, context budget, and recorded review outcomes. Supported workflow entrypoints open it once per eligible desktop session. The visual guide and Quick Start cover first use.
- Keep install, repair, and release paths trustworthy.
- Keep review, audit, and context-prep surfaces evidence-backed.
- Reduce onboarding friction for Claude Code and Codex without broadening automation risk.
- Keep public docs and runtime behavior aligned.
- Keep
/update-forgeflow,/forgeflow-version,/forgeflow-health,/forgeflow-update-verify, and runtime-drift checks aligned. - Preserve explicit manual boundaries for host settings and rollback.
- Verify shared helper behavior in both runtimes while documenting host-specific commands, configuration, and model availability.
- Keep review routing explainable and deterministic.
- Improve context-pack quality, budget guidance, and review-wave follow-through.
- Use Verifier verification and release-readiness warnings to keep high-risk claims grounded.
- Keep first-run, pilot, and support surfaces compact enough for real users to follow without internal maintainer context.
- Prefer public-safe summaries and aggregate evidence over raw local state.
- Fix repeated friction before adding new workflow surface area.
- Keep README, wiki, hosted docs, changelog pointers, and release metadata in sync.
- Avoid count-based or host-specific claims that drift easily.
- Prefer current user paths over internal phase history.
The following stay out of scope unless new evidence justifies them:
- hosted telemetry or remote analytics
- automatic GitHub or PR mutation
- CI auto-push or auto-merge behavior
- broad LLM-generated patching
- multi-fix autobatching across unrelated findings
- full runtime call-graph claims
- Prefer fixes backed by smoke failures, release-readiness failures, pilot evidence, or repeated user confusion.
- Prefer smaller changes that improve install confidence, review correctness, or docs accuracy.
- Defer speculative helpers when an existing command or document already covers the need.