القائمة
Use when a user describes a repeatable process and needs a process contract with trigger, inputs, output, owner, definition of done, source map and first-run contract. Triggers include “собери бриф процесса”, “operating brief”, “опиши процесс”, and “спецификация процесса”.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill should be used when the user asks to "подготовить weekly launch update", "сделать еженедельное обновление по запуску", "написать update для CEO", "собрать статус запуска", "выделить риски запуска", "подготовить статус по проекту", or "prepare a weekly launch update". It creates concise launch status updates from project context, weekly changes, risks, blockers, and decisions needed from leadership.
Use when a working process must be continued by another person or agent from an exact state.
Use before publishing or accepting an agent output as complete.
Use when work must continue in another model, runtime or computer without restarting.
Use when an operating brief or process description exists and the user needs to identify the first automation candidate, assign agent/automation/person roles, map human gates, and place each step on the adoption curve. Triggers include “разбери процесс”, “process audit”, “что автоматизировать”, and “приоритизируй шаги”.
| name | operating-brief |
| description | Use when a user describes a repeatable process and needs a process contract with trigger, inputs, output, owner, definition of done, source map and first-run contract. Triggers include “собери бриф процесса”, “operating brief”, “опиши процесс”, and “спецификация процесса”. |
Turn a raw process description into a concise contract that can be handed to a person or agent.
trigger, inputs, output, owner, definition_of_done.source · why · access · boundary.agent, automation or person.output/{project} {brief} <description> – YYYY-MM-DD.md.Use this self-contained structure so the skill stays portable after installation:
# {process name} – operating brief
## Identity
- project slug:
- owner:
- frequency:
## Five fields
- trigger:
- inputs:
- output:
- owner:
- definition of done:
## Source map
| source | why it matters | access | boundary |
|---|---|---|---|
## Process steps
| step | input | action | output | executor | human gate |
|---|---|---|---|---|---|
## First candidate
- candidate:
- reason:
## First run contract
- output filename:
- review owner:
- maximum run time:
- evidence line: result · evidence · gap · system update
- next run: