← ClaudeAtlas

forgeflow-consultlisted

Run the Forgeflow consultation workflow to produce an implementation brief before coding.
BrandedTamarasu-glitch/ForgeFlow · ★ 1 · Code & Development · score 74
Install: claude install-skill BrandedTamarasu-glitch/ForgeFlow
Use this skill when the user wants the Forgeflow team to design the approach before implementation. Resolve every `scripts/forgeflow/...` helper from the current checkout first, then from `${CODEX_HOME:-$HOME/.codex}/forgeflow/scripts/forgeflow`. A missing helper means the Codex runtime installation needs repair; it does not mean the workflow is unsupported in Codex. Workflow: 1. Build compact local memory context with `scripts/forgeflow/build-memory-context.js` when available. 2. Build first-pass file ownership packets with `scripts/forgeflow/build-scope-manifest.js` when available. 3. Render `scripts/forgeflow/render-lean-decision.js --task "<request>"` when available and carry the compact lean decision into the implementation brief. 4. Run `scripts/forgeflow/check-context-budget.js --root .forgeflow --warn-only --json` when available and surface any warnings. 5. Gather focused context for the requested feature. 6. Prefer existing `CONTEXT.md` files, the lane scope packet, and the compact memory context before reading full `.forgeflow/current-*.md` artifacts. 7. Spawn in parallel: - `smith_consultant` - `warden_consultant` - `lumen_consultant` - `atlas_consultant` 8. Wait for their briefs. 9. Spawn `arbiter_consultant` with the task, gathered context, all four outputs, and the lean decision. 10. Save the result to `.forgeflow/<project-name>/current-brief.md` when appropriate. 11. Present the implementation brief with ownership, sequencing, interfaces, lean dec