next

Read AGNT_DIR state.json and priority rules to recommend the next quest command.

1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/october-academy/agnt --skill next-october-academy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next
Source: https://github.com/october-academy/agnt/tree/main/skills/next
Command: npx skills add https://github.com/october-academy/agnt --skill next-october-academy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a solo-founder agent is midway through an Agentic30 journey, it can be unclear what the most valuable next step is; this Skill reads the agent's local state and signals to deterministically recommend the single next command to progress toward launch goals.

Core Features & Use Cases

  • State-aware navigation: Reads AGNT_DIR state.json and applies a priority table to choose the next quest (audit, discover, interview, compete, spec, channel, content, offer, launch, analyze, retro, or status).
  • Contextual messaging and tone: Computes day-based urgency and attaches concise rationale and optional journey-based tips to the recommendation.
  • Orchestration and safety: Optionally syncs MCP signals, updates limited state fields for CTA nudges, and can auto-dispatch the chosen child skill while respecting failure/backoff rules.
  • Use case: When a user asks "what should I do next?", the Skill inspects progress, channel signals, interviews, and timing to return a single actionable command plus a brief reason and expected effort.

Quick Start

Ask the navigator to recommend the next action by saying "Recommend the next action based on current AGNT state and signals."

Frequently Asked Questions about next

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

FAQPage Schema
How do I recommend the next best action for my project based on local state?

To recommend the next best action, the navigator reads local state.json from AGNT_DIR fallback paths and applies priority rules to output a single command with rationale. It evaluates current progress to select the most valuable next step toward your launch goals.

How does state management orchestration decide which task to execute next?

State management orchestration decides the next task by consulting navigator-engine.md priority and tone rules, optionally synchronizing MCP signals. It computes day-based urgency and countdown to select a quest like audit, spec, or launch.

Can I use MCP signals to determine the next action in an automated workflow?

Yes, you can use MCP signals to determine the next action. The navigator optionally synchronizes MCP signals alongside local state to compute recommendations, updating limited state fields for CTA nudges and auto-dispatching child skills while respecting failure backoff rules.

What is the best way to automate task selection for an Agentic30 launch journey?

The best way to automate task selection is applying a navigator inside Agentic30 CLI workflows. It reads progress, channel signals, interviews, and timing to return a single actionable command plus a brief reason and expected effort.

What to do when project state navigation fails to return a recommended next action?

When project state navigation fails to return a recommended next action, verify that state.json exists in your AGNT_DIR fallback paths. The navigator requires valid local state and navigator-engine.md priority rules to compute a recommendation and dispatch the chosen child skill.