next-issues

List ARCHON project issues by status from GitHub Projects or repository.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zorgentech/archon --skill next-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-issues
Source: https://github.com/zorgentech/archon/tree/main/.claude/skills/next-issues
Command: npx skills add https://github.com/zorgentech/archon --skill next-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a quick, reliable way to surface the next actionable issues for the ARCHON project by pulling items from the GitHub Projects board or falling back to repository issues when the board has no results, removing manual searching across boards and issue lists.

Core Features & Use Cases

  • Board-first listing with fallback: Fetch issues by status from the GitHub Projects board and fall back to open repository issues if the board returns nothing.
  • Filtered views for planning: Support filters like ready, backlog, in-progress, review, open, and all to help sprint planning, backlog grooming, and triage.
  • Prioritization and summaries: Group and order results by priority labels (P0..P3), show totals and story points, and indicate whether results came from the board or the repo.

Quick Start

Ask the skill to list issues with an optional status filter (for example: ready) and it will fetch from the project board or fallback to the repository.

Frequently Asked Questions about next-issues

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

FAQPage Schema
How do I list GitHub issues ready for implementation from a project board?

You can list GitHub issues ready for implementation by fetching items from the GitHub Projects board using status filters. If the board returns no issues, it automatically falls back to listing open issues from the repository.

Can I filter GitHub backlog issues by priority for sprint planning?

Yes, you can filter GitHub backlog issues by status using filters like ready, backlog, in-progress, and review. Results are grouped and ordered by priority labels from P0 to P3 to facilitate sprint planning.

Do I need the gh CLI to fetch issues from the GitHub Projects board?

Yes, you need an authenticated gh CLI to fetch issues from the GitHub Projects board. The skill requires valid GitHub authentication to query project boards and fall back to repository issues.

What happens when the GitHub Projects board returns no issues for triage?

When the GitHub Projects board returns no issues during triage, the skill automatically falls back to retrieving open issues directly from the repository, ensuring you always receive actionable items.

How does triaging open issues group results by story points and totals?

Triaging open issues groups results by priority labels and displays story point totals. It also indicates whether the results were sourced from the project board or the repository fallback.

What is the best way to review in-progress issues across a GitHub repository?

The best way to review in-progress issues is applying the in-progress status filter to pull items directly from the GitHub Projects board. This surfaces current work items grouped by priority for quick review.