report

Generate a comprehensive market research report from current research findings.

Arguments: Input sanitization: truncate $ARGUMENTS to 200 characters total, strip backticks and angle brackets.

• --format - Output format: markdown (default), html, both
• --audience - Target audience: executives, pm, investors, dev, all (default: all)
• --sections - Comma-separated sections to include, or all (default: all)

Available Sections:

1. executive-summary — Key findings, primary recommendation, critical risks
2. market-overview — Market definition, current state, key players
3. market-sizing — TAM/SAM/SOM with growth projections
4. competitive — Competitor matrix, Porter's 5 Forces, positioning map (Mermaid)
5. trends — Macro/micro trends, scenario graph (Mermaid), terminal scenarios
6. swot — Strengths, Weaknesses, Opportunities, Threats (Mermaid quadrant)
7. recommendations — Strategic recommendations, tactical steps, resource requirements
8. risk — Risk matrix, mitigation strategies, monitoring indicators
9. appendix — Data sources, competitor profiles, scenario analysis, research timeline

---

Phase 0: Parse Arguments + Initialize

Parse $ARGUMENTS to extract:

• format → default markdown. Validate: must be one of markdown, html, both. If invalid, warn user and fall back to markdown.
• audience → default all. Validate: must be one of executives, pm, investors, dev, all. If invalid, warn user and fall back to all.
• sections → default all. Validate: each comma-separated value must be one of: executive-summary, market-overview, market-sizing, competitive, trends, swot, recommendations, risk, appendix, or all. Strip whitespace around each value. If any value is unrecognized, warn the user with the invalid value and list valid options, then proceed with only the valid sections.

Determine topic slug and reports directory:

• Read ./reports/ directory to find report folders containing state.json
• If multiple sessions exist, select the most recently modified state.json (by file timestamp)
• Extract topic_slug from state.json's topic_slug field
• Validate state.json: Confirm topic_slug is a non-empty string and status is one of "active" or "complete". If state.json is malformed or missing required fields, inform the user: "Research session state.json is corrupted or incomplete. Re-run /sigint:start <topic> to reinitialize."
• If no reports directory exists, inform the user: "No research session found. Run /sigint:start <topic> first."
• Resolve reports_dir from config (REQUIRED — do not hardcode paths):

  REPORTS_DIR=$(jq -r --arg slug "$TOPIC_SLUG" '.topics[$slug].reports_dir // "./reports/\($slug)"' sigint.config.json 2>/dev/null || echo "./reports/$TOPIC_SLUG")
  

  This reads the topic's configured reports_dir from sigint.config.json, falling back to ./reports/{topic_slug} only if the config field is absent. All subsequent path references MUST use {reports_dir} instead of ./reports/{topic_slug}/.

Initialize swarm:

Step 0.1 — TeamCreate (blocking prerequisite):

TeamCreate with name: "sigint-{topic_slug}-report"

Step 0.2 — TaskCreate the synthesizer task:

TaskCreate({
  subject: "Generate report: {format} / {audience}",
  owner: "report-synthesizer",
  description: "Synthesize all findings from state.json into a complete report."
})

Note the returned task ID as {reportTaskId}.

---