osa

Coordinate distributed CLI subagents with fixed rotation order and per-agent git worktrees.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/nbiish/native-psionic-programs --skill osa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: osa
Source: https://github.com/nbiish/native-psionic-programs/tree/main/.agents/skills/osa
Command: npx skills add https://github.com/nbiish/native-psionic-programs --skill osa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate coordinated subagent workflows by enforcing a deterministic, fixed rotation order with per-agent worktrees, enabling parallel tasks and reliable fallbacks.

Core Features & Use Cases

  • Fixed rotation order across equal CLI agents (Gemini, Claude, Crush, pi, mini, opencode, kilo) to dispatch tasks with deterministic sequencing.
  • Per-subagent git worktrees to isolate changes and merge outputs safely.
  • YOLO mode (non-interactive) execution with automatic fallback on failure to ensure progress in automated pipelines.
  • Use cases include code changes orchestration, parallel agent execution, and multi-tool task coordination across development tasks.

Quick Start

Run the osa orchestrator to begin rotating the fixed agent order and observe isolated worktrees per subagent.

Frequently Asked Questions about osa

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

FAQPage Schema
How do I orchestrate multi-agent tasks with a deterministic execution order?

You can orchestrate multi-agent tasks deterministically by enforcing a fixed, rotate-first execution order across distributed subagents. This coordinates CLI agents like Gemini and Claude with per-agent git worktrees to isolate changes safely.

How does git-worktree isolation work for parallel agent execution?

Git-worktree isolation assigns a separate worktree to each subagent, ensuring parallel code changes remain independent. This allows multiple CLI agents to execute tasks simultaneously and merge outputs safely without conflicting modifications.

Can I use automation to dispatch code changes across different CLI agents like Gemini and Claude?

Yes, you can dispatch code changes across equal CLI agents including Gemini, Claude, Crush, pi, mini, opencode, and kilo. The orchestration uses a fixed rotation order to sequence tasks automatically across these tools.

What happens when a subagent fails during non-interactive task orchestration?

When a subagent fails during non-interactive task orchestration, the system applies automatic fallback on failure to ensure progress. This fault-tolerance mechanism keeps automated pipelines moving without manual intervention.

Do I need a fixed agent order to run multi-agent orchestration?

Yes, a fixed agent order is required to maintain deterministic sequencing. The orchestration model relies on this predefined rotation order to dispatch tasks, execute autonomous non-interactive pipelines, and manage worktrees effectively.

What is the best way to coordinate parallel work across multiple coding agents?

The best way to coordinate parallel work is using a deterministic orchestration model with fixed rotation. It dispatches tasks across multiple CLI agents, isolates changes in per-task git worktrees, and handles failures with automatic fallback.