On-demand research bundle for the Aria Creative Suite. Use when any agent needs competitor analysis, trend research, or content opportunity scanning to inform visual/video production.
This workflow produces an actionable research bundle — competitor analysis, trend spotting, and content opportunity identification — that feeds directly into visual and video production. It is a service workflow invoked on-demand by any Aria Creative Suite agent (Strategist, Designer, Video Producer, or Aria herself) when research context is needed to inform creative decisions.
The output is not academic research. Every finding translates into a specific production recommendation: a design brief the Designer can act on, a video format the Video Producer can storyboard, a content angle with hook and platform guidance. If a finding does not lead to a "make this" recommendation, it is context, not output.
Args: Accepts --headless or -H for autonomous execution. Supports scoped research via --scope competitor, --scope trend, --scope content, or --scope all (default).
Load available config from {project-root}/.pawbytes/config/config.yaml and {project-root}/.pawbytes/config/config.user.yaml (root level and cra section). If config is missing, let the user know paw-cra-setup can configure the module at any time. Resolve:
{user_name} (null) — address the user by name{communication_language} (system) — use for all communications{document_output_language} (system) — use for generated document content{default_brand} (null) — default brand to research if none specifiedLoad shared agency memory from {project-root}/.pawbytes/creative-suites/index.md. If a brand context is active or specified, load {project-root}/.pawbytes/creative-suites/brands/{brand-name}/guidelines.md and any existing research in {project-root}/.pawbytes/creative-suites/brands/{brand-name}/research/.
If --headless, complete the full pipeline without interaction using the active brand and scope from args. If interactive, greet and confirm research parameters before proceeding.
Parse the research request:
| Parameter | Source | Fallback |
|---|---|---|
| Brand | Explicit request or --brand arg | {default_brand} or active brand from index.md |
| Scope | --scope arg or explicit request | all (competitor + trend + content) |
| Focus areas | Explicit questions or topics | Derive from brand guidelines (industry, audience, competitors) |
| Target platforms | Explicit or from brand guidelines | Instagram, TikTok, YouTube, LinkedIn |
If interactive: confirm parameters and ask if there are specific questions or competitors to prioritize. If headless: proceed with available context.
Load from {project-root}/.pawbytes/creative-suites/brands/{brand-name}/:
guidelines.md — brand identity, voice, visual style, industry, audienceresearch/ — any prior research reports (avoid redundant work, build on existing findings)If no brand exists at the expected path, abort with a clear message suggesting brand onboarding through Aria.
Load ./references/competitor-scan.md for detailed research guidance.
Use Exa MCP tools to analyze 3-5 competitors across:
Production lens: For every competitor insight, note what it means for Designer and Video Producer. "Competitor X uses bold typography overlays on Reels" is more useful than "Competitor X has strong video presence."
Load ./references/trend-analysis.md for detailed research guidance.
Search for trends relevant to the brand's industry and audience:
Classify each trend: Fad (<3 months), Trend (6-18 months), Movement (2+ years), Declining (avoid).
Cross-reference competitor gaps with trending topics to find exploitable angles:
Produce an angle shortlist — 5-10 specific content angles, each with:
This is the most critical output section. Translate every research finding into briefs that Designer and Video Producer can act on directly.
Load ./references/production-recommendations.md for recommendation templates.
For each recommended angle, produce:
Design briefs (for Designer):
Video briefs (for Video Producer):
Platform-specific notes:
Produce research-report.md following the structure in ./references/report-template.md.
The report consolidates all findings into a scannable document with:
Write the report to {project-root}/.pawbytes/creative-suites/brands/{brand-name}/research/research-report.md with frontmatter:
---