next

Automate next-issue selection and dispatch from the lucOS prioritization board.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/lucas42/lucos_claude_config --skill next-lucas42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next
Source: https://github.com/lucas42/lucos_claude_config/tree/main/skills/next
Command: npx skills add https://github.com/lucas42/lucos_claude_config --skill next-lucas42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end workflow of selecting and starting the next actionable issue from the lucOS prioritization board, reducing manual triage time and delays.

Core Features & Use Cases

  • Automates next-issue selection from the Ready queue based on the lucOS prioritisation workflow.
  • Dispatches ownership and moves issues to Ready for work, including ad-hoc dispatch guidance.
  • Enforces guardrails to avoid misprioritization and ensure traceability across project boards.

Quick Start

Run the prioritisation script to fetch the next implementable issue and dispatch it to the assigned teammate.

Frequently Asked Questions about next

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

FAQPage Schema
How do I automate issue triage and select the next actionable issue from a project board?

Automated issue triage selects the next actionable issue from the prioritization board by evaluating readiness metadata and moving tasks to Ready. The automation script fetches the next implementable issue and dispatches it to the assigned teammate, reducing manual triage time.

What is the best way to dispatch tasks to owners and coordinate project board status to Ready?

Dispatching tasks to owners is best handled by automating the end-to-end workflow of selecting actionable issues and updating board status to Ready. The system enforces guardrails to ensure traceability and avoid misprioritization during the dispatch process.

Can I use frontmatter-driven configuration to guide issue prioritization and activation?

Yes, frontmatter-driven configuration uses name and description fields to guide activation for issue prioritization. This mechanism ensures the automation correctly targets the Ready queue and surfaces the necessary ownership and readiness metadata before dispatching.

Do I need a specific project board setup to run automated next-issue selection?

You need a prioritization board structured with triage data and a dispatch pipeline. The automation specifically fetches the next implementable issue from the Ready queue, meaning your project board must already have ownership and readiness metadata populated for the workflow to function correctly.

How do ad-hoc dispatch scenarios work when triaging new issues?

Ad-hoc dispatch scenarios are explicitly flagged by the user to override standard prioritization. The automation interacts with the project's triage data and dispatch pipeline to handle these specific cases, ensuring ownership is assigned and the issue is moved to Ready without disrupting the standard queue workflow.

Why does automated workflow dispatch enforce guardrails during issue selection?

Automated workflow dispatch enforces guardrails to avoid misprioritization and ensure traceability across project boards. By validating ownership and readiness metadata before moving issues to Ready, the system prevents incorrect task assignment and maintains accurate project tracking.