planlisted

Use this skill when the user wants a concrete implementation plan before consultation or coding. Resolve helpers before running them: set `FORGEFLOW_HELPER_DIR` to `scripts/forgeflow` when that directory exists, otherwise to `${CODEX_HOME:-$HOME/.codex}/forgeflow/scripts/forgeflow`. If neither exists, report a missing Codex runtime installation. Before other work, run: ```bash "$FORGEFLOW_HELPER_DIR/ensure-forgeflow-state.sh" ``` Workflow: 1. Build compact local memory context with `scripts/forgeflow/build-memory-context.js` when available, then load current discussion and research artifacts from `.forgeflow/<project-name>/` when needed. 2. Gather focused local context such as `CONTEXT.md`. 3. Spawn `compass_planner` and `atlas_early` in parallel. 4. Synthesize the result into a unified implementation plan. 5. Save it to `.forgeflow/<project-name>/current-plan.md` when appropriate. Output should include: - phases and deliverables - in-scope / out-of-scope / deferred - dependencies and coordination risks - accessibility checklist - success criteria