Check project backlog when discussing feature ideas or priorities. Use when user mentions adding features, asks what's planned, discusses priorities, or proposes new functionality. Silently reads backlog.json to show relevant items and suggest /feature-capture for untracked ideas.
/plugin marketplace add schuettc/claude-code-plugins/plugin install feature-workflow@schuettc-claude-code-pluginsThis skill is limited to using the following tools:
Automatically check the project backlog when the user discusses feature ideas, priorities, or planned work.
Invoke this skill when the user:
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 itemsCombine all items arrays to search across all statuses.
If no files exist: "No backlog found. Use /feature-capture to start tracking."
Search items for:
name (partial match, case-insensitive)problemStatement (keyword match)affectedAreas (if user mentions specific areas)dependsOn / blockedBy (if discussing dependencies)/feature-plan [id] if ready./feature-capture to add it.Include dependency status (blocked/ready) when relevant.
User: "We should add dark mode support"
Response:
This feature is already tracked:
**Dark Mode Toggle** (ID: dark-mode-toggle)
- Status: backlog
- Priority: P1
- Dependencies: None
Ready to start! Use `/feature-plan dark-mode-toggle`
This skill works with:
/feature-capture - Suggest when idea isn't tracked/feature-plan - Suggest when item is ready to startdisplaying-status skill - For broader status queriesBuild 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.