beo-router

Route beo sessions to the correct downstream skill based on current state.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/minhtri2710/skills --skill beo-router
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: beo-router
Source: https://github.com/minhtri2710/skills/tree/main/skills/beo/router
Command: npx skills add https://github.com/minhtri2710/skills --skill beo-router

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Route and bootstrap beo sessions by detecting current state and loading the correct downstream skill, ensuring a guided, stateful start to every workflow.

Core Features & Use Cases

  • Entry point for beo sessions: bootstraps the workspace, detects state, and routes to the next skill.
  • State-guided routing: directs to the appropriate beo skill (beo-exploring, beo-planning, beo-validating, beo-swarming, beo-executing, beo-reviewing, beo-compounding, beo-dream) based on artifacts and bead graph.
  • Handoff and resume support: handles HANDOFF.json to resume from the last checkpoint and maintain workflow continuity.

Quick Start

Start a new beo session; the router bootstraps, detects state, and routes to the appropriate skill.

Frequently Asked Questions about beo-router

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

FAQPage Schema
How do I bootstrap a workflow session and route to the right pipeline stage?▼

To bootstrap a workflow session and route correctly, the router detects your current state using artifacts like CONTEXT.md and phase-contract.md, then loads the appropriate downstream skill for execution.

What is state detection in a development pipeline and when is it needed?▼

State detection in a development pipeline identifies your current progress by checking artifacts like story-map.md and bead graphs. It is needed at session start or during handoffs to determine what comes next.

How do I resume a workflow from a previous handoff checkpoint?▼

To resume a workflow from a previous handoff checkpoint, the router processes HANDOFF.json to restore session continuity, validate gating artifacts, and route you back to the correct downstream skill.

Do I need specific markdown artifacts to gate pipeline transitions?▼

Yes, you need specific markdown artifacts to gate pipeline transitions safely. The router requires CONTEXT.md, phase-contract.md, and story-map.md to verify state and ensure secure handoffs before execution.

Can I use this router to manage handoffs across different execution skills?▼

Yes, you can use this router to manage handoffs across different execution skills. It directs sessions to appropriate downstream skills like beo-executing, beo-validating, or beo-planning based on detected state.

What are the limitations of state-guided routing for session bootstrapping?▼

The limitation of state-guided routing for session bootstrapping is its strict dependency on specific artifacts. Without CONTEXT.md, phase-contract.md, story-map.md, or HANDOFF.json, the router cannot detect state or gate transitions safely.