Our review
Analyzes the current work state and progress to provide strategic recommendations for the next phase of development.
Strengths
- Keeps the human in the loop for strategic decisions
- Identifies blockers and dependencies early
- Provides structured output for easy review
Limitations
- Requires git history to analyze progress
- May not capture external context beyond code changes
- Relies on clear commit messages for accurate trajectory
Use between work cycles to validate progress and plan the next feature or fix.
Avoid when immediate execution is needed and no strategic pause is beneficial.
Security analysis
SafeThe skill is read-only, only invoking git status, diff, and log to analyze the current state of a repository. It does not perform destructive, exfiltrating, or obfuscated actions, and does not use network tools or disable safety mechanisms.
No concerns found
Examples
think aheadthink ahead to plan the next stepname: 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:
- Read current state -
git status,git diff, last 10 commits - Check plan alignment - What was TODO, what actually got built
- Analyze trajectory - See patterns in commits and progress
- Flag blockers - External setup, missing credentials, test failures
- 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
Task Prioritizer
Productivity
Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.
Weekly Status Report Generator
Productivity
Generate structured and concise weekly status reports.
Daily Standup Report
Productivity
Generates structured and concise daily standup reports.