skills.rest
nand1234
nand1234COMMUNITY
Explore all skills by this author →
GitHub

next-ticket

Evaluate dependency readiness to identify next actionable tickets for a feature.

Updated Mar 6, 2026
Search Tags:#workflow#planning#engineering#status#dependency#next-ticket
One-click install
npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill next-ticket-nand1234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: next-ticket
Source: https://github.com/nand1234/Agentic-workflow-builder/tree/main/ai-dev-worflow/.claude/skills/next-ticket
Command: npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill next-ticket-nand1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams prioritize work by surfacing tickets that are ready to implement based on dependency statuses.

Core Features & Use Cases

  • Readiness evaluation: classifies tickets as READY, BLOCKED, IN PROGRESS, DONE, or MERGED to CP based on dependency relationships.
  • Progress visibility: provides a concise status report per feature, highlighting blockers and upcoming work.
  • RTM alignment: checks requirement-to-merge coverage and points to relevant docs to align the feature before merge.

Quick Start

Provide a feature slug to see the next actionable tickets and their current statuses.

Frequently Asked Questions about next-ticket

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

FAQPage Schema
How do I identify ready-to-implement tickets based on dependency status?▼

To identify ready tickets based on dependency status, evaluate dependency readiness to surface actionable work. Tickets are marked READY only when all dependencies are merged to CP, enabling engineers to prioritize implementation effectively.

What is the best way to track blocked tickets during sprint orchestration?▼

Tracking blocked tickets during sprint orchestration requires evaluating dependency relationships. A ticket is classified as BLOCKED when any dependency is not merged, providing a structured summary that highlights blockers and guides resolution.

How does dependency readiness evaluation classify ticket statuses?▼

Dependency readiness evaluation classifies ticket statuses by checking merge states. It assigns statuses like READY, BLOCKED, IN PROGRESS, DONE, or MERGED to CP based on whether all linked dependencies are successfully merged to CP.

Can I check requirement-to-merge coverage before finalizing a feature?▼

Yes, you can check requirement-to-merge coverage before finalizing a feature. The readiness evaluation checks RTM alignment and points to relevant docs to ensure the feature aligns with requirements before merge.

Do I need a feature slug to surface actionable tickets for sprint planning?▼

Yes, you need to provide a feature slug to surface actionable tickets. Supplying the feature slug allows the system to evaluate dependencies and generate a concise status report highlighting upcoming work and blockers.

Related Skills

Explore More Software Engineering Skills→
yzhao062yzhao062
13

nsf-proposal-guardrail

Ingest NSF solicitation text into a normalized requirements baseline.

Community
Advanced
r3d3y3s79r3d3y3s79

status-report-generator

Generate structured project status reports for weekly, executive, client, and sprint audiences.

Community
Intermediate
AlphaLab-USTCAlphaLab-USTC
131

requesting-code-review

Request code reviews for git commit ranges before merge.

Community
Intermediate
DethonDethon
3

implement-swarm

Automates task graph creation and execution with parallel workers and dependency tracking.

Community
Advanced