jeo

Coordinate end-to-end multi-agent AI workflows across Claude Code, Codex, Gemini, and OpenCode.

40|9|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/akillness/oh-my-skills --skill jeo-akillness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jeo
Source: https://github.com/akillness/oh-my-skills/tree/main/.agent-skills/jeo
Command: npx skills add https://github.com/akillness/oh-my-skills --skill jeo-akillness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires plannotator, agentation-mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This integrated orchestration skill coordinates end-to-end multi-agent workflows, unifying planning, execution, QA, and cleanup across multiple AI platforms while keeping a durable local ledger for traceability.

Core Features & Use Cases

  • End-to-end orchestration of multi-agent tasks using plannotator gate, BMAD fallback, and agentation UI verification.
  • Maintains a project-local .jeo ledger with long-term, short-term, planned, progress, and history data to track scope, progress, and outcomes.
  • Facilitates cross-platform execution and verification across Claude Code, Codex, Gemini, and OpenCode.

Quick Start

To begin, run jeo "<task description>" to activate the orchestration workflow.

Frequently Asked Questions about jeo

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

FAQPage Schema
How do I orchestrate multi-agent AI workflows across different coding tools?

Multi-agent AI workflow orchestration coordinates planning, execution, and QA across Claude Code, Codex, Gemini, and OpenCode. It unifies these platforms using plan gating and UI annotation verification to manage cross-tool execution with state persistence.

What is plan gating in multi-agent AI development?

Plan gating in multi-agent AI development enforces structured task progression by validating planning phases before execution. It uses plannotator gates and BMAD fallback mechanisms to ensure scope compliance before downstream agents proceed.

How do I track multi-agent AI project progress and history locally?

Track multi-agent AI project progress using a project-local .jeo ledger that persists state. It maintains long-term, short-term, planned, progress, and history data to ensure full traceability of scope, outcomes, and task execution across sessions.

Can I use agentation for UI verification in cross-platform AI workflows?

Yes, agentation UI verification validates interface changes during cross-platform AI workflows. It integrates with the orchestration cycle to verify UI annotations alongside QA and cleanup phases across supported coding tools.

Do I need plannotator and agentation-mcp to run end-to-end AI orchestration?

Yes, end-to-end AI orchestration depends on plannotator and agentation-mcp. These dependencies provide the foundational plan gating logic and UI annotation verification required to coordinate multi-agent execution.