Initial commit

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.
+
+---

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.
+
+---

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-<timestamp>.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.
+
+---