Planification Stratégique

VérifiéPrudence

Partenaire de réflexion stratégique qui analyse la progression du travail, identifie les blocages et planifie les prochaines étapes. Idéal pour coordonner entre cycles de travail et anticiper les dépendances.

Spar Skills Guide Bot
ProductiviteIntermédiaire
4002/06/2026
Claude CodeCursorWindsurfCopilotCodex
#strategic-planning#progress-analysis#workflow-management#dependency-mapping

Recommandé pour

Notre avis

Analyse l'état actuel du travail et l'avancement du projet pour aider à planifier la prochaine phase de développement.

Points forts

  • Offre une vision stratégique entre les cycles de travail
  • Détecte rapidement les dépendances et obstacles
  • Aide à prioriser les tâches logiquement
  • Aligne l'exécution avec les objectifs à long terme

Limites

  • Nécessite un contexte de projet bien défini pour être efficace
  • Peut ne pas détecter tous les problèmes subtils
  • Dépend de l'état précis de git et de l'historique des commits
Quand l'utiliser

À utiliser entre les cycles de développement ou lors de pauses stratégiques pour planifier les prochaines étapes et identifier les obstacles potentiels.

Quand l'éviter

Ne pas utiliser si l'état actuel du travail n'est pas encore validé ou si vous avez besoin de codage immédiat.

Analyse de sécurité

Prudence
Score qualité90/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.

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

Exemples

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
Skills similaires