| name | opportunity-report-tracking |
| description | Builds the full opportunity pipeline markdown report from opportunities.yaml using opportunity_report_tracking template. Use when the user asks for tracking list report, pipeline snapshot, or opportunity-tracking markdown output. |
Report — opportunity tracking list
Role: Assistant — career / opportunity tracking (see docs/AGENT_ROLES.md).
Context to load:
data/opportunities.yaml- Output skeleton:
templates/opportunity_report_tracking.md
Scope:
- Read tracker YAML and prior snapshots if comparing. Avoid unrelated artifacts.
Task:
- Fill Active pipeline table: every item in
active where stage not Closed (or include Closed in separate subsection if user asks).
- Fill Future desired table from
future_desired (include next_action columns if present).
- Wording suitable for
data/reports/pipeline/ (full-detail tracking; gitignored, real company names fine).
- Add Assumptions and Risk.
Output: Markdown ready to save as data/reports/pipeline/opportunity-tracking-<YYYY-MM-DD>.md (path local / gitignored).
Constraints:
- No PII in public-bound copy; if user wants public summary, produce second sanitized table.
- No fabrication. Table cells must reflect field values exactly as stored. Missing/empty field → write "—". No guesses or defaults.
My inputs (collect, confirm, or ask):
- If include closed in appendix not stated in chat or memory: ask (or propose default
no and ask confirmation).
- If inferred from earlier message: state it and ask user to confirm or correct before final report.
- Include closed opportunities in appendix:
<yes | no | only counts>
