next

Select one prioritized action per invocation and dispatch work to subagents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This orchestration tool picks a single action per /loop /next invocation from a predefined priority list to keep rpm moving without requiring constant prompts, reducing drift and context-switching.

Core Features & Use Cases

  • Single-step decision: each invocation processes exactly one action from the priority order (blocked-on-user → drift-fix → actionable-backlog → idle).
  • Auto-dispatch: delegates work to subagents when needed and logs decisions for audit trails.
  • Unattended operation: designed for looped use with /loop /next, enabling autonomous backlog progression and drift management.

Quick Start

Invoke the orchestrator with /loop /next to perform one step and let it manage the next action and log the outcome.

Frequently Asked Questions about next

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

FAQPage Schema
How do I automate backlog progression and drift detection in unattended sessions?

Automating backlog progression involves invoking an orchestrator with /loop /next to select a single action per tick from a strict priority list. This approach dispatches work to subagents, logs decisions for audit trails, and terminates after three consecutive idle ticks for safe, predictable operation.

What is the best way to prevent context-switching when managing rpm workflows?

Preventing context-switching requires a single-step decision orchestrator that picks exactly one action per invocation from a predefined priority order: blocked-on-user, drift-fix, actionable-backlog, then idle. This enforces a non-looping internal flow to keep operations moving without constant manual prompts.

How does the priority-based action selection mechanism work for session management?

The priority-based selection mechanism evaluates a strict list sequentially per invocation: blocked-on-user first, then drift-fix, actionable-backlog, and finally idle. It processes exactly one matching action, auto-dispatches tasks to subagents, logs the decision, and terminates safely after three consecutive idle ticks.

Do I need jq installed to run the rpm orchestrator?

Yes, you need jq installed as a required dependency to run the rpm orchestrator. This command-line JSON processor is necessary for the scripts component to parse data, evaluate the priority list, and auto-dispatch work to subagents during unattended session management.

Why does the orchestrator terminate after three consecutive idle ticks?

The orchestrator terminates after three consecutive idle ticks to enforce safe, predictable operation and prevent infinite looping. This constraint ensures the non-looping internal flow halts automated backlog progression and drift detection when no actionable tasks remain in the priority queue.