omni-plan

Orchestrate a 13-step multi-agent pipeline with tri-tiered evaluation and recursive convergence.

8|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill omni-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omni-plan
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/skills/omni-plan
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill omni-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and automates a complex, cross-domain planning and execution workflow to deliver production-ready software and documentation with auditable decisions.

Core Features & Use Cases

  • 13-step orchestrative pipeline that chains every tool in the system into a single, cohesive workflow.
  • Tri-tiered evaluation with recursive convergence to steadily improve quality across dimensions.
  • Autonomous Pivot/Refine/Proceed decision loops with guardrails, logs, and convergence reporting for robust delivery.

Quick Start

Invoke omni-plan on a target to start the 13-step orchestration and produce a production-ready plan.

Frequently Asked Questions about omni-plan

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

FAQPage Schema
How do I orchestrate multi-agent planning for production-ready software delivery?

Multi-agent planning for production-ready software is orchestrated through a 13-step pipeline that automates structured research, reviews, and evaluation across CEO, engineering, and design perspectives to deliver auditable outputs.

How does recursive convergence work in automated codebase evaluation?

Recursive convergence in automated codebase evaluation applies tri-tiered quality checks repeatedly, driving autonomous pivot, refine, or proceed decision loops until production-readiness criteria are met and convergence is reported.

Can I use automated planning pipelines to generate engineering reviews across different perspectives?

Automated planning pipelines generate engineering reviews across different perspectives by chaining tools into a cohesive workflow that evaluates targets from CEO, engineering, and design viewpoints with explicit logs and guardrails.

What is the best way to automate cross-domain software planning and documentation workflows?

The best way to automate cross-domain software planning and documentation workflows is using an end-to-end orchestration pipeline that coordinates research, evaluation, and automated fix loops to produce production-ready plans with auditable decisions.

Do I need specific dependencies to run automated fix loops and convergence reporting?

No specific dependencies are required to run automated fix loops and convergence reporting, as the orchestration operates autonomously with built-in guardrails and explicit logs to manage the workflow internally.

When should I not use an autonomous multi-agent orchestration pipeline?

You should avoid autonomous multi-agent orchestration pipelines for simple tasks lacking the complexity to warrant tri-tiered evaluation, as the 13-step process is built for projects requiring deep research, recursive convergence, and structured reviews.