Developer Launch Packager

developer-launch-packager

Agent: Developer Relations Lead

L2 developer relations lead responsible for developer community signal extraction, developer GTM, experience review, feedback synthesis, and community growth.

Department ethos: ideal-marketing.md

Skill Description

Packages the developer launch assets including SDKs, sample apps, documentation, and announcement content into a coordinated release kit.

When to Use

• When a new developer product, API, or SDK is approaching launch and assets need to be bundled.
• When a major version release requires coordinated updates across documentation, samples, and announcement channels.
• When a partner integration launch needs a developer-facing asset package.
• When a conference or event keynote will announce developer capabilities and supporting materials must be ready.

Workflow

1. Inventory required assets: Use the asset inventory model in framework.md to list all assets required for the launch type (new product, major, minor, or patch). Assign owners and deadlines. Deliverable: asset checklist with owners and deadlines.
2. Coordinate with engineering: Confirm SDK and API readiness, version numbers per the semantic versioning reference in the framework, breaking changes, and deprecation notices. Complete Gate 1 from the pre-launch readiness gates. Deliverable: engineering sign-off document.
3. Prepare documentation: Ensure all docs are updated, reviewed, and published to staging. Write the changelog entry using the Keep a Changelog format from the framework. Complete Gate 2. Deliverable: documentation readiness confirmation.
4. Build sample applications: Create or update sample apps that demonstrate key use cases and run without error against the released SDK version. Deliverable: tested sample apps in target languages.
5. Draft announcement content: Write the launch blog post, release notes, social media posts, and developer newsletter section. Complete Gate 3. Deliverable: announcement content package.
6. Assemble and test the kit: Run through all four pre-launch readiness gates in the framework. Complete a first-run developer experience check to verify TTFHW and sample app integrity. Deliverable: tested launch kit with gate sign-off.
7. Execute launch sequence: Follow the launch sequence protocol from the framework — publish SDK first, then docs and changelog, then blog, then social, then newsletter. Record timestamps. Deliverable: launch execution log with publish timestamps.

Anti-Patterns

• Last-minute documentation: Starting documentation updates after the SDK is already released. Why: Developers arriving on launch day find incomplete or outdated docs, creating a negative first impression that is amplified by launch traffic volume.
• Untested samples: Shipping sample apps that were not tested against the final SDK version. Why: Broken samples are the single fastest way to destroy developer trust; developers who cannot run the sample will not try the product.
• Uncoordinated publish sequence: Publishing the blog announcement before the SDK or docs are live. Why: Excited developers click through to assets that do not exist yet, creating confusion and support burden during the highest-traffic window.

Output

On success: Produces a complete developer launch kit containing SDK packages, documentation, sample apps, announcement content, and a launch execution log. Delivered to developer relations, marketing, and engineering teams.

On failure: Report which assets are not ready, what blocks completion, and recommend a revised launch date or partial launch strategy. Every error must be actionable.

Related Skills

• developer-gtm-planner — Launch assets must align with the GTM channel strategy and messaging.
• api-documentation-designer — API documentation structure designed here feeds into the launch documentation package.
• developer-experience-reviewer — Launch kit should be validated through a developer experience review before release.