next-item

Retrieve GitHub backlog items filtered by Ready status and sorted by Priority P0-P3.

6|Updated Oct 7, 2025
One-click install
npx skills add https://github.com/rjroy/vibe-garden --skill next-item
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-item
Source: https://github.com/rjroy/vibe-garden/tree/main/compass-rose/skills/next-item
Command: npx skills add https://github.com/rjroy/vibe-garden --skill next-item

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams determine the next logical piece of work by identifying the highest-priority, ready backlog item and presenting rationale to guide execution.

Core Features & Use Cases

  • Retrieve items from the GitHub project backlog via the compass-rose gh-api-scripts integration.
  • Filter to Ready status items and sort by Priority (P0 > P1 > P2 > P3), then surface top 2-3 options.
  • Provide concise rationale and note codebase relevance as a tiebreaker when priorities are equal.
  • Graceful degradation when Priority field is missing; treat all items as equal priority and rely on creation date.

Quick Start

Run the next-item recommendation to fetch the backlog, filter for Ready items, and display the top 2-3 options with rationale.

Frequently Asked Questions about next-item

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the highest-priority ready backlog item in a GitHub project?

To find the highest-priority ready backlog item, query your GitHub project via compass-rose gh-api-scripts, filter items by Ready status, and sort by Priority (P0 > P1 > P2 > P3) to surface the top options.

How does priority sorting handle tie-breakers for backlog items?

Priority sorting handles tie-breakers by using codebase signals as a secondary ranking factor when priorities are equal, ensuring the most relevant backlog item is selected for execution.

What happens if a GitHub project backlog item is missing the Priority field?

If a GitHub project backlog item is missing the Priority field, the system gracefully degrades by treating all items as equal priority and relying on creation date to determine the next item to work on.

Can I use compass-rose gh-api-scripts to filter project backlog by Ready status?

Yes, you can use compass-rose gh-api-scripts to query the GitHub project backlog and filter specifically for items marked with Ready status before sorting them by priority level.

How are the top backlog options presented for execution?

The top 2-3 ready backlog options are presented with concise rationale explaining why each item is recommended, including codebase relevance notes when used as a priority tie-breaker.