Strategic Planning Skill

A Claude Code skill for structured strategic analysis, decision-making frameworks, and project planning that helps you think through complex technical and business decisions methodically.

When to Use This Skill

Choose this skill when:

• Evaluating multiple technical approaches for a new feature
• Planning a large-scale migration or refactoring effort
• Making build-vs-buy decisions for infrastructure components
• Conducting architectural reviews or design critiques
• Prioritizing a backlog of features or technical debt items
• Preparing technical proposals or RFCs for stakeholder review

Consider alternatives when:

• You need to write actual code (use a coding skill instead)
• You need project management tooling (use Jira, Linear, or similar)
• You need real-time collaboration (use a whiteboard or design tool)

Quick Start

Copy
# Add to your Claude Code project
claude mcp add strategic-planning

# Run a strategic analysis
claude "analyze the trade-offs between microservices and monolith for our payment system"

Copy
# .claude/skills/strategic-planning.yml
name: strategic-planning
description: Structured strategic analysis and decision frameworks
triggers:
  - "strategic analysis"
  - "trade-off analysis"
  - "decision framework"
config:
  framework: auto
  output_format: markdown
  include_risks: true

Core Concepts

Decision Frameworks

Framework	Best For	Output
SWOT Analysis	Evaluating a single option	Strengths, weaknesses, opportunities, threats matrix
Decision Matrix	Comparing multiple options	Weighted scoring table with rankings
RICE Scoring	Feature prioritization	Reach, Impact, Confidence, Effort scores
Six Thinking Hats	Group decision exploration	Perspectives from facts, emotions, risks, benefits, creativity, process
Pre-mortem	Risk identification	List of failure modes and mitigations
Opportunity Cost	Resource allocation	Comparison of what you gain vs. what you give up

Strategic Analysis Example

Copy
## Decision: Database Selection for Real-Time Analytics

### Options Evaluated
1. PostgreSQL with TimescaleDB extension
2. ClickHouse dedicated OLAP database
3. Apache Druid distributed analytics store

### Decision Matrix (1-5 scale, weighted)

| Criteria (Weight) | TimescaleDB | ClickHouse | Druid |
|-------------------|-------------|------------|-------|
| Query Speed (0.3) | 3 (0.9)     | 5 (1.5)    | 4 (1.2) |
| Ops Complexity (0.25) | 5 (1.25) | 3 (0.75)  | 2 (0.5) |
| Team Familiarity (0.2) | 5 (1.0) | 2 (0.4)   | 1 (0.2) |
| Scalability (0.15) | 3 (0.45)  | 5 (0.75)   | 5 (0.75) |
| Cost (0.1) | 4 (0.4)          | 3 (0.3)    | 2 (0.2) |
| **Total** | **4.0**           | **3.7**    | **2.85** |

### Recommendation: TimescaleDB
Highest overall score driven by operational simplicity and
team familiarity. Acceptable query performance for current scale.

Configuration

Parameter	Type	Default	Description
framework	string	"auto"	Analysis framework: auto, swot, decision_matrix, rice, premortem
output_format	string	"markdown"	Output format: markdown, json, table
include_risks	boolean	true	Include risk analysis section in output
include_timeline	boolean	false	Add implementation timeline estimates
stakeholders	array	[]	List of stakeholder perspectives to consider
constraints	array	[]	Known constraints (budget, timeline, team size)
depth	string	"standard"	Analysis depth: quick, standard, comprehensive

Best Practices

1. Define success criteria before analyzing options — without clear criteria and weights, any analysis becomes subjective; agree on what matters most before comparing alternatives.

2. Include at least one unconventional option — the best decision often comes from considering an option nobody initially suggested, such as a hybrid approach or a completely different framing.

3. Quantify trade-offs wherever possible — "faster" is vague, "3x faster queries at 2x storage cost" is actionable; attach numbers to claims so stakeholders can make informed decisions.

4. Document the decision context, not just the outcome — record why you chose option A at this point in time, so future teams can re-evaluate when constraints change.

5. Revisit strategic decisions on a schedule — set a calendar reminder to review major decisions quarterly; what was the right call six months ago may not be optimal today.

Common Issues

Analysis paralysis from too many frameworks — When the skill suggests multiple frameworks for a single decision, pick one and commit. The value is in structured thinking, not in running every possible framework on every decision.

Stakeholder disagreement on criteria weights — If team members cannot agree on how to weight decision criteria, run the analysis with each person's weights separately. Often the same option wins regardless, which builds consensus naturally.

Overly optimistic risk assessments — Strategic plans tend to underestimate risks. Counter this by explicitly asking "what would make this fail?" and requiring at least three concrete failure scenarios for any major decision.