Installs just this skill. Get the whole plugin for auto-invocation.
⚡ How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/skill-status
👁️ Context preview
The summary Claude sees to decide when to auto-load this skill.
Show where you are in the workflow and what to do next — use for progress checks and orientation
📊 Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
📦 Ships with octo
</> SKILL.md
skill-status.SKILL.md
---name: skill-status
effort: low
user-invocable: true
description: "Show where you are in the workflow and what to do next — use for progress checks and orientation"
trigger: |
AUTOMATICALLY ACTIVATE when user asks about:
- "status" or "progress" or "where am I"
- "what's next" or "next step"
- "show status" or "project status"
- "what have I been working on" or "summarize recent work"
- "update project memory" or "update CLAUDE.md"
---# Project Status Dashboard
## Overview
Display current project status, roadmap progress, blockers, and intelligent next-action suggestions based on workflow state.
**Core principle:** Read state → Display dashboard → Route intelligently.
---## When to Use
**Use this skill when user asks:**
- "What's the status?" or "Show me progress"
- "Where am I in the workflow?"
- "What should I do next?"
- "What's the current phase?"
- "Are there any blockers?"
- "What have I been working on?" or "Summarize recent work"
- "Update project memory" or "Update CLAUDE.md"
If the recent activity reveals patterns not captured in `CLAUDE.md`, suggest specific additions:
```markdown
### Suggested CLAUDE.md Updates
Based on recent activity, consider adding:
- [specific suggestion based on new patterns, conventions, or decisions]
- [specific suggestion based on new tooling or workflow changes]
```
**Only suggest updates that reflect durable project knowledge** (conventions, architecture decisions, provider configs) — NOT transient status like "currently working on X".
---
## Integration with Other Skills
### With flow-* skills
```
User asks "what's next?"
→ skill-status shows current phase
→ User runs /octo:develop to continue
```
### With skill-task-management
```
User asks "show status"
→ skill-status displays dashboard
→ skill-task-management shows active todos
```
### With /octo:embrace
```
User asks "status" but no .octo/ exists
→ skill-status suggests /octo:embrace
→ User initializes new project
```
---
## Best Practices
### 1. Always Check for .octo/ First
**Good:**
```bash
if [[ ! -d ".octo" ]]; then
echo "Not initialized"
exit 1
fi
```
**Poor:**
```bash
# Assume .octo/ exists and fail later
cat .octo/STATE.md
```
### 2. Use octo-state.sh for State Reading
**Good:**
```bash
./scripts/octo-state.sh read_state
```
**Poor:**
```bash
# Parse STATE.md manually
grep "Current Phase" .octo/STATE.md
```
### 3. Provide Actionable Next Steps
**Good:**
```
Continue with `/octo:develop` to implement features.
Check `.octo/phases/phase3/` for implementation plan.
```
**Poor:**
```
You're in phase 3.
```
---
## Red Flags - Don't Do This
| Action | Why It's Wrong |
|--------|----------------|
| Modify STATE.md directly | Use octo-state.sh write_state instead |
| Skip .octo/ existence check | Will fail with confusing errors |
| Show status without next action | User doesn't know what to do |
| Hardcode phase names | Read from ROADMAP.md for accuracy |
| Ignore blockers | User needs to know what's blocking progress |
