# Orchestrate a Product Launch

Product launches fail when research, development, marketing, sales, and support move in separate plans. This skill gives Claude, Codex, and Claude Code a structured multi-agent launch workflow from strategy through post-launch optimization.

## Install

```bash
npx skillstore add dnyoussef/when-releasing-new-product-orchestrate-product-launch
```

## Metadata

- Status: approved
- Slug: dnyoussef-when-releasing-new-product-orchestrate-product-launch
- Skillstore revision: r1
- Version status: missing
- Tree hash: cf242b0c1759961c24bb4b565d97810126a5518513e711164bdd1936e4aa791c
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/when-releasing-new-product-orchestrate-product-launch
- Ref: 0519034dad657fb1f7706e0550e962beeda73fdf
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 76
- Public page: https://skillstore.pages.dev/skills/dnyoussef-when-releasing-new-product-orchestrate-product-launch
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-when-releasing-new-product-orchestrate-product-launch/manifest

## Capabilities

- Coordinates research, business analysis, product strategy, development, marketing, launch execution, and optimization phases.
- Defines specialist agent roles and handoffs for product launch planning.
- Provides phased timelines, deliverables, success criteria, and memory key conventions.
- Includes Claude Flow command examples for spawning agents, storing outputs, restoring sessions, and exporting summaries.
- Supplies launch examples for SaaS products, mobile apps, and enterprise B2B products.

## Use Cases

- Plan a SaaS Launch: Create a phased launch plan that connects market research, product strategy, development readiness, launch execution, and weekly optimization.
- Coordinate Engineering Readiness: Align backend, frontend, mobile, database, security, QA, and deployment work around clear phase gates and deliverables.
- Prepare Go-To-Market Operations: Build a coordinated plan for campaigns, content, SEO, sales enablement, support readiness, launch metrics, and post-launch review.

## Prompt Templates

### Start a Launch Plan

```
Use this skill to plan a launch for [product]. Ask me for missing context before creating the phase plan.
```

### Define Phase Deliverables

```
Use this skill to define deliverables, owners, dependencies, and success criteria for each launch phase for [product].
```

### Coordinate Team Handoffs

```
Use this skill to map handoffs between product, engineering, marketing, sales, support, and operations for our launch.
```

### Run Readiness Review

```
Use this skill to run a go/no-go launch readiness review. Include risks, blockers, owners, mitigations, and post-launch metrics.
```

## Limitations

- Requires user review before running any shell or npx command.
- Does not replace legal, compliance, security, or financial review.
- Assumes Claude Flow or compatible orchestration tooling is installed.
- Needs product-specific inputs, budgets, market data, and team constraints.

## Best Practices

- Confirm installed tools and permissions before using any command examples.
- Fill product name, target market, launch date, budget, and team ownership before starting.
- Review each phase gate with business, engineering, security, and support owners.

## Anti Patterns

- Running npx or deployment commands without user approval.
- Using generic market assumptions when customer research is available.
- Treating post-launch optimization as optional after launch week.

## Security Audit

- Audited at: 2026-07-09T12:23:32.325\+00:00
- Summary: Most static hits are Markdown backticks, code fence markers, memory key examples, or GraphViz labels rather than Ruby backtick execution or reconnaissance. The real concerns are documented bash and npx claude-flow command examples plus shared /tmp export paths, which require user approval and safer file handling. No prompt-injection text or data-exfiltration intent was found in the reviewed files.

## Stats

- Views: 336
- Downloads: 9
- Favorites: 0
- Popularity score: 0