reference-before-planlisted

# Reference Before Plan Use this skill when external references must shape the plan before implementation. ## Setup 1. Read `../_shared/references/prime-planning-workflow.md`, `../_shared/references/state-and-config.md`, and `../_shared/references/plan-artifact-template.md`. 2. Initialize state with `python3 scripts/optim_plans.py init --repo <target-repo> --topic <topic> --plan-level reference-before-plan --request-text <original-request>`. 3. Use `.git/optim-plans` for controller state and `docs/optim-plans/YYYY-MM-DD-topic/` for public artifacts. ## Required Reference Flow 1. Inspect the target Git repo read-only before external research so search terms match the actual codebase. 2. Search proactively for related projects, articles, papers, docs, and prior art. 3. Download or clone at least 3 credible references before writing `PLAN_v1.md`. Store large downloads outside the target repo by default under `~/.cache/optim-plans/refs/<repo-slug>/<topic>/`. 4. Record source metadata with `record-reference`: title, URL, kind, retrieval method, access date, local path, coverage, and evidence gaps. 5. For every reference, produce a structured analysis artifact and record it with `record-reference-analysis`. If a richer parser is unavailable, do a manual structured read and record any waiver with `record-reference-waiver`. 6. For every reference after analysis, ask at least 3 ref-specific adoption questions before using its ideas in `PLAN_v1.md`. Each question must be based on