next-ticket

Select and implement the highest-value open ticket from project issue trackers.

3|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/AdamCaviness/agentic-toolkit --skill next-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-ticket
Source: https://github.com/AdamCaviness/agentic-toolkit/tree/main/skills/next-ticket
Command: npx skills add https://github.com/AdamCaviness/agentic-toolkit --skill next-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Next Ticket skill automates selecting the highest-value open ticket from a project's issue tracker, then implements it end-to-end and waits for review to ensure quality before pushing.

Core Features & Use Cases

  • Detects the project's ticket system (GitHub Issues, Jira, GitLab Issues, Azure Boards, etc.) and fetches open tickets.
  • Scores tickets by severity, simplicity, blocking power, and value to identify the best candidate.
  • Creates a branch, implements the ticket end-to-end, writes and runs tests (TDD), formats code, and prepares for review.

Quick Start

Run /next-ticket to start selecting and implementing the top-ticket end-to-end.

Frequently Asked Questions about next-ticket

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

FAQPage Schema
How do I automatically select and implement the highest-value open ticket from an issue tracker?

Automated ticket implementation fetches all open tickets from trackers like GitHub Issues or Jira, scores them by severity, blocking power, and value, then branches and implements the top candidate end-to-end.

What is the best way to automate TDD workflow when picking up new issue tracker tickets?

Automating TDD for issue tracker tickets involves creating a branch, writing failing tests first, iteratively implementing code until tests pass, formatting, and finally awaiting review.

Does automated ticket implementation work with multiple issue tracking platforms like Jira and GitLab Issues?

Automated ticket implementation detects and works with GitHub Issues, Jira, GitLab Issues, and Azure Boards, fetching open tickets and scoring them across platforms.

How are open tickets scored and prioritized for automated end-to-end implementation?

Tickets are scored by severity, simplicity, blocking power, and value to identify the highest-value candidate, ensuring the most impactful issue is implemented first.

What steps are involved in the end-to-end automated ticket implementation workflow?

The workflow includes detecting the tracker, caching configuration, branch creation, writing failing tests first, iterative implementation until green, formatting, and entering a review-wait state.

Can I use automated ticket implementation for AFK development workflows?

Automated ticket implementation supports AFK workflows by selecting, implementing, testing, and awaiting review without manual intervention, streamlining development.