next-backlog-issue

Selects the next unblocked backlog issue and coordinates its delivery through human approval gates.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/urban233/ntn-ingest --skill next-backlog-issue-urban233
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: next-backlog-issue
Source: https://github.com/urban233/ntn-ingest/tree/main/.agents/skills/next-backlog-issue
Command: npx skills add https://github.com/urban233/ntn-ingest --skill next-backlog-issue-urban233

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams maintaining a structured backlog of issues need a disciplined way to pick the next eligible item and drive it through specification, implementation, and completion without skipping required human approvals. This Skill enforces that end-to-end delivery workflow so no gate is bypassed. ## Core Features & Use Cases - Dependency-aware issue selection: Filters backlog issues by frontmatter status and depends-on completion, then ranks candidates using the tier or wave order in backlog/overview.md. - Specification-first delivery: Delegates implementation-spec creation to the feature-spec-creator skill and requires explicit human approval of the spec before any code is written. - Approval-gated completion: Records human sign-off at each stage (issue start, spec, code, architecture records) before marking the issue completed and archiving the spec under specs/completed/. - Use Case: A maintainer asks which backlog issue to tackle next; the Skill reads the backlog ledger, proposes the highest-priority unblocked issue with dependency evidence, and walks the human through spec approval, implementation, verification, and archival. ## Quick Start Ask the assistant to start the next backlog issue end-to-end and it will select an eligible issue and guide you through each approval gate.

Frequently Asked Questions about next-backlog-issue

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

FAQPage Schema
How do I pick the next backlog issue to work on?▼

The Skill scans every issue's frontmatter, keeps only those with status `planned` whose `depends-on` entries are all `completed`, and ranks them by the tier or wave order in `backlog/overview.md`. It then reports the selection with dependency evidence and waits for your approval before starting.

How does the AI-driven issue delivery workflow enforce human approval?▼

It defines explicit gates: approving the issue start, the final implementation specification, the generated code after verification, and any architecture documentation changes. Passing tests count as evidence only and never substitute for human acceptance.

Can it resume an issue that is already in progress?▼

In-progress issues are excluded from automatic selection. The Skill resumes an `in_progress` issue only when the user explicitly asks to resume that specific issue.

What happens when no backlog issue is eligible to start?▼

It reports whether all issues are completed or identifies the exact outstanding dependencies and blockers preventing eligibility. It does not bypass blockers or start a blocked issue.

Does the workflow commit code or create pull requests automatically?▼

No. It never stages, commits, pushes, opens pull requests, or performs external actions unless the human explicitly requests that action. Completed specs are moved to `specs/completed/` and never deleted.