Example Research

• Template — full worked example for a fictional “Rival Co”
• Field Rules — frontmatter fields, body section order, mention/findings format
• Writing via Bash Heredoc — required pattern for subagents to avoid permission prompts

Each enrichment subagent writes one markdown file per competitor to {OUTPUT_DIR}/{competitor-slug}.md, where {OUTPUT_DIR} is the per-run Desktop directory set up by the main agent in Step 0 (e.g., ~/Desktop/acme_competitors_2026-04-23/). The YAML frontmatter contains structured fields for report/matrix compilation. The body contains per-section research plus aggregated mentions and benchmarks.

Template

Field Rules

• YAML frontmatter: All structured fields go here. Extracted for matrix + CSV compilation.
• pricing_tiers: Pipe-separated (|) with tier name + short price. compile_report.mjs parses on | for the matrix view.
• key_features, integrations: Pipe-separated lists.
• strategic_diff: One-line summary (shown in overview table).
• Body sections: ## Product, ## Pricing, ## Features, ## Positioning, ## Comparison vs {user_company}, ## Mentions, ## Benchmarks, ## Research Findings, ## Battle Card (deep/deeper modes only; synthesized by the Battle lane after fact-check).
• Mentions format: - **[SourceType]** title | snippet (source: url, date) — SourceType is one of Benchmark, Comparison, News, Reddit, HN, LinkedIn, YouTube, Review, Podcast, X.
• Findings format: - **[confidence]** fact (source: url) — confidence is high, medium, or low.
• Filename: {OUTPUT_DIR}/{competitor-slug}.md where slug is lowercase, hyphenated.

Writing via Bash Heredoc

Subagents write these files using bash heredoc to avoid security prompts. Use the full literal {OUTPUT_DIR} path — no ~ or $HOME:

Use 'COMPETITOR_MD' (quoted) as the delimiter to prevent shell variable expansion.

IMPORTANT: Write ALL competitor files in a SINGLE Bash call using chained heredocs to minimize permission prompts.