next

Select and execute the next pending task from a spec workflow.

14|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/brsbl/ottonomous --skill next-brsbl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next
Source: https://github.com/brsbl/ottonomous/tree/main/skills/next
Command: npx skills add https://github.com/brsbl/ottonomous --skill next-brsbl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the decision and initiation step in a multi-task workflow by selecting the next actionable item from a set of specs, tasks, and sessions.

Core Features & Use Cases

  • Next-item decision: Selects the next pending task or session, resolving blockers and ordering by priority.
  • Batch & parallel execution: Supports batch execution with parallel subagents for multiple priorities while marking work-in-progress.
  • Planning-driven execution: Always triggers a planning phase before implementation and reports outcomes with IDs and statuses.

Quick Start

Tell me to pick the next task or session to continue your workflow.

Frequently Asked Questions about next

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

FAQPage Schema
How do I automate selecting the next task in a multi-step workflow?

Automating next task selection is handled by prioritizing unblocked, high-priority items from your pending specs and sessions. The system resolves blockers, orders tasks by priority, and delivers a concrete implementation prompt to subagents for execution.

How does planning-driven task execution work before implementation?

Planning-driven task execution enforces a mandatory planning phase before any implementation begins. It tracks statuses and reports progress with deterministic prompts, ensuring a concrete plan is established and validated before subagents execute the selected work.

Can I run batch operations with parallel subagents for pending tasks?

Batch operations with parallel subagents are supported for executing multiple priorities simultaneously. The system manages work-in-progress states, dispatching actionable items to parallel workers while tracking session statuses and reporting deterministic outcomes.

What is the best way to manage session statuses during orchestration?

Session management during orchestration is handled by tracking statuses and reporting progress with deterministic updates. It selects the next actionable session, resolves blockers, and marks work-in-progress states to maintain accurate workflow visibility across batch operations.

How do I resolve blockers when picking the next actionable item?

Blockers are resolved by evaluating pending tasks and sessions to identify unblocked, high-priority work. The orchestration mechanism filters out blocked items, prioritizes actionable tasks, and delivers a concrete plan to initiate the next step.

Does this task selection approach work without external dependencies?

This task selection approach works without external dependencies, relying entirely on internal workflow logic. It evaluates pending specs, resolves blockers, and generates implementation prompts autonomously to drive the next actionable item forward.