competitor-analysis
Competitor Analysis
Orchestrate 7 research agents to produce a comprehensive competitor teardown. Phase 1 runs 4 parallel research agents (Product, Marketing, UX, Technical). Phase 2 runs 3 sequential synthesis agents (MVP Spec, GTM Strategy, Competitive Landscape) that build on Phase 1 findings.
Workflow
1. Parse Input
Target: $ARGUMENTS
If the target above is non-empty, use it immediately — do NOT ask the user to confirm or re-provide it. Parse it as follows:
- URL (starts with
http): use as-is for WebFetch, extract company name from domain - Company name (no URL): construct likely URLs (
https://{name}.com,https://www.{name}.com)
If the target above is empty, ask the user what competitor to analyze and wait for their response.
Store the parsed values:
COMPANY_NAME: Human-readable name (e.g., "Linear")
More from wcygan/dotfiles
business-review
>
12ux-review
>
12zed-config
>
12zellij-guide
All-in-one Zellij terminal multiplexer guide. Use when the user asks about Zellij keybindings, configuration, layouts, plugins, sessions, CLI commands, or troubleshooting. Also use when helping with dotfiles config at ~/Development/dotfiles/config/zellij/.
11api-workshop
>
11tailwind
Tailwind CSS v4 expert. Auto-loads when working with Tailwind CSS, utility classes, responsive design, dark mode, shadcn/ui, CSS variables, @theme directive, custom variants, component styling, clsx, cn helper, color palette, spacing, typography utilities, hover/focus/group/peer states, container queries, and @apply patterns.
10