next

Suggest next Kanban work items using priority and dependency resolution.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/ramontramontini/CTEDemo --skill next-ramontramontini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next
Source: https://github.com/ramontramontini/CTEDemo/tree/main/.claude/skills/next
Command: npx skills add https://github.com/ramontramontini/CTEDemo --skill next-ramontramontini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams decide what to work on next by prioritizing stories based on Kanban policies and dependency resolution, reducing decision fatigue and delays.

Core Features & Use Cases

  • Priority-aware suggestions: Pulls in-progress and claimed work checks to honor Kanban flow and prompts for user decision.
  • Dependency-respecting queue: Retrieves ready-to-pull stories with dependencies already resolved, or falls back to plain ready_to_pull results with a warning.
  • Deterministic presentation: Builds a Policy 5 table sorted by priority, type, and FIFO for clear, actionable options.

Quick Start

Fetch the next set of stories from the hub and present the top candidates for action.

Frequently Asked Questions about next

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

FAQPage Schema
How do I decide which Kanban task to work on next?

To decide your next Kanban task, this Skill retrieves in-progress, claimed, and ready_to_pull stories, resolves dependencies, and presents a priority-sorted table to eliminate manual queue analysis.

How does dependency resolution work for ready-to-pull queues?

Dependency resolution filters ready_to_pull stories to include only those with resolved dependencies. If none are found, it falls back to standard ready_to_pull results and issues a warning.

How are prioritized work items presented for user selection?

Prioritized work items are presented as a deterministic Policy 5 table, strictly sorted by priority, story type, and FIFO ordering to ensure clear and actionable next-step options.

Can I use this for Kanban prioritization if I have in-progress and claimed tasks?

Yes, this Skill checks in_progress and claimed work to honor Kanban flow constraints before prompting you to pull new stories, ensuring continuous workflow without context switching.

What happens when dependencies are not resolved for my next work items?

When dependencies are unresolved, the queue retrieval falls back to plain ready_to_pull results with a warning, allowing you to proceed while acknowledging the dependency constraints.