Initial commit

This commit is contained in:
Zhongwei Li
2025-11-29 18:30:39 +08:00
commit 5699f8df12
14 changed files with 455 additions and 0 deletions

View File

@@ -0,0 +1,31 @@
---
name: cxo-briefing-kit
description: Use to package concise executive updates, decks, and decision logs for
enterprise pursuits.
---
# CXO Briefing Kit Skill
## When to Use
- Preparing executive sponsor briefings ahead of milestone meetings.
- Summarizing pursuit status for CRO, COO, CFO, or CEO stakeholders.
- Logging decisions, risks, and asks after executive reviews.
## Framework
1. **Audience Snapshot** note executive priorities, role, and preferred format.
2. **Headline & Status** articulate deal stage, confidence, and key wins/risks.
3. **Value Story** highlight quantified impact + proof tied to executive objectives.
4. **Decision & Ask** specify approvals, resources, or unblockers required.
5. **Action & Follow-up** capture owners, due dates, and communication plan.
## Templates
- One-slide exec update (headline, metrics, risks, asks).
- Briefing memo outline with context, status, decisions, next steps.
- Decision log sheet with timestamp, owner, outcome.
## Tips
- Keep main slide under 150 words; push detail to appendix.
- Tailor numbers to executive KPIs (margin, risk, innovation, customer impact).
- Pair with `pursuit-governance` to keep cadences consistent.
---

View File

@@ -0,0 +1,31 @@
---
name: procurement-playbook
description: Use to manage legal, security, and procurement workflows for complex
deals.
---
# Procurement Playbook Skill
## When to Use
- Enterprise deals entering security/privacy review or contract negotiation.
- RFP/RFI responses requiring coordinated SME input.
- Situations with heavy exception requests, custom terms, or compliance evidence.
## Framework
1. **Requirement Intake** capture questionnaires, policy docs, and mandatory deliverables.
2. **Workstream Mapping** assign internal SMEs (legal, security, privacy, finance) with timelines.
3. **Evidence Library** maintain templates for SOC2, penetration tests, insurance, data flows, DPIA.
4. **Exception Management** document asks, approvals, fallback positions, and decision owners.
5. **Closeout** log final concessions, expirations, and follow-up obligations.
## Templates
- Procurement workback plan (deliverable, owner, due date, status).
- Security questionnaire index with sourcing notes.
- Exception request log with approval layers.
## Tips
- Keep source-of-truth links updated; expired certifications stall reviews.
- Coordinate with `cxo-briefing-kit` for executive escalations.
- Pair with `risk-register` to surface procurement blockers early.
---

View File

@@ -0,0 +1,31 @@
---
name: pursuit-governance
description: Use to set cadences, decision logs, and escalation paths for enterprise
pursuits.
---
# Pursuit Governance Playbook Skill
## When to Use
- Launching complex pursuits with multiple internal workstreams.
- Preparing executive steering updates for strategic deals.
- Standardizing standups, decision logs, and risk reviews across regions.
## Framework
1. **Cadence Matrix** define daily standups, weekly exec reviews, and async updates per workstream.
2. **Decision Log** capture requests, approvals, and rationale with timestamps and owners.
3. **Escalation Paths** map issue severity to escalation channels (CRO, legal, product, finance).
4. **Communication Kit** templates for updates, dashboards, and summaries.
5. **Retrospective Loop** schedule debriefs and feed insights back into playbooks.
## Templates
- Pursuit governance calendar.
- Decision log sheet (request, owner, status, timestamp).
- Escalation matrix with contacts and SLAs.
## Tips
- Keep cadences lightweight; combine workstreams where possible to avoid meeting overload.
- Use a shared workspace (Notion, Asana, Sheets) for transparency.
- Pair with `risk-register` to ensure escalations include mitigation details.
---

View File

@@ -0,0 +1,31 @@
---
name: risk-register
description: Use to track pursuit risks, owners, mitigation steps, and escalation
triggers.
---
# Enterprise Risk Register Skill
## When to Use
- During enterprise pursuits with multiple high-stakes dependencies.
- Preparing executive updates or steering committee reviews.
- Handing off deals between pursuit phases or regions.
## Framework
1. **Risk Catalog** categorize by workstream (value, product, legal, security, executive, finance).
2. **Scoring** likelihood x impact, color-coded with thresholds for escalation.
3. **Mitigation Plan** define owner, action, due date, and supporting resources.
4. **Watchlist & Escalation** highlight items nearing deadlines or requiring CRO/exec attention.
5. **Retrospective** update playbooks with resolved risks + guidance.
## Templates
- Risk register table (risk, category, score, owner, mitigation, status).
- Weekly summary slide for executive steering meetings.
- Escalation request form with context + proposed action.
## Tips
- Keep risk statements precise (impact + trigger) to aid decision-making.
- Default to weekly updates; high-risk deals may require twice-weekly cadences.
- Align scoring with `pursuit-governance` to maintain consistent reporting.
---

View File

@@ -0,0 +1,31 @@
---
name: value-story-framework
description: Use to craft executive-ready value narratives and ROI/TCO stories for
enterprise pursuits.
---
# Value Story Framework Skill
## When to Use
- Translating discovery insights into quantified impact stories.
- Preparing executive briefings or RFP narrative sections.
- Aligning sellers, value engineers, and finance on assumptions.
## Framework
1. **Headline Impact** state quantified outcome (savings, revenue, risk reduction) with time horizon.
2. **Driver Pillars** break impact into 3-4 drivers with supporting data or benchmark references.
3. **Proof Layer** attach customer stories, product metrics, or analyst stats per driver.
4. **Execution Plan** outline phases, required resources, and success metrics.
5. **Decision Ask** specify commitments, timeline, and next-step expectations.
## Templates
- Value narrative deck outline (headline, drivers, proof, plan, ask).
- ROI/TCO worksheet with inputs, assumptions, scenario toggles.
- Executive one-pager layout for CXO readouts.
## Tips
- Keep assumptions transparent; include sensitivity +/- ranges.
- Mirror customer language from discovery to reinforce credibility.
- Pair with `cxo-briefing-kit` to ensure outputs land with each stakeholder.
---