community-automations/launch-crew

DevOps & Code

PublicClaude subagent

Launch Crew

A launch needs copy, visuals, and email all saying the same thing, and chasing three people to align them eats the week. This crew runs them from one brief.

sonnet1 weekCrewAIOpenAIDALL-EMailchimp
ClaudeClaude
ROI for
README.md

Why this subagent

A launch needs copy, visuals, and email all saying the same thing, and chasing three people to align them eats the week. This crew runs them from one brief.

A lead agent splits the brief and dispatches copy, image, and email agents in parallel, then assembles their work into a consistent package. You hand over one brief and get a coordinated launch kit back, staged for your review.

How it runs

    • Read

      Used at step 01 to kick off the pipeline.

    • Write

      Used at step 01 to kick off the pipeline.

    • WebFetch

      Used at step 01 to kick off the pipeline.

    • WebSearch

      Used at step 01 to kick off the pipeline.

Sample output

json
// Sample output
// (generated when the pipeline finishes)

As the lead agent, turn one launch brief into parallel assignments for copy, image, and email sub-agents, then assemble their outputs into a single launch package consistent with the brief's positioning.

Unlock the rest

The full agent definition, install snippet, and starter task are gated for community members.

Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.