ci

Show all available /ci: commands with their options, arguments, and usage examples. Covers built-in and any custom commands in the commands/ directory.

Import an existing skill file (extractor, synthesizer, or command) into the competitive analysis pipeline. Reads the file or pasted content, detects what it is, validates it against the pipeline contract, adapts what doesn't conform, places it in the right directory, and registers it in the right index.

Run market synthesis across all competitor profiles — positioning map, JTBD gaps, whitespace, differentiation opportunities, and strategic implications. Run monthly or before a strategy review.

Scaffold and register a new extractor, synthesizer, or command for the competitive analysis pipeline. Guides you through what it needs, generates the file from the right template, and registers it so the orchestrator picks it up automatically.

Re-synthesize one competitor's profile from their most recent snapshot, without re-running extraction. Use after manually editing a snapshot, after adding a new Stage 1 synthesizer, or when you want a fresh profile read without a full pipeline run.

Publish a saved brief to configured distribution channels (Slack, email, Notion). Defaults to the latest brief. Use --brief <date> for a specific brief or --all to publish all unpublished briefs. Use --yes to skip all prompts (for automated/ci:run use). Prompts for channel selection and confirmation before sending.

Run the competitive analysis pipeline — extracts signals from due competitors, detects deltas, runs synthesis, and delivers a brief. The main weekly driver of the pipeline.

Configure scheduled runs for any /ci: command. Defaults to Desktop scheduled tasks (persistent, no expiry). Falls back to session-bound CronCreate if Desktop is unavailable. Run without arguments to set up interactively.

Interactive first-run setup for the competitive analysis plugin. Creates a product context file, seeds {workspace_root}/competitors.yaml, and configures the pipeline. Run this before your first /ci:run.

Show the current state of the competitive analysis pipeline — extractors, synthesizers, schedule, distribution, and workspace health. A quick dashboard before running or after setup.

Analyzers apply an analytical framework to a competitor's snapshot and write a named `## Analysis — [Framework]` section to the profile. Multiple analyzers can be active simultaneously — each owns its own section and runs independently.

Applies SWOT analysis to a competitor's snapshot from our perspective. Writes

Each extractor owns one section of the run snapshot. The orchestrator spawns all applicable extractors in parallel for each competitor, and each extractor writes its section directly to the new snapshot file.

Fetches a competitor's product changelog or release notes, structures recent releases, identifies investment themes by release volume, and checks factual alignment between what they claim to be building (## Positioning) and what they actually shipped.

Extracts how a competitor positions themselves — their core message, target audience, claimed differentiators, and tone — from their homepage.

Extracts a competitor's pricing model, plan structure, price points, and feature gating — from their pricing page and any public pricing signals.

Orchestrator entry point for the competitive analysis pipeline. Reads the competitor registry, determines what's due, runs extractors in parallel, runs delta detection and synthesis, and delivers the brief.

Market synthesizers read **all** competitor profiles and produce market-level analysis documents. They are not run automatically by `/ci:run` — use `/ci:market` to run on demand, or `/ci:run --with-market` to run after a full pipeline cycle.

Cross-competitor market analysis. Combines competitive positioning map, JTBD gap analysis, whitespace/value curve, differentiation opportunities, and strategic implications into a single actionable document.