Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/boshu2/agentops --skill operationalize명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Use Agent Mail as an optional messaging and file-reservation adapter for explicitly coordinated writers. Triggers: "coordinate writers", "reserve files".
Operate explicit orchestrator, implementer, validator, and scribe roles through a caller-selected agent runtime. Triggers: "agent-native factory", "role-shaped agent panes", "persistent workers".
Initialize minimal AgentOps documentation and verdict storage without taking over repository workflow. Triggers: "bootstrap AgentOps", "initialize AgentOps docs".
SKILL.md 표시 중
| name | operationalize |
| description | Distill repeated, evidence-backed expertise |
Turn repeated, cited expertise into a proposal for a reusable artifact.
.agents/scratch/operationalize/ first and return the path; the proposal
is advisory either way.A rule needs three real occurrences before it may be abstracted. Count only occurrences that actually happened and can be cited — sessions, diffs, verdicts, or artifacts that resolve in this repository — not hypothetical cases or restatements of one event. With one or two occurrences, propose a quote-anchored reference note instead and stop short of a rule. An explicit authoritative source may substitute for occurrences only when the proposal transcribes that source rather than generalizing beyond it. The named failure mode is premature abstraction: a rule minted from a single vivid incident that encodes the incident's accidents as policy.
Every proposed rule carries a reapply proof: a demonstration that the rule, as written, reproduces the correct decision on at least one of its source occurrences without extra context. If applying the drafted rule to its own source moment requires unwritten judgment, the rule is not yet operational — tighten the wording until the reapply succeeds, or downgrade the proposal to a reference. When the proposal creates process, the reapply proof must also show that the creation gate returns the correct create-or-drop decision. No reapply proof, no rule.
Tie each rule to its source moments with a quote bank: for every counted
occurrence, a short verbatim quote or command/output excerpt plus a locally
resolving citation (repo path, .agents/ao digest, or session artifact). An
occurrence that cannot be quoted and cited does not count toward the
three-instance floor. Anchors let a later reader test whether the rule still
matches what actually happened, instead of trusting the abstraction.
Operationalize does not create tracker work, promote policy, start a factory,
validate its own output, or control another invocation. The proposal is
advisory: adopting it into a skill, deterministic check, reference, or
workflow is a separate, caller-selected step — skill-builder,
workflow-builder, or a fresh RPI — never performed here. The proposal
cannot promote itself, and process-only output earns no capability credit.