opportunity-report-next-steps-rollup

name: opportunity-report-next-steps-rollup description: >- Builds sorted rollup of next actions across all active opportunities using opportunity_report_next_steps_rollup template. Use when user asks for combined backlog, rollup next steps, or sorted pipeline todos by date.

Report — next steps rollup (all active)

Role: Assistant — career / opportunity tracking (see docs/AGENT_ROLES.md).

Context to load:

• data/opportunities.yaml
• Output skeleton: templates/opportunity_report_next_steps_rollup.md

Scope:

• Load only opportunities YAML and output template.
• Skip per-opportunity reports unless user asks for evidence behind a row.

Task:

1. Collect next_action for every item in active with stage not Closed (unless user wants closed included).
2. Optionally include future_desired entries with next_action set.
3. Sort rows: primary next_action_date ascending (empty dates last); secondary priority P0 → P1 → P2.
4. Build Combined backlog table; each row must include opportunity_id for traceability.
5. Assumptions / Risk.

Output: Markdown for data/reports/pipeline/opportunity-next-steps-rollup-<YYYY-MM-DD>.md or paste-only.

Constraints:

• All reports stay in data/ (gitignored), so real company/person names fine.
• No fabrication. Populate rows only from next_action and next_action_date as recorded. Don't invent or extrapolate absent actions.
• Missing data → state explicitly. If next_action_date absent, sort row last, mark date cell "Not set". No date guessing.

My inputs (collect, confirm, or ask):

• If whether to include future_desired rows with next_action not stated in chat or memory: ask (or propose default and ask confirmation).
• If inferred from earlier message: state it and ask user to confirm or correct before final report.
• Include future_desired with next_action: <yes | no>