| id | genesis-orchestrator |
| name | genesis-orchestrator |
| type | skill |
| version | 2.0.1 |
| created | 20/03/2026 |
| modified | 20/03/2026 |
| status | active |
| metadata | {"author":"NodeJS-Starter-V1","version":"2.0.1","locale":"en-AU"} |
| description | Autonomous project orchestration protocol for Next.js full-stack builds. Triggers on \"build\", \"implement\", \"create feature\", \"plan\", \"architecture\", or when starting new phases. Enforces phase-locked execution, token economy, and sectional verification gates.
|
| context | fork |
Genesis Hive Mind Orchestrator
Master orchestration protocol for autonomous Next.js full-stack development. Transforms natural language intent into precise, phase-locked execution commands.
Description
Governs the full lifecycle of feature and project builds by enforcing phase-locked execution, token economy constraints, and sectional verification gates. Decomposes complex requests into Discovery, Vision Board, Blueprint, and Execution phases, delegating to sub-agents (MATH_COUNCIL, TITAN_DESIGN, GENESIS_DEV) as required. Ensures no phase advances without passing all quality checks.
When to Apply
Positive Triggers
- Starting a new feature implementation
- Planning project architecture
- Executing multi-phase development tasks
- Needing to break complex work into verifiable sections
- User says: "build", "implement", "create", "plan", "architecture"
Negative Triggers
- Reviewing or optimising existing code (use
council-of-logic instead)
- Styling or designing UI components (use
scientific-luxury instead)
- Running single-file bug fixes that do not require phased execution
Core Directives
Token Economy Protocol
| Rule | Mechanism | Instruction |
|---|
| NEVER output full project code in one pass | SECTIONAL_EXECUTION | Break every major task into isolated 'Phases'. Complete one phase, verify it, clear context, then proceed. |
Why: Prevents context-window overflow and ensures quality verification at each step.
Sub-Agent Activation
| User Intent | Activate Agent |
|---|
| "optimise", "algorithm", "performance", "logic" | MATH_COUNCIL |
| "design", "UI", "animation", "style", "look" | TITAN_DESIGN |
| "build", "implement", "create", "add feature" | GENESIS_DEV |
| "plan", "architecture", "structure" | BLUEPRINT_MODE |
| "what is", "explain", "how does" | DISCOVERY_MODE |
Autonomous Workflow Loop
PHASE 1: DISCOVERY
Trigger: On project load or git pull
- Scan file structure (Greenfield vs. Brownfield)
