Initial commit

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

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

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