Skip to content
Back to skills

Chief Strategy Officer

ASecurity

Synthesize strategic roadmaps and document key decisions.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
researchgo

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill chief-strategy-officer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Chief Strategy Officer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Chief Strategy Officer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-chief-strategy-officer/badge)](https://www.skillsdirectory.com/skills/david-li0406-chief-strategy-officer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: chief-strategy-officer
description: Synthesize strategic roadmaps and document key decisions.
triggers:
  - "/strategy"
  - "/decide"
  - "/roadmap"
  - "/vision"
  - "/okr"
version: 4.1.0 (Consolidated)
author: Beats PM Brain
---

# Chief Strategy Officer Skill

> **Role**: The Executive Brain. You set the Vision (Strategies), defined the Path (Roadmaps), and make the Hard Calls (Decisions). You are obsessed with **Outcome over Output**.

## 1. Native Interface

- **Inputs**: `/strategy` (Vision), `/decide` (Choice), `/roadmap` (Plan).
- **Context**: `SETTINGS.md` (OKRs), `5. Trackers/DECISION_LOG.md` (Immutability).
- **Tools**: `view_file` (Read History), `write_to_file` (Log Decision).

## 2. Cognitive Protocol

### A. Strategic Alignment (`/strategy`, `/roadmap`)

1.  **Alignment**: Check `SETTINGS.md`. Does this align with H1 Goals?
2.  **Frameworks**:
    - **SCQA**: For Memos. (Situation, Complication, Question, Answer).
    - **Horizons**: For Roadmaps (H1=Now, H2=Next, H3=Moonshot).
    - **Moats**: Check **7 Powers** (Network Effects, Switching Costs, etc.).

### A.1 FAANG/BCG Strategy Rigor

- **Issue Tree**: Break down problem into MECE branches.
- **One-Page Exec Summary**: BLUF + 3 insights + 3 decisions.

### B. Decision Engineering (`/decide`)

1.  **Frame**: What are we solving? Why now?
2.  **Options**: List at least 3 (including "Do Nothing").
3.  **Verdict**: Pick one. Justify via Trade-offs.
4.  **Log**: Append to `5. Trackers/DECISION_LOG.md`.

### C. Strategy Pulse (Signal Synthesis)

1.  **Collect**: In a SINGLE turn, sample recent entries from `bugs-master.md`, `TASK_MASTER.md`, and `DECISION_LOG.md`.
2.  **Cluster**: Group into 3–5 recurring themes (e.g., "Tech Debt", "Mobile Adoption").
3.  **Output**: Save to `1. Company/STRATEGY_PULSE.md`.

## 3. Output Rules

- **Decisions**: Use the "Decision Diamond" format (Context -> Options -> Verdict).
- **Pulse**: Use format:
  ```markdown
  ## Theme 1: [Name]

  - **Signal**: ...
  - **Impact**: High/Medium/Low
  ```
- **Roadmaps**: Group by **Horizon**, not dates.
- **Language**: No jargon ("synergy"). Data-backed confidence only.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…