Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

operation-system-contract

Read this when changing runtime-owned dispatch, source-aware operationRef, step-completion transport, prompt composition boundaries, or live versus debug prompt differences.

Ejecutar en Manus

Resumen

Read this when changing runtime-owned dispatch, source-aware operationRef, step-completion transport, prompt composition boundaries, or live versus debug prompt differences.

Comando de instalación

npx skills add https://github.com/atman-33/multi-agent-ff15 --skill operation-system-contract

Copia y pega este comando en Claude Code para instalar la habilidad

Fuente

atman-33/multi-agent-ff15

Estrellas4

Forks0

Actualizado22 de abril de 2026, 00:09

SKILL.md

readonly

name	operation-system-contract
description	Read this when changing runtime-owned dispatch, source-aware operationRef, step-completion transport, prompt composition boundaries, or live versus debug prompt differences.

Operation System Contract

Purpose

This document organizes the stable runtime and prompt-composition contract of the operation system in this repository.

Refer to it when changing workflow routing, runtime dispatch ownership, report handling, or prompt composition boundaries.

Non-Negotiable Invariants

Dispatch is runtime-mediated, not direct agent chaining.
The runtime decides the next actor and owns worker dispatch.
The canonical workflow key in runtime state is operationRef, and operationName is for display only.
Workflows with the same name across builtin and project sources are treated as separate catalog entries.
Auto activation from a free-form message succeeds only when there is a unique catalog match.
The canonical transport for step completion is taskId + next + message.
Routing depends on runtime state, not standalone body tags or [STEP:N] tokens.
Noctis steps and worker steps share the same completion contract.
A delegated child task does not change parent step ownership; after reporting, it returns to the same Noctis-owned step.

Más de este repositorio

mismo repositorio

github-release

atman-33/multi-agent-ff15

Automate GitHub release workflows including version management, CHANGELOG updates, PR creation, and GitHub Release publishing for multi-agent-ff15.

2026-05-024

operation-customization

atman-33/multi-agent-ff15

Create or customize repository operations and facet files. Use when adding or editing builtin or project-authored workflow YAML, jobs, instructions, skills, policies, or output-contracts, or when diagnosing operation routing, prompt composition, instruction placeholders such as output, setting, or root placeholders, source-aware operation refs, and debug-preview behavior.

2026-05-024

pr-assistant

atman-33/multi-agent-ff15

Analyzes git changes, drafts localized PR titles and bodies, and assists with creating comprehensive pull requests. Use when user wants to create a PR, review changes before PR, or needs help drafting PR descriptions. Triggers on phrases like 'create PR', 'make a pull request', 'draft PR description', 'what changed in this branch', 'prepare PR'.

2026-04-264

manual-verification-docs

atman-33/multi-agent-ff15

Organize post-implementation manual verification steps, execution methods, and expected results into a checklist-oriented dated Markdown report. Use when the user asks for verification steps, acceptance checks, expected outcomes, or manual test notes for UI, API, job, permission, or notification changes after implementation.

2026-04-254

agent-relationships

atman-33/multi-agent-ff15

Use when you want a short reference for the relationships and traits of FF15-derived agents such as Noctis, Gladiolus, Ignis, and Prompto.

2026-04-224

operation-authoring-and-diagnostics

atman-33/multi-agent-ff15

Read this before safely changing operation YAML, project workflow authoring paths, source-aware operationRef handling, facet source resolution, output contracts, output placeholders, or workflow-related tests.

2026-04-224

Fuente

atman-33

atman-33/multi-agent-ff15

Abrir repositorio de GitHub Ver repositorios del creador

Comando de instalación

Descarga

Ejecutar en Manus

Útil paraSOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas15-1252L4

name	operation-system-contract
description	Read this when changing runtime-owned dispatch, source-aware operationRef, step-completion transport, prompt composition boundaries, or live versus debug prompt differences.

Operation System Contract

Purpose

This document organizes the stable runtime and prompt-composition contract of the operation system in this repository.

Refer to it when changing workflow routing, runtime dispatch ownership, report handling, or prompt composition boundaries.

Non-Negotiable Invariants

Dispatch is runtime-mediated, not direct agent chaining.
The runtime decides the next actor and owns worker dispatch.
The canonical workflow key in runtime state is operationRef, and operationName is for display only.
Workflows with the same name across builtin and project sources are treated as separate catalog entries.
Auto activation from a free-form message succeeds only when there is a unique catalog match.
The canonical transport for step completion is taskId + next + message.
Routing depends on runtime state, not standalone body tags or [STEP:N] tokens.
Noctis steps and worker steps share the same completion contract.
A delegated child task does not change parent step ownership; after reporting, it returns to the same Noctis-owned step.