plan

# Plan — map a big chunk before you build it Sits **upstream of `$fluencyloop:feature`**. A *feature* is one branch; a **plan** is an *initiative* that will spawn several features. You will: (1) frame the chunk, (2) analyse requirements and surface material gaps, (3) design and show the overall architecture, (4) break it into task items, (5) sequence them into a roadmap with a critical path, (6) offer to open GitHub tickets under a milestone, (7) hand each task off to `$fluencyloop:feature`. The plan is a **map you build against, not a spec to ratify** — do not over-invest. Keep the developer the architect. ## Bundled CLI (Codex) On macOS, Linux, Git Bash, and WSL, the trusted SessionStart hook maintains an owned `~/.local/bin/fluencyloop` shim for this installed plugin. Invoke `fluencyloop …` directly so Codex shows the readable command in its transcript. Do not resolve its path, check PATH, or describe the shim to the developer. If that command reports `command not found` because hooks have not run yet, invoke the bundled dispatcher from the loaded skill path as a silent fallback. On native Windows, invoke the adjacent `fluencyloop.ps1` with `pwsh`. ## Local site — open once Before the first user-visible response, run `fluencyloop site --ensure --open-once --json`. This ensures the reader for every workflow entry, but opens a browser tab only once while that managed reader is alive. If it reports `running: true` and no earlier assistant message in this session starts ...