forward-planlisted

# forward-plan Turn the native ready set, outcome ranking, and the repo ROADMAP into one dependency-filed plan artifact. Brigade stays invoke-only. This skill is the allowlist-bound agent recipe. It is a registry skill, never a CLI subcommand - the planning sequence stays inspectable. ## When this applies - You need a forward plan that joins what is ready now with roadmap direction. - An operator schedules a headless harness against this skill for planning. - The workspace has (or can create) `.brigade/work/` and may or may not have GraphTrail installed. ## Allowlist Work only through this allowlist: - `brigade work ready --json` (add `--explain` when blocked items matter) - `brigade outcome rank --json` (optional `--by-capability` / `--recency`) - Read of repo-root `ROADMAP.md` under the parse contract below - `brigade code …` for GraphTrail footprint / impact / doctor checks - `brigade work task edge …` / `brigade work task add --graph …` only after an operator confirms derived edges (never auto-apply. See Safety gates) - `brigade work plans` to list existing plan artifacts - Write only under `.brigade/work/plans/` (the plan JSON + plan.md pair) - Read/Grep of on-disk task ledgers, existing plans, and code paths named by GraphTrail output Bash is scoped to those `brigade …` commands only. Do not expand into arbitrary shell, remote APIs, or writes outside `.brigade/work/plans/`. Stay inside the target workspace. Do not follow `..` or symlinks out of it. ## Safe