MSPOT Generator

Create one-page strategic alignment documents. Mission, Strategy, Projects, Omissions, Tracking. Forces clarity on what you WILL and WON'T do. Use when user says "mspot", "strategic plan", "quarterly plan", "what are we NOT doing", "omissions", "team alignment", "OKRs alternative", "priorities", "what should we focus on".

Security Scan

The skill is an instruction-only template for producing MSPOT one‑page strategy documents and its requested files/env/install footprint matches that purpose.

Purpose & Capability

Name and description match the provided SKILL.md: the skill supplies templates, questions, and examples to produce MSPOT documents. There are no unrelated binaries, environment variables, or config paths requested.

Instruction Scope

Runtime instructions are limited to formatting strategy output and asking planning questions. They do not instruct the agent to read local files, access system credentials, or contact external endpoints. The 'Integration' section only references complementary skills and does not require additional secrets or system access.

Install Mechanism

No install spec or code files that would write or execute code on disk. As an instruction-only skill it has minimal installation risk.

Credentials

The skill declares no required environment variables, credentials, or config paths — appropriate for a template/formatter tool.

Persistence & Privilege

Flags show default behavior (not always:true, user-invocable allowed). The skill does not request permanent presence or system-level changes.

Assessment

This skill appears internally consistent and low-risk: it only provides templates and examples for crafting MSPOT one-page strategy documents and requests no credentials or installs. Before installing, consider: (1) any sensitive business info you paste into the skill will be part of the agent interaction and may be retained in platform logs — avoid pasting secrets; (2) if you later combine this skill with other skills that do have network access or credentials, review those skills separately; and (3) if you want to be extra careful, preview outputs in a private workspace before sharing broadly. Overall, it is appropriate to install if you want a guided MSPOT template.

What is MSPOT?

One-page strategic clarity (from HubSpot):

• Mission: Why we exist (rarely changes)
• Strategy: How we'll win this period
• Projects: The 3-5 big bets
• Omissions: What we're explicitly NOT doing
• Tracking: How we'll measure success

Why It Works

1. Forces Omissions: Saying NO is harder and more valuable
2. Limits Projects: 3-5 max prevents spreading thin
3. One Page: If it doesn't fit, it's not clear
4. Trackable: Decision-useful metrics only

Output Format

═══════════════════════════════════════════════
MSPOT: [Name]
Period: [Timeframe] | Owner: [Person]
═══════════════════════════════════════════════

MISSION: [One sentence: Why this exists]

STRATEGY: [2-3 sentences: How we'll win]

PROJECTS (3-5 max):
1. [Name] - Outcome: [X] - Owner: [Y] - Due: [Z]
2. [Name] - Outcome: [X] - Owner: [Y] - Due: [Z]
3. [Name] - Outcome: [X] - Owner: [Y] - Due: [Z]

OMISSIONS:
✗ NOT [X] - Because: [reason]
✗ NOT [Y] - Because: [reason]

TRACKING:
Lead: [Activity] → Target: [X]
Lag: [Result] → Target: [Y] by [date]
═══════════════════════════════════════════════

Key Questions

Section	Question
Mission	"If we succeed, what changes?"
Strategy	"What's our unfair advantage?"
Projects	"If only 3 things, which ones?"
Omissions	"What are we tempted to do but shouldn't?"
Tracking	"What number tells us we're winning?"

Integration

Compounds with:

• pre-mortem-analyst → Pre-mortem each Project before committing
• inversion-strategist → Invert to find Omissions
• artem-decision-journal → Log major MSPOT decisions

---

See references/examples.md for TeddySnaps/TISA/GolfTab MSPOTs