Master Orchestrator

Name: Master Orchestrator
Availability: InStock
Author: KhoriumAI

Define architecture planning protocols with three implementation strategies before coding.

Updated Aug 23, 2026

Search Tags:#planning #architecture #delegation #governance #negotiation #software-engineering #technical-debt

Ready to run

npx skills add https://github.com/KhoriumAI/SimOps --skill master-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Master Orchestrator
Source: https://github.com/KhoriumAI/SimOps/tree/main/khorium_skills/orchestrator
Command: npx skills add https://github.com/KhoriumAI/SimOps --skill master-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define and enforce architecture planning protocols to prevent technical debt.

Core Features & Use Cases

Provides a disciplined framework for strategic planning, approach negotiation, and sub-skill delegation across software projects.
Guides engineering leaders to align on architecture before implementation, reducing risk and rework.
Facilitates governance and decision-making through repeatable, structured processes.

Quick Start

Follow the Phase 1 kickoff protocol to ground new tasks in architecture before coding.

Frequently Asked Questions about Master Orchestrator

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

FAQPage Schema

How do I prevent technical debt during software architecture planning?▼

To prevent technical debt during software architecture planning, define and enforce a structured planning protocol that requires proposing three implementation strategies before proceeding to code. This ensures alignment and reduces rework risk.

What is the best way to scope engineering tasks and negotiate solutions?▼

The best way to scope engineering tasks and negotiate solutions is to apply a three-phase planning protocol with mandatory front-matter identity, ensuring architecture is grounded before implementation and delegation across projects.

How does a three-phase planning protocol work for software project governance?▼

A three-phase planning protocol works for software project governance by enforcing a structured decision-making process that requires front-matter identity and approach negotiation before task delegation, ensuring repeatable and disciplined execution.

Can I use structured delegation to manage technical debt across multiple projects?▼

Yes, you can use structured delegation to manage technical debt across multiple projects by applying governance protocols that mandate architecture alignment and solution negotiation before implementation begins, reducing risk and rework.

Do I need to propose multiple implementation strategies for every engineering task?▼

Yes, the planning protocol requires proposing three implementation strategies for every engineering task before proceeding, ensuring thorough approach negotiation and preventing architectural misalignment and technical debt.

When should I not use a strict architecture planning protocol?▼

You should not use a strict architecture planning protocol for trivial tasks that do not carry architectural risk or technical debt implications, as the overhead of front-matter identity and multiple strategy proposals may outweigh the benefits.