메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | operation-authoring-and-diagnostics |
| description | 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. |
This document organizes the authoring rules and diagnostic viewpoints needed to safely change builtin or project-authored operations and facets in this repository.
Refer to it when changing operation YAML, facet files, output contracts, placeholder behavior, or workflow-related tests.
The schema fields you should review most often are:
initial_stepsteps[]steps[].jobsteps[].instructionsteps[].skillssteps[].policiessteps[].delegation.allowed_workerssteps[].delegation.worker_jobsteps[].delegation.worker_instructionsteps[].delegation.worker_skillssteps[].delegation.worker_policiessteps[].output_contracts.report[].formatsteps[].rules[]The semantic roles of those fields differ as follows:
job: the stable role, responsibility, decision principles, and prohibitions for the stepinstruction: the step-specific execution procedure and referencesskills: background skills or reference material required to execute the current steppolicies: constraints and conventions that the current step must followdelegation.*: the allowed targets and prompt material used when a Noctis-owned step delegates a child task to a workeroutput_contracts.report[].format: the format definition for report artifactsCanonical source forms are:
job.file / job.inlineinstruction.file / instruction.inlineskills[].filepolicies[].file / policies[].inlineoutput_contracts.report[].format.file / output_contracts.report[].format.inlineCanonical authored locations and identity are:
builtins/<lang>/operations/*.yamlprojects/<project-id>/operations/*.yamlbuiltins/<lang>/facets/**projects/<project-id>/facets/**operationRef (builtin:<lang>:<fileName> or project:<projectId>:<fileName>)The following constraints often map directly to runtime failure, so check them early in design:
initial_step should point to a noctis stepfile sources resolve relative to the operation YAML pathoperationRef as the canonical key, not plain operation nameoutput_contracts.report[].format must stay consistent with the output filename and any downstream referencessteps[].delegation.allowed_workers is the authored upper bound, while the runtime effective set is the intersection with the mission's allowed worker setrules may be omitted only for an autonomous delegation step where Noctis remains on the same parent stepLegacy fields such as initial_movement, movements, max_movements, edit, handoff_mode, job_file, and knowledge_files are not canonical.
When changing prompts, always inspect both the operation YAML and the referenced facet files together.
Automate GitHub release workflows including version management, CHANGELOG updates, PR creation, and GitHub Release publishing for 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.
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'.
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.
Use when you want a short reference for the relationships and traits of FF15-derived agents such as Noctis, Gladiolus, Ignis, and Prompto.
Read this when changing runtime-owned dispatch, source-aware operationRef, step-completion transport, prompt composition boundaries, or live versus debug prompt differences.