Strategic Planning Partner

VerifiedCaution

Strategic thinking partner that analyzes work progress, identifies blockers, and plans next steps. Perfect for coordinating between work cycles and anticipating dependencies.

Sby Skills Guide Bot
ProductivityIntermediate
506/2/2026
Claude CodeCursorWindsurfCopilotCodex
#strategic-planning#progress-analysis#workflow-management#dependency-mapping

Recommended for

Our review

Analyzes the current work state and project progress to help plan the next development phase.

Strengths

  • Provides strategic oversight between work cycles
  • Spots dependencies and blockers early
  • Helps prioritize tasks logically
  • Aligns execution with long-term goals

Limitations

  • Requires a well-defined project context to be effective
  • May not catch all subtle issues
  • Relies on accurate git state and commit history
When to use it

Use between development cycles or strategic pauses to plan the next steps and identify potential blockers.

When not to use it

Do not use if the current work state is not yet committed or if you need immediate hands-on coding.

Security analysis

Caution
Quality score90/100

The skill instructs the AI to run git commands to analyze the repository, which involves bash execution. While the commands are read-only and low-risk, they still fall under 'powerful tools used for legitimate purposes'. No destructive or exfiltrating actions are present.

Findings
  • Implicitly executes git commands (git status, git diff, git log) to read repository state without declaring allowed-tools.

Examples

Plan next feature after completion
Think ahead - I just finished the user authentication module. What should we tackle next?
Strategic review of current state
Think ahead - please review the current state of the project, including git status and recent commits, and suggest the next steps.
Blocking detection and dependency mapping
Think ahead - are there any blockers or dependencies I should be aware of before moving forward with the feature build?

name: think-ahead description: AI thinking partner for strategy and planning. Reads the current work state, analyzes progress, and helps you plan the next phase while the worker instance builds. Triggered by "think ahead".

Think Ahead

Your strategic planning partner. While the worker instance executes, you stay one step ahead—understanding what's been built, spotting opportunities, and planning the next moves.

The Role

You're the thinking partner ↔ They're the working partner

This skill reads their progress and helps you:

  • Understand what just shipped
  • Spot dependencies and blockers
  • Plan the next feature thoughtfully
  • Coordinate between tasks
  • Anticipate problems before they happen

When To Use

Say: "think ahead"

Perfect for:

  • Between work cycles - Worker finishes a task, you plan the next one
  • Strategic pauses - Before committing to a direction, validate the approach
  • Blocking detection - Spot if work is waiting on external setup (Google Cloud, credentials, etc.)
  • Dependency mapping - See what needs what, plan build order
  • Opportunity spotting - Notice refactoring chances or improvements
  • Coordination - When multiple features are in flight, stay synchronized

What This Delivers

I'll:

  1. Read current state - git status, git diff, last 10 commits
  2. Check plan alignment - What was TODO, what actually got built
  3. Analyze trajectory - See patterns in commits and progress
  4. Flag blockers - External setup, missing credentials, test failures
  5. Suggest next moves - What logically comes next, in priority order

Then present it as:

### Current State
Branch, staged changes, unstaged work

### What Just Shipped
Staged changes ready to commit
Tests, screenshots, infrastructure

### What's In Progress
Unstaged changes still being polished
Incomplete work that needs finishing

### The Arc
Recent commits showing the direction
How pieces fit together
What the pattern suggests

### Strategic Recommendations
Priority 1: What must happen next
Priority 2: What depends on that
Priority 3: What's blocked and why
What should the worker tackle next?

The Workflow

Worker builds → You think ahead → Plan next task → Worker executes
     ↓
   Repeat

Think of it like:

  • Worker = Getting things done, implementing features
  • You = Understanding the landscape, planning strategically
  • This skill = Bridging the gap, keeping strategy and execution aligned
Related skills