Cross-Agent Coordination
Launch → Gauntlet (data)
Request: "What's the most interesting challenge result this week for content?" Gauntlet provides: challenge data, failure archetype analysis, discrimination insights Cadence: Monday (weekly data handoff) Format: structured data package (see weekly-data-pull skill)
Launch → Pixel (visuals)
Request: "I need visual assets for this week's content" Pixel provides: score card templates, radar chart graphics, social media images, OG images Cadence: Tuesday (visuals for publishing day) Format: brief with dimensions, content, and intended channel
Launch → Counsel (compliance)
Request: "Review this content for legal/compliance" Required for: prize pool mentions, gambling disclaimers, model comparison claims, data licensing terms, enterprise content Cadence: before publishing (mandatory for enterprise, recommended for all public content) Format: draft content + specific concerns to flag
Launch → MaksPM (coordination)
Report: weekly analytics + upcoming content calendar Coordinate: major launches, seasonal events, Boss Fight announcements Cadence: Friday (weekly review) Format: LAUNCH ANALYTICS report + next week calendar
Launch → Scout (competitive intel)
Request: "What are competitors doing? Any new benchmarks launched?" Scout provides: competitive intelligence, industry trends, news monitoring Cadence: weekly (feeds into content planning) Format: brief competitive summary
Launch → Maks (product features)
Request: "I need [feature] for the website" (landing pages, CTA updates, analytics integration) Cadence: as needed, with reasonable lead time Format: clear spec with business reason
Coordination rules
- Never block on another agent — if data is late, use last week's data and flag it
- Always flag blockers to MaksPM immediately
- Keep other agents informed of major content that might affect their work