/org - Cross-Domain Orchestration

You've spent the past few articles building a website. The homepage is done, the inner pages are built, the content is polished. Now you're launching - and that's not just an engineering task anymore.

Engineering needs to deploy the site and run final QA. Marketing needs to write the launch announcement and line up the social posts. Docs needs a user guide so visitors can actually get value from day one. These three outputs need to be consistent with each other, and they need to land at the same time.

Here's how you run it:

/org "Launch the new portfolio site. Engineering: deploy to production and run final QA. Marketing: write a launch announcement post and a social media thread. Docs: write a quick-start user guide covering the three main sections of the site."

What you'll see:

/org initializing...

CEO Agent: Analyzing initiative scope...
  → 3 domains identified: Engineering, Marketing, Docs
  → Coordinating domain leads...

CTO: Planning engineering execution
  Wave 1: Pre-deployment checklist, final QA pass
  Wave 2: Production deployment, smoke test

CMO: Planning marketing execution
  Wave 1: Draft launch announcement post
  Wave 2: Social media thread (Twitter/X, LinkedIn)
  → Coordinating with Engineering for feature list

VP Support: Planning docs execution
  Wave 1: Site structure outline
  Wave 2: Quick-start guide (three main sections)
  → Coordinating with Engineering for accurate feature details

CEO Agent: Cross-domain plan validated. No conflicts.
  Proceeding to execution...

[Engineering] ⚠ QA pass - 1 issue found (broken image path on portfolio page)
[Engineering] ✓ Issue fixed, re-validated
[Engineering] ✓ Deployed to production
[Marketing]   ✓ Launch announcement drafted (823 words)
[Marketing]   ✓ Social thread drafted (6 posts)
[Docs]        ✓ Quick-start guide complete (1,200 words)

CEO Agent: Synthesizing outputs...
  → Announcement references correct feature set ✓
  → User guide sections match live site structure ✓
  → Social posts link to correct URLs ✓

Launch package ready.

All three tracks ran, cross-checked each other's outputs, and produced a coherent launch package. No manual coordination required on your end. Ask Claude "show me the launch package" and it will pull together the outputs from all three domains.

You've built out a content marketing strategy over the past few articles - you have a channel plan, four published posts, and clear messaging. Now it's time to activate the full launch: get the word out, equip the sales team, and prepare support for incoming questions.

That means marketing (social media launch plan), sales (pitch deck with the content angle), and support (FAQ for common questions about the content program). Three domains, all needing to reflect the same strategy.

/org "Full launch of the content marketing program. Marketing: write a social media launch plan for the first two weeks. Sales: create a one-page pitch deck showing the content program as a trust-building asset. Support: write an FAQ covering the top 10 questions customers are likely to ask about the new content."

The org layer handles the coordination that would otherwise fall on you:

CEO Agent: Analyzing initiative scope...
  → 3 domains identified: Marketing, Sales, Support
  → Strategic framing: content program as trust/credibility signal

CMO: Drafting two-week social launch plan
  → Platform breakdown: LinkedIn (primary), newsletter, Twitter/X
  → Coordinating with Sales on messaging tone

CSO: Creating one-page pitch deck
  → Positioning: content program as sales enablement asset
  → Pulling key stats and messaging from Marketing plan

VP Support: Writing customer FAQ
  → 10 questions identified from strategy documents
  → Coordinating with Marketing to align on program description

CEO Agent: Cross-domain plan validated.

[Marketing]  ✓ Two-week social launch plan (8 posts, 3 platforms)
[Sales]      ✓ One-page pitch deck (5 slides, PDF ready)
[Support]    ✓ FAQ document (10 Q&As, 1,400 words)

CEO Agent: Synthesizing outputs...
  → Pitch deck messaging consistent with social plan ✓
  → FAQ description of content program matches Marketing copy ✓

Launch package ready.

Without /org, you'd be passing context between three separate sessions, manually checking that the pitch deck says the same things as the social copy, and making sure support isn't describing the program in a way that contradicts marketing. The CEO agent does that work. When it's done, just ask Claude to show you the results - it knows where everything landed.

Maya's course materials are done -- /team built all six units in parallel and the quality gates caught the inconsistencies between rubrics. But she can't just start teaching differently. Her department chair needs to approve the standards alignment. The school librarian needs to prepare research resources for six project units. And the parent community needs to understand what's changing before the first day of class. These three stakeholder groups have different concerns, different formats, and different approval processes.

/org "Launch the redesigned US History course for fall semester.
Department: standards alignment report showing every Ohio standard is covered,
    comparison to previous course coverage.
Library: research resource guide for 6 project units, including databases,
    primary source archives, and book carts.
Parent outreach: welcome packet explaining PBL approach, FAQ, semester overview,
    and a sample rubric."

The CEO agent frames this as a stakeholder alignment initiative -- the strategic goal isn't the materials (those are done) but getting buy-in from three groups with different priorities:

CEO Agent: Analyzing initiative scope...
  → 3 domains identified: Department, Library, Parent Outreach
  → Strategic framing: stakeholder alignment for curriculum change

Department Lead: Standards alignment matrix
  → Mapping all 6 units to Ohio 10th-grade standards
  → Generating comparison: new PBL coverage vs. old lecture format

Library Lead: Research resource guide
  → Organizing databases and primary sources by unit
  → Building checkout schedule to avoid conflicts with other classes

Parent Outreach Lead: Welcome packet
  → FAQ addressing grading concerns (the #1 parent question for PBL)
  → Sample rubric showing how projects are scored
  → Coordinating with Department for consistent language on standards

CEO Agent: Cross-domain plan validated.

[Department] ✓ Standards matrix complete
  → New course covers 3 additional standards the old format missed
[Library]    ✓ Resource guide organized by unit (databases, archives, book carts)
[Parent]     ✓ Welcome packet with FAQ, overview, sample rubric

CEO Agent: Synthesizing outputs...
  → Parent FAQ describes grading consistently with actual rubrics ✓
  → Resource guide references correct unit topics and timelines ✓
  → ⚠ Library resource guide references JSTOR database access --
    school does not currently have a JSTOR subscription.
    Maya needs to request this before fall semester.

Stakeholder package ready.

The department report gives Maya ammunition she didn't expect: the new course actually covers more standards than the old one. The parent FAQ uses the same grading language as the rubrics -- the synthesis pass caught where the FAQ originally described assessment differently. And the JSTOR subscription gap? That's the kind of cross-domain dependency that surfaces only when someone checks whether the library's plan actually matches the school's resources. Without /org, Maya discovers that gap on the first day a student tries to access a database that doesn't exist.

David's Decatur location is almost ready. /team built the staffing plan, training materials, and menu design in parallel -- the quality gate caught a training manual referencing a sauce station the smaller kitchen doesn't have. Now it's opening week, and three domains need to move in lockstep: operations (health inspection, soft-opening logistics, grand opening runsheet), marketing (social media campaign, press release, influencer outreach), and staffing (final schedule, uniforms, day-one team briefing).

/org "Coordinate Decatur location opening week (Oct 1-7).
Operations: health inspection prep checklist, soft-opening dinner logistics
  (Oct 3, 30 invited guests), grand opening day runsheet (Oct 5).
Marketing: social media campaign (2 weeks pre-opening through opening week),
  local press release, influencer dinner invite list and outreach emails.
Staffing: opening week schedule for all 8 new hires, uniform order with sizes,
  day-one team briefing document."

The CEO agent catches something the three domains would have missed independently:

CEO Agent: Analyzing initiative scope...
  → 3 domains identified: Operations, Marketing, Staffing
  → ⚠ Coordination dependency detected: influencer dinner (Marketing)
    and soft-opening dinner (Operations) are the same event on Oct 3.
    Consolidating into a single joint plan.

COO: Operations planning
  → Health inspection prep: 47-item checklist from Atlanta health code
  → Soft-opening/influencer dinner: combined event plan, 30 guests
  → Grand opening runsheet: 6am kitchen prep through 10pm post-service

CMO: Marketing planning
  → Social campaign: countdown posts starting Sept 20
  → Press release: David's story + menu highlights + neighborhood angle
  → Influencer coordination: now aligned with soft-opening event logistics

CHRO: Staffing planning
  → Opening week schedule: all 8 hires, factoring soft-opening as all-hands
  → Uniform order: sizes confirmed, delivery by Sept 28
  → Day-one briefing: who does what, hour by hour

CEO Agent: Cross-domain plan validated.

[Operations] ✓ Inspection checklist, combined dinner plan, day runsheet
[Marketing]  ✓ Social campaign (14 posts), press release, influencer emails
[Staffing]   ✓ Schedule, uniform order, team briefing

CEO Agent: Synthesizing outputs...
  → Press release menu items match actual launch menu ✓
    (caught reference to egusi soup -- cut during menu reduction)
  → Staffing schedule accounts for soft-opening all-hands ✓
  → Grand opening runsheet integrates all 3 domains:
    hour-by-hour from 6am kitchen prep to 10pm social media posts

Opening week package ready.

The influencer-dinner/soft-opening merge is the key catch. Marketing was planning a curated influencer event. Operations was planning a soft-opening test run for the kitchen. Same date, same venue, same dinner -- but two different planning documents with different guest counts and different purposes. The CEO agent consolidated them into one event that serves both goals: the influencers get the authentic soft-opening experience, and the kitchen gets a real-conditions test run with guests who'll post about it.

Sadie's game is ready. /team built the trailer script, community posts, and 30 personalized press emails in parallel -- the quality gate flagged a journalist who hadn't published in 8 months. Now it's launch week, and three domains need to land in sequence: the build goes live on Steam, the marketing embargo lifts, and the community events kick off. The timing has to be precise because Steam's algorithm rewards launch-week velocity.

/org "Launch week for Meridian (Oct 14-18).
Engineering: final build verification, Steam upload, store page goes live
  Oct 14 10am PT.
Marketing: press embargo lifts Oct 14 9am PT (1 hour before store page),
  trailer drops on YouTube same time, social media campaign days 1-5.
Community: Discord launch-day event Oct 14 evening, first-48-hours review
  monitoring, community post schedule for the week."

The CEO agent flags a timing question and catches a scheduling conflict:

CEO Agent: Analyzing initiative scope...
  → 3 domains identified: Engineering, Marketing, Community
  → Timing note: press embargo (9am) lifts before store page (10am).
    Reviews go live before players can buy. Flagging for confirmation.
    [This is intentional for narrative games -- builds anticipation]

CTO: Engineering execution
  → Final build verification checklist (achievements, cloud saves, controller)
  → Steam build upload and store page activation sequence

CMO: Marketing execution
  → Embargo lift: press contacts notified, trailer goes public
  → Social campaign: posts timed 2 hours after embargo to ride review wave
  → Day 2-5 posts: user quotes, screenshot highlights, developer thread

Community Lead: Community execution
  → Discord launch-day event: live play-along, Q&A with Sadie
  → Pre-written responses for common scenarios (positive reviews,
    negative reviews, bug reports, "when is the Mac version?")
  → Review monitoring: first-48-hours sentiment tracking

CEO Agent: Cross-domain plan validated.

[Engineering] ✓ Build verification checklist, upload sequence
[Marketing]   ✓ Embargo coordination, 5-day social campaign
[Community]   ✓ Discord event plan, response templates, monitoring plan

CEO Agent: Synthesizing outputs...
  → Social posts reference correct store page URL ✓
  → Community response templates match marketing messaging ✓
  → ⚠ Scheduling conflict: Discord launch-day event (7pm PT) overlaps
    with Sadie's planned Twitch launch stream (7pm PT).
    She can't be in both places.
    Recommends: run the stream inside Discord, or move Discord event to Oct 15.

Launch week package ready.

The scheduling conflict is small but would have been embarrassing to discover at 6:55pm on launch day. Sadie planned the Discord event and the Twitch stream separately, weeks apart, and never noticed they overlapped. The CEO agent caught it because it reconciled the community timeline against the marketing timeline. That's the coordination layer doing its job.

Rosa's wedding documents are ready -- /team built the ceremony script, reception timeline, and day-of coordination doc in parallel, and the quality gate caught that the florist needed to arrive an hour earlier for the arch setup. Now it's the final week before a destination wedding in Todos Santos, Mexico, and three domains need to converge: vendor confirmations, guest logistics, and venue coordination. And the weather forecast just changed everything.

/org "Final week coordination for the Todos Santos wedding (7 days out).
Vendors: final confirmation calls, updated headcount (83 confirmed guests),
  dietary restriction list, final payment schedule.
Guests: final RSVP follow-up (4 non-responses), transportation confirmation
  for airport shuttle, welcome bag assembly list.
Venue: room block status, rehearsal dinner logistics, weather forecast review
  and contingency decision by Wednesday."

The CEO agent frames the entire week around one decision that affects everything:

CEO Agent: Analyzing initiative scope...
  → 3 domains identified: Vendors, Guests, Venue
  → Critical path: Wednesday weather contingency decision.
    Everything downstream depends on beach vs. indoor ceremony.
    Structuring all domain plans with conditional outputs.

Vendor Lead: Confirmation and logistics
  → 8 vendor confirmation calls with specific talking points per vendor
  → ⚠ Caterer's final headcount form requires dietary restrictions
    in Spanish (they cook from Spanish-language recipes)
  → Final payment schedule: 3 vendors due by Thursday, 5 on event day

Guest Lead: RSVP and transportation
  → Personalized follow-up for 4 non-responders
  → Transportation confirmation: 6 guests arriving Thursday, not Friday
    -- need early hotel check-in
  → Welcome bag assembly: 83 bags, contents list, packing volunteers

Venue Lead: Logistics and weather
  → Room block: 34 of 40 rooms confirmed
  → Rehearsal dinner: hotel terrace, 28 guests
  → ⚠ Weather forecast: 65% chance of afternoon showers Saturday
    Recommendation: activate rain contingency Plan B

CEO Agent: Weather contingency activation.
  This decision cascades to ALL domains. Producing change document...

┌─────────────────────────────────────────────────┐
│  PLAN B ACTIVATION -- Weather Contingency       │
│  Decision: activate indoor backup (hotel salon) │
├─────────────────────────────────────────────────┤
│                                                 │
│  VENDOR CHANGES:                                │
│  • Florist: arch relocated to salon entrance    │
│    (wind-resistant construction no longer        │
│    needed -- reallocate to fuller arrangement)   │
│  • Lighting designer: move string light plan    │
│    from beach poles to salon ceiling rigging     │
│  • DJ: indoor sound check instead of beach      │
│    setup, different acoustic profile             │
│  • Photographer: scout indoor portrait          │
│    locations by Thursday, update shot list       │
│                                                 │
│  GUEST CHANGES:                                 │
│  • Update welcome bag insert: ceremony at       │
│    hotel salon, not beach                        │
│  • Shuttle timing unchanged (same venue)        │
│  • Dress code note: heels now fine (not sand)   │
│                                                 │
│  VENUE CHANGES:                                 │
│  • Confirm salon availability and setup time    │
│  • Rehearsal dinner moves indoors if rain        │
│    starts early (terrace has no cover)           │
│  • Ceremony script: remove "sound of waves"     │
│    stage direction, add salon-specific cues      │
│                                                 │
│  TIMELINE IMPACT:                               │
│  • Florist arrival: unchanged (1pm)             │
│  • Lighting setup: +1 hour for ceiling rigging  │
│    (lighting designer now arrives at noon)       │
│  • Ceremony start: unchanged (4pm)              │
│  • Reception: unchanged (salon adjoins terrace  │
│    -- if skies clear, open terrace for cocktails)│
│                                                 │
└─────────────────────────────────────────────────┘

[Vendors]  ✓ Confirmation checklist with Plan B updates
[Guests]   ✓ Follow-ups sent, transport confirmed, welcome bags updated
[Venue]    ✓ Salon confirmed, rehearsal backup arranged

CEO Agent: Synthesizing outputs...
  → All vendor setup times adjusted for indoor venue ✓
  → Guest communications reflect ceremony location change ✓
  → Ceremony script references match indoor setting ✓
  → Day-of coordination doc updated across all vendor entries ✓

Final week package ready. Plan B fully activated.

This is /org at its most valuable. One decision -- activate the rain plan -- cascaded across every domain. The florist's arrangement changes because wind resistance doesn't matter indoors. The lighting designer needs extra rigging time, which shifts their arrival. The welcome bag inserts need reprinting. The ceremony script needs stage direction edits. The photographer needs new portrait locations. Each of these changes is small on its own. Missing any one of them means something goes wrong on the day.

Without /org, Rosa makes the weather call on Wednesday and then spends 48 hours manually updating every vendor, every guest communication, and every planning document. The Plan B activation document gives her one place where every change is tracked, every domain is aligned, and nothing falls through the gap between "we decided to move indoors" and "every vendor knows what that means for their setup."

Jordan's episodes are done -- /team built research packages and scripts for episodes 2-4 in parallel, with the quality gate flagging a sensitivity consideration for the Memphis episode. Now it's time to launch "Forgotten Picket Lines" across every platform simultaneously. Distribution needs to get the podcast on Apple, Spotify, and six secondary platforms. Marketing needs a social media campaign and cross-promotion pitches to other labor history shows. Community needs a newsletter, a feedback system, and discussion templates. All of it needs to describe the show consistently.

/org "Launch the podcast 'Forgotten Picket Lines' across all channels.
Distribution: submit to Apple Podcasts, Spotify, and 6 secondary platforms.
  RSS feed setup, episode metadata for first 3 episodes + trailer.
Marketing: social media launch campaign (Twitter, Instagram, Bluesky), trailer
  distribution plan, 5 cross-promotion pitches to labor history podcasts.
Community: newsletter setup (Substack or Buttondown), listener feedback form,
  episode discussion thread templates for each platform."

The CEO agent coordinates a unified show identity and catches a gap between domains:

CEO Agent: Analyzing initiative scope...
  → 3 domains identified: Distribution, Marketing, Community
  → Cross-domain dependency: show description must be consistent
    across all platforms. Creating unified "show identity" document
    for all domains to reference.

Distribution Lead: Platform submissions
  → RSS feed configured with show metadata
  → Platform-specific descriptions (Apple: 4,000 chars, Spotify: 600 chars,
    Pocket Casts, Overcast, etc. -- each has different limits)
  → Episode metadata: titles, descriptions, chapter markers, tags

CMO: Marketing execution
  → Social campaign: launch week posts across 3 platforms
  → Trailer distribution: YouTube, social clips, embeddable player
  → Cross-promotion pitches tailored to each target show:
    "Your episode on the Triangle Shirtwaist Fire is why I started this
    project -- Forgotten Picket Lines picks up where that story leaves off."

Community Lead: Listener infrastructure
  → Newsletter: Buttondown setup (better for small shows than Substack)
  → Feedback form: auto-categorizes into "story suggestions,"
    "corrections," and "general feedback"
  → Discussion templates: episode-specific threads for each platform

CEO Agent: Cross-domain plan validated.

[Distribution] ✓ RSS feed, 8 platform submissions, episode metadata
[Marketing]    ✓ Social campaign (12 posts), trailer plan, 5 pitches
[Community]    ✓ Newsletter, feedback pipeline, discussion templates

CEO Agent: Synthesizing outputs...
  → Show descriptions consistent across platforms ✓
  → Cross-promotion pitches align with show identity doc ✓
  → ⚠ Marketing's Instagram plan references video clips and reels,
    but Distribution only prepared audio assets.
    Recommends: create audiogram templates (waveform animations
    over still images) to bridge audio content and video-first platforms.

Launch package ready.

The audiogram recommendation is the synthesis doing its job. Marketing planned for Instagram, which is video-first. Distribution prepared audio files for podcast platforms. Neither domain was wrong -- they each optimized for their channel. But nobody planned the bridge between audio-only content and video-first social marketing. The CEO agent flagged the gap and proposed a practical solution: audiogram templates that turn audio clips into shareable video content without requiring Jordan to learn video editing on a weekend-and-evenings schedule.