Initial commit

This commit is contained in:
Zhongwei Li
2025-11-29 18:30:57 +08:00
commit 33ae5383b7
13 changed files with 417 additions and 0 deletions

View File

@@ -0,0 +1,31 @@
---
name: account-based-blueprint
description: Framework for consolidating manufacturing account intelligence, buying
centers, and pursuit strategy.
---
# Account-Based Blueprint Skill
## When to Use
- Kicking off strategic pursuits with multi-plant or multi-division manufacturers.
- Aligning sales, engineering, partners, and exec sponsors on account context.
- Preparing executive reviews or investment asks tied to major deals.
## Framework
1. **Account Overview** footprint, business units, strategic initiatives, installed base.
2. **Buying Centers & Stakeholders** org chart covering operations, engineering, IT/OT, finance, procurement.
3. **Current State & Pain Map** KPIs, constraints, compliance mandates, modernization priorities.
4. **Solution & Value Narrative** target workloads, reference architecture, ROI metrics, competitive positioning.
5. **Pursuit Plan** milestones, resource needs, partner involvement, escalation points.
## Templates
- Executive dossier (one-pager + slide) summarizing account insights.
- Stakeholder matrix with influence, priorities, relationships.
- Pursuit tracker with stages, owners, decision gates, and notes.
## Tips
- Refresh after every executive meeting or site visit.
- Attach site photos, process maps, or plant diagrams to improve context.
- Pair with `qualify-industrial-opportunity` and `run-deal-health-review` outputs.
---

View File

@@ -0,0 +1,30 @@
---
name: deal-health-dashboard
description: Reporting framework for executive visibility into manufacturing pursuits.
---
# Deal Health Dashboard Skill
## When to Use
- Preparing weekly executive reviews for large industrial pursuits.
- Surfacing blockers across technical validation, partner readiness, or procurement.
- Aligning sales, engineering, finance, and delivery teams on risk mitigation.
## Framework
1. **KPI Summary** stage, ACV/TCV, probability, forecast category, aging, next milestone.
2. **Workstream Tracker** technical validation, commercial approvals, legal, partner integration, financing.
3. **Risk Matrix** probability x impact grid covering stakeholders, solution gaps, competition, supply chain.
4. **Action Register** owner, action, due date, status, escalation level.
5. **Executive Narrative** key callouts, asks, and support needed.
## Templates
- Dashboard slide layout with KPI tiles, risk heatmap, and action table.
- Weekly summary memo template for ELT distribution.
- Risk/action tracker spreadsheet reusable across pursuits.
## Tips
- Pull data from CRM, project trackers, and partner portals to keep single source of truth.
- Highlight decision deadlines 2+ weeks out to secure resources early.
- Pair with `run-deal-health-review` to auto-populate updates.
---

View File

@@ -0,0 +1,31 @@
---
name: partner-integration-kit
description: Toolkit for coordinating system integrators, OEM partners, and service
vendors in manufacturing pursuits.
---
# Partner Integration Kit Skill
## When to Use
- Pursuits requiring multi-party delivery (automation, MES, IoT, safety systems).
- Onboarding new partners to co-sell or co-deliver solutions.
- Preparing integration readiness reviews or partner governance cadence.
## Framework
1. **Partner Matrix** catalog roles (SI, OEM, distributor), competencies, certifications, territories.
2. **Integration Requirements** data flows, protocols, safety/regulatory requirements, testing environments.
3. **Joint Value Narrative** messaging pillars, proof points, and differentiation with partners.
4. **Enablement & Governance** training plans, escalation matrix, release/change management.
5. **Performance Dashboard** pipeline contribution, stage progression, delivery KPIs, CSAT.
## Templates
- Partner kickoff deck (roles, deliverables, SLAs).
- Integration readiness checklist (systems, documentation, test cases).
- Joint success plan with KPIs, review cadence, risk tracker.
## Tips
- Capture NDAs, data-sharing agreements, and export control docs in the same workspace.
- Provide sandbox/demo environments to speed partner validations.
- Pair with `build-technical-bid-plan` and `run-deal-health-review` outputs.
---

View File

@@ -0,0 +1,31 @@
---
name: technical-bid-library
description: Central repository structure for manufacturing RFP responses, compliance
statements, and solution modules.
---
# Technical Bid Library Skill
## When to Use
- Preparing RFI/RFP responses requiring technical depth, safety certifications, or compliance proof.
- Accelerating reuse of architecture diagrams, BOMs, and validation plans.
- Enabling distributed teams/partners to contribute to proposals with version control.
## Framework
1. **Module Catalog** break components into reusable sections (architecture, safety, cybersecurity, sustainability, services).
2. **Metadata & Tagging** account, industry, standard, version, reviewer, expiration.
3. **Compliance Evidence** certifications, test results, maintenance schedules, ITAR/export controls.
4. **Content Governance** approval workflows, change logs, and ownership assignments.
5. **Distribution Layer** templates for decks, docs, and portal uploads.
## Templates
- Bid response outline with placeholders per section.
- BOM + pricing appendix template with configurable tables.
- Change log sheet capturing edits, reviewers, and attachments.
## Tips
- Store source files (CAD, spreadsheets) alongside PDFs to speed edits.
- Flag expired certifications automatically to prevent use in proposals.
- Pair with `build-technical-bid-plan` for populated submissions.
---