orquestrador-init

Create and manage a pedagogical orchestrator from a validated F0 summary.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/iago-leal/skills --skill orquestrador-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orquestrador-init
Source: https://github.com/iago-leal/skills/tree/main/meca-framework/orquestrador-init
Command: npx skills add https://github.com/iago-leal/skills --skill orquestrador-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a factory to create a dedicated MECA orchestrator instance from a validated F0 summary, ensuring consistent pedagogy and governance across sessions.

Core Features & Use Cases

  • Ingests a validated Sumarização F0 and RAOP to produce an autonomous orquestrador that follows the MECA two-layer expertise principle.
  • Supports activation via /orquestrador-init and safe transitions with --refresh, including SOAP-based transition artifacts.
  • Automates artifact lifecycle (SOAPs, RAOP updates) and enforces authorship seals.

Quick Start

Invoke /orquestrador-init after a validated F0 to generate the inaugural orquestrador and update the RAOP accordingly.

Frequently Asked Questions about orquestrador-init

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

FAQPage Schema
How do I create a pedagogical orchestrator from a validated F0 summary?

To create a pedagogical orchestrator, invoke /orquestrador-init after a student completes Session Zero with a validated F0 summary and an available RAOP, generating an autonomous MECA orchestrator instance.

What is the MECA two-layer expertise principle in pedagogical orchestration?

The MECA two-layer expertise principle is an enforced pedagogical framework where the generated orchestrator follows structured expertise tiers to guide educational sessions consistently based on validated evidence.

How do I safely swap an active MECA orchestrator during a session?

To safely swap an active MECA orchestrator, use the optional --refresh command to transition orchestrators, which automatically generates SOAP-based transition artifacts to maintain session continuity.

What artifacts are required to generate an autonomous MECA orchestrator?

Generating an autonomous MECA orchestrator requires a validated Sumarização F0 and a RAOP, while also enforcing frontmatter-signed authorship seals to operate and manage the artifact lifecycle.

Can I use the orquestrador-init factory without frontmatter-signed authorship seals?

No, the orquestrador-init factory strictly requires frontmatter-signed authorship seals to operate, ensuring consistent pedagogy and governance across all generated MECA orchestrator sessions.

When do I need to update the RAOP after creating a pedagogical orchestrator?

You need to update the RAOP immediately after generating the inaugural pedagogical orchestrator via /orquestrador-init, as the factory automatically automates the RAOP artifact lifecycle updates.