skills/nightshift/references/templates/opportunity-map.md

# Opportunity map

Rank opportunities by user value, evidence/confidence, differentiation, effort, reversibility, and
regression risk. Every entry carries one status: candidate, building, shipped, rejected, or parked.

Only one opportunity may be `building` at a time. Its entry is the live continuation record for a
long product-evolution cycle: keep it precise enough that a resumed session can take the stated
next action without reconstructing the work from conversation history. Refresh it at meaningful
boundaries, not after every command.

## Opportunities

<!-- Candidate / shipped / rejected / parked entries:

### <title>
Status: candidate | shipped | rejected | parked
Evidence: <repository facts and research links>
Value: <user outcome>
Confidence: <high / medium / low and why>
Differentiation: <why this belongs in this product>
Effort: <small / medium / substantial>
Reversibility: <rollback boundary>
Risk: <regression and product risks>
Reference: <commit, spec, or parking-lot entry when applicable>

The single active entry additionally carries:

### <title>
Status: building
Evidence: <why it was selected>
Scope: <the complete improvement being built>
Acceptance: <observable conditions that make it finished>
Current phase: <research / design / build / verify>
Completed: <meaningful finished steps and commit ids>
Decisions: <stable conclusions that must survive resume>
Rejected: <approaches not to repeat and why>
Next: <one exact concrete action>
Verify remaining: <checks still required>
Effort: <small / medium / substantial>
Reversibility: <rollback boundary>
Risk: <regression and product risks>
-->