Skill

checking-backlog

Checks project backlog in docs/features/DASHBOARD.md during discussions of feature ideas, priorities, or planned work. Shows matching features by status and suggests /feature-plan or /feature-capture.

developer-tools

npx claudepluginhub schuettc/claude-code-plugins --plugin feature-workflow

Tool Access

This skill is limited to using the following tools:

ReadGlob

Preview

Automatically check the project backlog when the user discusses feature ideas, priorities, or planned work.

SKILL.md

Similar Skills

feature-status

Displays project status dashboard from DASHBOARD.md, summarizing in-progress, backlog by priority, and completed features. Supports category filters and feature ID details. Use for status checks and backlog overviews.

1 tool

feature-workflow

backlog

Manages backlog items synced to GitHub Issues via MCP tools. Create, list, view, update, close, resolve, groom, and sync without direct file edits.

7 files

arn-spark-feature-extract

Extracts structured, prioritized feature backlog from project artifacts like product concepts, use cases, prototypes. Produces Feature Tracker document bridging to feature specs; optionally uploads to GitHub/Jira.

2 files

arn-spark

Stats

Parent Repo Stars11

Parent Repo Forks3

Last CommitMar 26, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Backlog Awareness

Automatically check the project backlog when the user discusses feature ideas, priorities, or planned work.

When to Use

Invoke this skill when the user:

Proposes new functionality: "We should add...", "It would be nice if...", "What if we..."
Asks about planned work: "What features are planned?", "Is X in the backlog?"
Discusses priorities: "What should we work on next?", "What's most important?"
Mentions a specific feature by name that might be tracked

Instructions

Step 1: Load Dashboard

Read docs/features/DASHBOARD.md to see all features by status.

If it doesn't exist: "No backlog found. Use /feature-capture to start tracking."

Step 2: Search for Matches

Parse the DASHBOARD.md tables to find:

Feature IDs and names in each section (In Progress, Backlog, Completed)
Priority and effort information

For deeper context on a specific feature, read its files:

docs/features/[id]/
├── idea.md      # Problem statement, priority, effort, impact
├── plan.md      # Implementation details (if in-progress)
└── shipped.md   # Completion notes (if completed)

Search idea.md for:

name in frontmatter (partial match, case-insensitive)
Problem statement content (keyword match)
affectedAreas (if user mentions specific areas)

Step 3: Respond Based on Results

Feature exists: Show status, priority, and category from DASHBOARD.md. Suggest /feature-plan [id] if in backlog.
Related items found: List them with their category, ask if user's idea is an extension or new feature.
Not tracked: Suggest /feature-capture to add it.

Example

User: "We should add dark mode support"

Response:

This feature is already tracked:

**Dark Mode Toggle** (ID: dark-mode-toggle)
- Status: backlog
- Priority: P1

Ready to start! Use `/feature-plan dark-mode-toggle`

Integration Notes

This skill works with:

/feature-capture - Suggest when idea isn't tracked
/feature-plan - Suggest when item is in backlog
/feature-status - For broader status queries