From 30eb814cbb8c3d1a0337ec699c6138591e4db038 Mon Sep 17 00:00:00 2001 From: Zhongwei Li Date: Sat, 29 Nov 2025 18:31:20 +0800 Subject: [PATCH] Initial commit --- .claude-plugin/plugin.json | 24 +++++++++++ README.md | 3 ++ agents/enablement-captain.md | 27 ++++++++++++ agents/launch-director.md | 30 +++++++++++++ agents/workstream-lead.md | 27 ++++++++++++ commands/assemble-war-room.md | 33 +++++++++++++++ commands/post-launch-retro.md | 33 +++++++++++++++ commands/run-launch.md | 48 +++++++++++++++++++++ plugin.lock.json | 77 ++++++++++++++++++++++++++++++++++ skills/launch-tiering/SKILL.md | 31 ++++++++++++++ skills/risk-playbooks/SKILL.md | 39 +++++++++++++++++ skills/war-room-ops/SKILL.md | 30 +++++++++++++ 12 files changed, 402 insertions(+) create mode 100644 .claude-plugin/plugin.json create mode 100644 README.md create mode 100644 agents/enablement-captain.md create mode 100644 agents/launch-director.md create mode 100644 agents/workstream-lead.md create mode 100644 commands/assemble-war-room.md create mode 100644 commands/post-launch-retro.md create mode 100644 commands/run-launch.md create mode 100644 plugin.lock.json create mode 100644 skills/launch-tiering/SKILL.md create mode 100644 skills/risk-playbooks/SKILL.md create mode 100644 skills/war-room-ops/SKILL.md diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json new file mode 100644 index 0000000..ba0b87c --- /dev/null +++ b/.claude-plugin/plugin.json @@ -0,0 +1,24 @@ +{ + "name": "product-launch-orchestration", + "description": "Product launch governance orchestrator covering war rooms, execution, and retros", + "version": "1.0.0", + "author": { + "name": "GTM Agents", + "email": "opensource@intentgpt.ai" + }, + "skills": [ + "./skills/launch-tiering/SKILL.md", + "./skills/war-room-ops/SKILL.md", + "./skills/risk-playbooks/SKILL.md" + ], + "agents": [ + "./agents/launch-director.md", + "./agents/workstream-lead.md", + "./agents/enablement-captain.md" + ], + "commands": [ + "./commands/assemble-war-room.md", + "./commands/run-launch.md", + "./commands/post-launch-retro.md" + ] +} \ No newline at end of file diff --git a/README.md b/README.md new file mode 100644 index 0000000..3d6520e --- /dev/null +++ b/README.md @@ -0,0 +1,3 @@ +# product-launch-orchestration + +Product launch governance orchestrator covering war rooms, execution, and retros diff --git a/agents/enablement-captain.md b/agents/enablement-captain.md new file mode 100644 index 0000000..73e6ada --- /dev/null +++ b/agents/enablement-captain.md @@ -0,0 +1,27 @@ +--- +name: enablement-captain +description: Ensures sales, CS, and partner teams are trained, equipped, and ready for launch day. +model: haiku +--- + +# Enablement Captain Agent + +## Responsibilities +- Build enablement plans covering messaging, demos, objection handling, and success plays. +- Coordinate content creation (decks, scripts, competitive notes), LMS uploads, and certification flows. +- Schedule enablement sessions, office hours, and follow-up assessments. +- Gather field feedback to iterate assets throughout launch window. + +## Process +1. **Launch Intake** – review tier, target personas, product readiness, release dates. +2. **Audience Mapping** – identify required audiences (AEs, SEs, CSMs, partners) and prioritize regions. +3. **Curriculum Planning** – define sessions, formats, assets, certification requirements. +4. **Delivery & QA** – run enablement sessions, capture attendance, test knowledge. +5. **Feedback Loop** – collect rep feedback, update assets, communicate changes to war-room. + +## Outputs +- Enablement roadmap (sessions, owners, due dates, KPIs). +- Asset kit (decks, FAQ, demo scripts, cheat sheets) with version control. +- Feedback log plus action items for post-launch improvements. + +--- diff --git a/agents/launch-director.md b/agents/launch-director.md new file mode 100644 index 0000000..78b97f5 --- /dev/null +++ b/agents/launch-director.md @@ -0,0 +1,30 @@ +--- +name: launch-director +description: Owns cross-functional launch governance, ensuring workstreams, KPIs, + and risks stay aligned. +model: sonnet +--- + + + +# Launch Director Agent + +## Responsibilities +- Translate product/exec goals into launch tiering, success metrics, and governance cadence. +- Coordinate workstreams across product marketing, demand gen, enablement, customer success, ops, and comms. +- Maintain source-of-truth boards (roadmap, risk log, decision register). +- Drive pre-launch checkpoints, go/no-go reviews, and post-launch retros. + +## Workflow +1. **Brief Intake** – capture product value, target personas, readiness checkpoints, dependent features. +2. **Tiering & Scope** – size the launch (Tier 1/2/3) with budget, channels, asset requirements. +3. **Workstream Planning** – assign owners, timelines, and definitions of done per function. +4. **Governance Rituals** – schedule war-room standups, risk reviews, and exec updates. +5. **Measurement Alignment** – confirm KPIs, instrumentation, dashboards, and reporting cadence. + +## Outputs +- Launch governance plan (tier, workstreams, owners, checkpoints). +- Risk/decision log with status and mitigation owners. +- Communication plan for execs, stakeholders, and post-launch reporting. + +--- diff --git a/agents/workstream-lead.md b/agents/workstream-lead.md new file mode 100644 index 0000000..f0bf35d --- /dev/null +++ b/agents/workstream-lead.md @@ -0,0 +1,27 @@ +--- +name: workstream-lead +description: Coordinates execution for a specific launch workstream (content, demand, enablement, success). +model: haiku +--- + +# Launch Workstream Lead Agent + +## Responsibilities +- Convert overall launch plan into detailed tasks, owners, and SLAs for the assigned workstream. +- Track dependencies (assets, approvals, tooling) and escalate blockers quickly. +- Collaborate cross-functionally to keep timelines aligned and deliverables on-brand/compliant. +- Provide status updates for war-room standups and exec readouts. + +## Process +1. **Plan Intake** – review launch tier, objectives, assigned deliverables, budgets. +2. **Task Breakdown** – create project plan with milestones, owners, due dates, success criteria. +3. **Dependency Management** – identify asset gaps, vendor needs, content reviews, localization. +4. **QA & Launch Readiness** – verify acceptance criteria, performance benchmarks, instrumentation. +5. **Reporting** – update dashboards/boards, highlight risks, log decisions/changes. + +## Outputs +- Workstream project plan (timeline, owners, dependencies). +- Status update templates for war-room. +- Risk + mitigation list for assigned workstream. + +--- diff --git a/commands/assemble-war-room.md b/commands/assemble-war-room.md new file mode 100644 index 0000000..a4510df --- /dev/null +++ b/commands/assemble-war-room.md @@ -0,0 +1,33 @@ +--- +name: assemble-war-room +description: Produces launch governance plan with tiering, workstreams, cadences, and risk controls. +usage: /product-launch-orchestration:assemble-war-room --product "AI Copilot" --tier 1 --date 2025-02-10 +--- + +# Command: assemble-war-room + +## Inputs +- **product** – launch name/identifier. +- **tier** – 1/2/3 severity. +- **date** – GA/announce date. +- **workstreams** – optional list (content, demand, enablement, success, ops, comms). +- **budget** – optional budget allocation. + +## Workflow +1. **Tiering Confirmation** – validate scope, KPIs, required workstreams, governance level. +2. **Workstream Chartering** – assign leads, deliverables, milestones, dependencies. +3. **War-Room Cadence** – define standups, risk reviews, exec syncs, communication channels. +4. **Risk & Decision Logs** – create templates and owners for mitigation + decision tracking. +5. **Enablement Hooks** – ensure enablement captain + workstream leads have onboarding instructions. + +## Outputs +- War-room charter (tier, goals, KPIs, stakeholders, cadence). +- Workstream RACI + timeline board outline. +- Risk/decision log templates with owners + escalation paths. + +## Agent/Skill Invocations +- `launch-director` – leads governance plan. +- `workstream-lead` – confirms deliverables per function. +- `launch-tiering` skill – enforces tier criteria + budgets. + +--- diff --git a/commands/post-launch-retro.md b/commands/post-launch-retro.md new file mode 100644 index 0000000..2d886c1 --- /dev/null +++ b/commands/post-launch-retro.md @@ -0,0 +1,33 @@ +--- +name: post-launch-retro +description: Produces a retrospective plan summarizing launch performance, learnings, and follow-up actions. +usage: /product-launch-orchestration:post-launch-retro --product "AI Copilot" --window 30d --audience "exec" +--- + +# Command: post-launch-retro + +## Inputs +- **product** – launch identifier. +- **window** – timeframe to evaluate (7d, 30d, quarter). +- **audience** – intended audience (exec, GTM, product, board). +- **kpis** – optional list of KPIs to spotlight. +- **feedback_sources** – optional sources (CS, community, partners, analysts). + +## Workflow +1. **Data Snapshot** – gather product metrics, pipeline, revenue, adoption, support volume, sentiment. +2. **Workstream Review** – collect inputs from each owner (what worked, blockers, improvements). +3. **Customer/Market Feedback** – summarize quotes, reviews, analyst reactions, competitor moves. +4. **Action Plan** – prioritize follow-up work (bugs, roadmap updates, enablement refresh, marketing plays). +5. **Retro Meeting Facilitation** – propose agenda, facilitation plan, decision/owner logging. + +## Outputs +- Retro deck/brief (objectives, KPIs, highlights, lowlights, actions). +- Consolidated feedback log + sentiment analysis. +- Action register with owners, due dates, and impact. + +## Agent/Skill Invocations +- `launch-director` – runs retro and maintains decision/action logs. +- `enablement-captain` – contributes field feedback + follow-up training. +- `risk-playbooks` skill – ensures lessons learned feed future mitigation plans. + +--- diff --git a/commands/run-launch.md b/commands/run-launch.md new file mode 100644 index 0000000..640e638 --- /dev/null +++ b/commands/run-launch.md @@ -0,0 +1,48 @@ +--- +name: run-launch +description: Creates launch execution runbook covering timeline, comms, instrumentation, and go/no-go gates. +usage: /product-launch-orchestration:run-launch --product "AI Copilot" --window 14d --channels "email,press,webinars" +--- + +# Command: run-launch + +## Inputs +- **product** – launch identifier. +- **window** – time horizon for execution (e.g., 14d, 30d). +- **channels** – comma-separated channels/workstreams. +- **dependencies** – optional gating items (feature flag, pricing, legal approval). +- **alerts** – optional monitoring thresholds (error rate, adoption, PR sentiment). + +### GTM Agents Pattern & Plan Checklist +> Inspired by GTM Agents orchestrator guidance @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Start with **pipeline** (timeline → comms → instrumentation → gates → command center). Use **diamond** when channel workstreams can run in parallel; note selection in plan header. +- **Plan schema**: Save `.claude/plans/plan-.json` with objective, stages, parallel groups, agent assignments, context passing (e.g., feature readiness), error handling, and success criteria (launch KPIs). +- **Tool hooks**: Reference `docs/gtm-essentials.md` (Serena for doc/code patches, Context7 for platform docs, Sequential Thinking for retros, Playwright for pre-launch QA). +- **Guardrails**: Define retry strategy (default 2 attempts) and escalation ladder (Launch Director → Product Marketing Lead → CSO) for failed gates. +- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` checklist before execution to confirm agents, dependencies, and deliverables. + +## Workflow +1. **Timeline Build** – map critical path (code freeze, press embargo, enablement, GA) with owners. +2. **Communication Plan** – outline internal + external comms (press, blog, email, social, CS updates). +3. **Instrumentation & Monitoring** – confirm telemetry, dashboards, alerting, and logging. +4. **Go/No-Go Gates** – document readiness checklist, fallback plans, rollback triggers, decision authority. +5. **Launch-Day Command Center** – schedule standups, escalation tree, backlog triage process. + +## Outputs +- Launch execution runbook (timeline, tasks, owners, dependencies). +- Go/no-go checklist + approval matrix. +- Monitoring plan with dashboard links and alert thresholds. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `launch-director` – orchestrates execution + governance. +- `workstream-lead` – ensures deliverables per channel. +- `war-room-ops` skill – defines command center rituals. + +## GTM Agents Safeguards +- **Fallback agents**: document substitutions (e.g., Workstream Lead covering enablement) when specialists unavailable. +- **Escalation triggers**: if launch KPIs (error rate, adoption, sentiment) breach guardrails twice within 24h, execute rollback path and notify Exec Sponsor per war-room ops skill. +- **Plan maintenance**: revise plan JSON whenever dependencies, owners, or gates change; log updates in status packets. + +--- diff --git a/plugin.lock.json b/plugin.lock.json new file mode 100644 index 0000000..92cd266 --- /dev/null +++ b/plugin.lock.json @@ -0,0 +1,77 @@ +{ + "$schema": "internal://schemas/plugin.lock.v1.json", + "pluginId": "gh:gtmagents/gtm-agents:plugins/product-launch-orchestration", + "normalized": { + "repo": null, + "ref": "refs/tags/v20251128.0", + "commit": "641a94da7b98a81468b42796d5ad2dfd467d130a", + "treeHash": "4ec4f41801bce70190365658acaf3dc7c358784bb5a09e4d2375b9b250e9b3f7", + "generatedAt": "2025-11-28T10:17:11.227237Z", + "toolVersion": "publish_plugins.py@0.2.0" + }, + "origin": { + "remote": "git@github.com:zhongweili/42plugin-data.git", + "branch": "master", + "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390", + "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data" + }, + "manifest": { + "name": "product-launch-orchestration", + "description": "Product launch governance orchestrator covering war rooms, execution, and retros", + "version": "1.0.0" + }, + "content": { + "files": [ + { + "path": "README.md", + "sha256": "f481564c98f9f1e9577aa5dfe60c533731b37ae545de53383a2be2bbc94afc91" + }, + { + "path": "agents/workstream-lead.md", + "sha256": "f58f88dcb66cba8d95c4617dbb92305d73874ff9f87119b8c96a215f655d738d" + }, + { + "path": "agents/launch-director.md", + "sha256": "df4442c2c7cc0224fb0df53d8488304c917e9da86f709eec4f4bfb60c65edf7d" + }, + { + "path": "agents/enablement-captain.md", + "sha256": "8ba72b88ecc1f6853539fb3d7e98ed14882f02607b268eaeedfecfabe3352dce" + }, + { + "path": ".claude-plugin/plugin.json", + "sha256": "c676350f8bce8a0514d78918690dbce8f878d960d6deb913b5240e9e54058cb5" + }, + { + "path": "commands/assemble-war-room.md", + "sha256": "53f62c8955e15f131534c2ce29a9e09a311ccf006d795a6a00b9694fd5098c25" + }, + { + "path": "commands/post-launch-retro.md", + "sha256": "30e02fb26726ccb3a9f530bcc15730ec84cd6bd4be333ec8e8406cabb174d9a6" + }, + { + "path": "commands/run-launch.md", + "sha256": "10a6be37347418facdd5488bb579a80736d51eb19884752f1b133371b299985b" + }, + { + "path": "skills/risk-playbooks/SKILL.md", + "sha256": "b80ed52cd05bb05a46abe7f8bf78e38f09f68fa5980c478164c71db55bc829f0" + }, + { + "path": "skills/launch-tiering/SKILL.md", + "sha256": "8c5f0a2608a1a0c88210396bb3b7fc3f37b077ce721e116b1524232ca2e8e0f1" + }, + { + "path": "skills/war-room-ops/SKILL.md", + "sha256": "223b007823606556aa7a2f56a5eff96ca1c8d6463e908cce1b32c2a5adc5a490" + } + ], + "dirSha256": "4ec4f41801bce70190365658acaf3dc7c358784bb5a09e4d2375b9b250e9b3f7" + }, + "security": { + "scannedAt": null, + "scannerVersion": null, + "flags": [] + } +} \ No newline at end of file diff --git a/skills/launch-tiering/SKILL.md b/skills/launch-tiering/SKILL.md new file mode 100644 index 0000000..13dc738 --- /dev/null +++ b/skills/launch-tiering/SKILL.md @@ -0,0 +1,31 @@ +--- +name: launch-tiering +description: Use when sizing go-to-market launches by impact, resources, and governance + needs. +--- + +# Launch Tiering Framework Skill + +## When to Use +- Evaluating upcoming releases to determine Tier 1/2/3 scope. +- Aligning stakeholders on budget, channels, and required deliverables. +- Documenting launch expectations for planning, approvals, and reporting. + +## Framework +1. **Impact Criteria** – ARR target, product scope, audience reach, competitive urgency. +2. **Resource Requirements** – channels activated, creative/engineering effort, regional needs. +3. **Governance Level** – exec involvement, war-room cadence, risk tolerance. +4. **Instrumentation** – telemetry readiness, reporting complexity, experimentation. +5. **Compliance & Dependencies** – legal/security review, partner commitments, support readiness. + +## Templates +- Tier scoring matrix (criteria, weights, thresholds, recommended resourcing). +- Tier playbook (required workstreams, artifacts, checkpoints, reporting). +- Approval checklist for tier changes or escalations. + +## Tips +- Reassess tier mid-cycle if scope or market conditions shift. +- Maintain a historical log of tier decisions for future benchmarking. +- Tie tier definitions to budgeting + staffing models to ensure consistency. + +--- diff --git a/skills/risk-playbooks/SKILL.md b/skills/risk-playbooks/SKILL.md new file mode 100644 index 0000000..d6a176d --- /dev/null +++ b/skills/risk-playbooks/SKILL.md @@ -0,0 +1,39 @@ +--- +name: risk-playbooks +description: Use when identifying launch risks, mitigation plans, and escalation owners. +--- + +# Launch Risk Playbooks Skill + +## When to Use +- Pre-launch risk assessments and go/no-go criteria. +- During launch week to monitor escalations and coordinate mitigations. +- Post-launch retros to capture lessons and update future playbooks. + +## Framework +Launch risk governance combines categorical coverage with a repeatable execution cadence. Use the following building blocks to keep Tier 1+ launches on track. + +### Risk Categories +1. **Product & Reliability** – feature readiness, bugs, infrastructure load, rollback paths. +2. **Go-to-Market** – messaging accuracy, asset approvals, channel readiness, partner alignment. +3. **Compliance & Legal** – policy reviews, privacy terms, licensing, regional constraints. +4. **Support & Success** – staffing levels, escalation handoffs, enablement coverage. +5. **External Factors** – competitor moves, macro events, press sentiment, supply chain. + +### Execution Process +1. Identify risks w/ likelihood + impact scoring. +2. Assign owners, mitigation steps, triggers, fallback actions. +3. Maintain real-time risk log during war-room standups. +4. Capture resolution notes + update future tiering guidelines. + +## Templates +- Risk register (description, likelihood, impact, owner, mitigation, status). +- Escalation playbook (trigger, communication plan, action tree). +- Lessons learned tracker feeding future launches. + +## Tips +- Pre-populate risk banks per tier to accelerate planning. +- Tie mitigations to instrumentation/alerts to catch issues early. +- Share summaries with execs daily during Tier 1 launches. + +--- diff --git a/skills/war-room-ops/SKILL.md b/skills/war-room-ops/SKILL.md new file mode 100644 index 0000000..576d0f0 --- /dev/null +++ b/skills/war-room-ops/SKILL.md @@ -0,0 +1,30 @@ +--- +name: war-room-ops +description: Use when running launch command centers, standups, and escalation workflows. +--- + +# War-Room Operations Skill + +## When to Use +- Launches requiring daily standups and cross-functional coordination. +- Managing high-risk windows (launch week, pricing changes, major PR events). +- Ensuring swift resolution of issues and clear stakeholder comms. + +## Framework +1. **Cadence & Channels** – schedule standups, async updates, and escalation channels (Slack, pager, email). +2. **Rituals** – agenda for standups (status, blockers, metrics), risk reviews, exec syncs. +3. **Escalation Paths** – define severity levels, decision owners, fallback contacts. +4. **Documentation** – central log for decisions, incidents, mitigations, deployments. +5. **Monitoring Hooks** – dashboards, alert routing, on-call rotations, support coverage. + +## Templates +- War-room charter (objectives, team, schedule, SLAs). +- Standup template (status, blockers, next actions, owners). +- Escalation matrix (severity, trigger, contact tree, resolution target). + +## Tips +- Keep war-room staffed with empowered decision makers. +- Record all decisions + rationale for post-launch retros. +- Automate reminders for updates to reduce noise. + +---