compass_skill
- Shell
8
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill simota/agent-skills --skill compass- SKILL.md7.8 KB
Overview
This skill monitors strategy execution by tracking a Helm roadmap, its underlying assumptions, and actual KPIs to detect strategic drift early. I map assumptions to measurable metrics, cascade strategy into aligned OKRs, and produce concise Strategy Health Reports with clear alerts and routing recommendations. I do not write code or make final pivot decisions—I surface the evidence and who should act.
How this skill works
I ingest a Helm roadmap and assumption set, then link each assumption to specific KPIs and thresholds. I continuously compare KPI actuals and milestone progress against targets, compute a weighted Drift Score, and evaluate assumption states (VALID → WATCH → BREACH). When thresholds are crossed I emit Green/Yellow/Red/Black alerts with explicit routing (Sherpa/Helm/Magi) and recommended actions. I also decompose strategic objectives into Company and Team OKRs and score alignment.
When to use it
- You need continuous monitoring of a published strategy roadmap and assumptions
- You want early detection of strategic drift or simultaneous assumption breaches
- You must cascade strategy into aligned Company and Team OKRs with an alignment score
- You need structured, actionable Strategy Health Reports for execs and operators
- You require routing recommendations for who should act on alerts
Best practices
- Always link every tracked metric to a Helm strategic objective or named assumption
- Define leading and lagging indicators and set clear VALID/WATCH/BREACH thresholds before monitoring starts
- Configure monitoring frequency and milestone cadence in the ANCHOR phase
- Treat alerts as decision prompts: each must state who acts, what to change, and the required decision
- Validate OKR alignment score before cascading and resolve OKR conflicts via ON_OKR_CONFLICT trigger
Example use cases
- Enterprise product leadership monitoring quarter-by-quarter roadmap execution and market signals
- Startups tracking core growth assumptions (acquisition, retention) to detect early breaches and request pivots
- SaaS companies cascading top-level strategic goals into team OKRs and measuring alignment
- Operational teams receiving Yellow alerts routed to Sherpa for execution adjustments
- Executive summaries for board reviews showing Drift Score, top breached assumptions, and required handoffs
FAQ
No. Compass monitors, alerts, and recommends who should act. Strategy formulation stays with Helm and implementation remains with Sherpa or engineering teams.
How are alert levels determined and routed?
Alert levels derive from KPI deviation, assumption state, and milestone delay. Green/Yellow/Red/Black map to no action, Sherpa, Helm, and Magi respectively, with explicit routing in every alert.
Can Compass create OKRs automatically?
I decompose strategy into Company and Team OKRs and compute an Alignment Score, but I verify conflicts and ask before finalizing cascaded OKRs via ON_OKR_CONFLICT.
