azoth-next

Surface the next priority roadmap task and propose a concrete action.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex-visible entrypoint that surfaces the next priority task from Azoth's roadmap and suggests a concrete, actionable next step to move the workflow forward.

Core Features & Use Cases

  • Codex-native entrypoint: Use /next to quickly retrieve the upcoming roadmap task and a recommended action.
  • Execution contract adherence: Reads the contract at commands/next/command.yaml and the body at commands/next/body.md; preserves the command's stage structure, gate rules, and evaluation rules.
  • Seamless integration: Maintains the agent binding and supports Codex UI and CLI usage for uninterrupted workflow continuity.

Quick Start

Ask Codex to fetch the next priority task from the roadmap and propose the next action

Frequently Asked Questions about azoth-next

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

FAQPage Schema
How do I surface the next priority task from a roadmap in Codex?

To surface the next priority task from a roadmap in Codex, use the /next trigger to fetch the upcoming task and propose a concrete next action. The system reads the command contract and body to preserve stage structure and evaluation rules.

What is the best way to orchestrate workflow tasks using Codex slash commands?

Orchestrating workflow tasks with Codex slash commands involves triggering /next to retrieve the next roadmap item. This approach preserves the agent orchestrator binding and suggests an actionable step to advance the workflow.

Does the next-task orchestrator require specific dependencies to function?

The next-task orchestrator does not require external dependencies to function. It operates natively within Codex-enabled environments by reading the command contract and body files to maintain gate rules and stage structure.

Can I use the roadmap task surfacing feature in both Codex UI and CLI?

Yes, you can use the roadmap task surfacing feature in both Codex UI and CLI. It maintains seamless integration to support uninterrupted workflow continuity when fetching prioritized tasks and recommended steps.

How does the next-task command enforce execution contracts?

The next-task command enforces execution contracts by reading the command.yaml and body.md files. This ensures the workflow preserves the command's stage structure, gate rules, evaluation rules, and the agent orchestrator binding.

When should I not use an automated roadmap task orchestrator?

You should not use an automated roadmap task orchestrator if your environment lacks Codex support or if your workflow does not rely on structured stage gates and evaluation rules for task progression.