review-and-planlisted

# Review And Plan Discover opportunities first; implementation still goes through `../optim-plans/SKILL.md`. ## Required Flow 1. Inspect the target Git repo before asking product questions. Read the app shape, docs, tests, dependency files, entry points, recent change notes, and any obvious UX or safety-critical paths. 2. Search GitHub open-source projects for feature inspiration before ranking opportunities. Use `gh search repos` / `gh search code` when available; if `gh` is unavailable or unauthenticated, use the GitHub REST/search API or web search constrained to GitHub repository pages. Record sources either way. 3. Produce a ranked opportunity list grouped exactly by: - Documentation - Efficiency/cost - Feature completeness - UX - Safety/recoverability 4. For each opportunity, include stable fields: - `id`: stable ID such as `OPP-001` - `category`: one group above - `rank`: rank within category or overall list - `title` - `repo_evidence`: local file/behavior evidence - `repository_url`: GitHub source repository URL - `supported_claim`: concise claim supported by that source - `source_tool`: `gh`, `github-api`, or `web` 5. Ask one case-by-case opportunity question at a time before any accepted opportunity enters implementation scope. Use only planning-stage generic controller-backed choice questions. 6. Each opportunity question must recommend one disposition first: `accept`, `defer`, or `reject`, with evidence. Offer the other di