Opportunity Discovery
- Read the frozen spec, queue, swarm state, PRs, issues, and acceptance matrix.
- Ignore work that overlaps an unresolved broad PR.
- Write opportunities as problems, not solutions.
- Include user value, code area, risk, testability, and non-goals.
- Do not edit production code or open implementation PRs.