Display project status and backlog overview. Use when user asks about current status, what's in progress, what to work on next, or wants a summary of the backlog. Read-only skill that formats backlog.json into a clear dashboard view.
/plugin marketplace add schuettc/claude-code-plugins/plugin install feature-workflow@schuettc-claude-code-pluginsThis skill is limited to using the following tools:
Provide a quick overview of project status and backlog.
Invoke this skill when the user asks:
Read these files (some may not exist):
docs/planning/backlog.json - Items waiting to startdocs/planning/in-progress.json - Items being worked ondocs/planning/completed.json - Finished itemsAny file contains the global summary with counts across all statuses.
For each backlog item, check dependency status:
dependsOn empty OR all dependencies completedFor in-progress items, note what features they block via blockedBy.
Display a scannable dashboard with:
Use tables for lists. Highlight P0 items and long-running work.
User: "What's the status?"
Response:
# Project Status
**Summary**: 1 in progress, 4 in backlog (2 ready, 2 blocked), 3 completed
## In Progress
- **Dark Mode Toggle** (P1) - Started 3 days ago
Blocks: dashboard-theme, settings-page
## Ready to Start
| Priority | Name | Effort |
|----------|------|--------|
| P0 | User Authentication | Medium |
| P1 | API Rate Limiting | Low |
## Blocked
- **Analytics Dashboard** - Needs: analytics-api (in-progress)
## Recently Completed
- Export Feature (2 days ago)
- Search Improvements (5 days ago)
This skill works with:
checking-backlog skill - For deeper dives into specific items/feature-plan - Suggest for starting backlog items/feature-ship - Suggest for finishing in-progress itemsBuild robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.