Review current plan status and recommend next action
8 stars
0 votes
0 copies
0 views
Added September 20, 2026
ai-agentsgobashgitdocumentation
Security analysis
A100/100
Scanned September 20, 2026
$npx -y skills add tstapler/dotfiles --skill status --agent claude-code
Installs into .claude/skills of the current project.
Are you the author of Status?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tstapler-status-dotfiles)
---
description: Review current plan status and recommend next action
---
# Project Plan Status Check
This command uses the `project-coordinator` agent to analyze current project state and recommend what to work on next.
## Agent Delegation
```
@task project-coordinator
Analyze current project status and recommend next action.
**Context**:
- Repository: [Automatically detected]
- Git Branch: [Current branch from git status]
- Uncommitted Changes: [Detect from git status]
**Analysis Tasks**:
1. **Scan Active Plans**:
- Check TODO.md in root directory
- Find all non-archived files in docs/tasks/
- Find all non-archived files in docs/projects/
- Scan docs/bugs/ directory for all bug documentation
- Review git status for uncommitted changes
2. **Analyze Current State**:
- Identify in-progress tasks (marked with π, "IN PROGRESS", or similar)
- Scan for open bugs and assess severity (Critical, High, Medium, Low)
- Review recently completed tasks (last 7 days from git log)
- Check for blocked tasks or dependency issues
- Identify bugs blocking planned work
- Assess overall project momentum
3. **Provide Status Report** with:
- **Overall Health**: [Healthy | At Risk | Blocked]
- **Active Tasks**: Count and list
- **Open Bugs**: Count by severity (Critical, High, Medium, Low)
- **Blockers**: Count and specific issues (tasks and bugs)
- **Recent Velocity**: [High | Medium | Low]
4. **Detail Each Category**:
- **In Progress**: Tasks with progress indicators and estimated remaining effort
- **Critical Bugs**: Immediate blockers requiring attention (if any)
- **High-Severity Bugs**: Important issues to prioritize (if any)
- **Blockers**: Specific reasons and what's needed to unblock (including bug dependencies)
- **Recently Completed**: Last 5 completed tasks with dates
- **Upcoming**: Next 3 prioritized tasks from TODO.md (may include bug fixes)
5. **Recommend Next Action** with:
- **Work Item**: Task or bug fix from TODO.md, task files, or bugs directory
- **Rationale**: Why this work now (priority, severity, dependencies, flow state, bug impact)
- **Estimated Time**: Time to completion (respect 1-4 hour context boundaries)
- **Prerequisites**: Any context needed before starting
- **Files to Load**: Specific files to understand before beginning (3-5 max)
**Expected Output Format**:
```markdown
## Project Status Summary
**Overall Health**: [Status]
**Active Tasks**: [Count]
**Open Bugs**: [Count by severity - Critical: N, High: N, Medium: N, Low: N]
**Blockers**: [Count - including both tasks and bugs]
**Recent Velocity**: [Assessment]
### In Progress ([N] tasks)
[Detailed list with progress and estimates]
### π Critical Bugs ([N] bugs)
[ONLY if critical bugs exist - list with impact and recommended action]
### π High-Severity Bugs ([N] bugs)
[ONLY if high-severity bugs exist - list with impact]
### Blockers ([N] items)
[List with reasons and unblocking requirements - include bug blockers]
### Recently Completed (last 7 days)
[Last 5 with completion dates - include fixed bugs]
### Upcoming (next 3 priorities)
[Prioritized list from TODO.md - may include bug fixes based on severity]
## π― Recommended Next Action
**Start**: [Task Name]
**Rationale**:
[Why this task now - priority, flow, dependencies]
**Estimated Time**: [Hours to completion]
**Prerequisites**:
[Context needed before starting]
**Files to Load Before Starting**:
1. [File with purpose]
2. [File with purpose]
...
**Next Steps**:
1. [Action item]
2. [Action item]
...
```
**Focus**: Eliminate decision paralysis by providing clear, actionable recommendation based on current project state, dependencies, and maintaining flow.
```
## Usage Tips
```bash
# Run at the start of each work session
/plan:status
```
The agent will:
- β Scan all active planning documents and bug tracking
- β Identify in-progress, blocked, and upcoming tasks
- β Surface critical and high-severity bugs prominently
- β Assess project momentum and bug impact
- β Recommend the single best next work item (task or bug fix)
- β Provide bug-aware prioritization and rationale
- β Provide clear rationale and prerequisites
This eliminates decision paralysis, surfaces critical issues, and helps maintain flow state throughout your work session.
## When to Use
- **Start of work session** - "What should I work on?"
- **After completing a task** - "What's next?"
- **When feeling stuck** - "Am I blocked or just uncertain?"
- **Before context switching** - "Should I finish this or pivot?"