- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add boshu2/agentops --skill implement -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add boshu2/agentops --skill implement -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add boshu2/agentops --skill implement -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add boshu2/agentops --skill implement -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/boshu2/agentops/tree/HEAD/plugin/skills/implementVom Herausgeber
Implement the accepted outcome. Repair ordinary known defects directly. Use the existing intent; a clear edit needs no Plan first. An incoming report nobody has accepted yet goes to Triage first. Implement owns source changes and factual checks.
When changing a public failure path, preserve its native failure signal and check that its recovery advice matches any work already performed. For uncertain write outcomes or unattended callers, use only the relevant checks in Test's error recovery method.
For an accepted bounded shortcut, review feedback or a defect your change introduced, an authorized commit, history rewrite or merge conflict, dependency upgrade, removal, blocked operation, a decision read from another tool's state or your own uncertain write, use only the matching change safety method. These methods preserve existing authority; they grant no new operation.
For authorized service operations, load only the relevant procedure from operations methods (reliability, delivery, incident recovery, resilience, toil); ordinary edits owe no operations phase.
.git/hooks is not cloned) and it fails on a deliberate
violation; else list it under gaps as not wired. Use a local server already
on a port only if it provably serves this checkout; stop only processes you started.Keep full logs at their source; do not duplicate inventories or status documents.
changed: <runtime-derived paths>; identity: <commit or content digests>
author: <runtime session/subagent/thread ID, "ID (supplied)" or "unknown">; when an integrator or fresh read follows
checks: <exact command> -> <result>, one per line; before and after for a behavioral change
not run: <check> -> <reason>; "none" only when every relevant check ran
consumers: <file:line> -> <covering check, or "uncovered">
not_as_briefed: <steps refused, held, worked around or unverified, one line with its reason each> | none
gaps: <missing or truncated evidence, known failures, scope amendments needed> | none
cause: <defect repairs only: trigger -> mechanism -> symptom at file:line; sites left as follow-up>
Report an uncovered live consumer for a caller scope amendment and continue independent authorized work. Disclose a reversible implementation choice only when its alternative has a material consequence the caller may want to change; name the choice, alternative and reason in the handoff, without a fixed worksheet. Generated companions already included as scope require no new approval; a change to accepted direction, behavior or acceptance always needs caller authority.
Before repairing a failure you cannot yet explain, read and follow the diagnosis loop. The same file holds the experiments for races, leaked state, hangs, regressions and failures that cross components.
When scaffolding is the requested change, start from the repository's existing layout (or the ecosystem's standard one for a new project) and one working vertical slice; avoid placeholder success paths and a new framework for a one-off operation.
Prefer current-session execution. When delegation is authorized, or the caller asks for a one-shot adapter or a factory, read delegated work before dispatching or writing it.
Specialists advise only; known defects stay implementation work. A genuine causal stall admits one bounded fresh helper under RPI's stall rule; retries renew no bound.
Return facts, not semantic PASS. An implement-only handoff does not authorize Git, tracker or delivery transitions; existing caller authority remains usable. A full outcome request finishes on its checks and CI; it continues to one fresh independent judgment only on Validate's triggers.
Make the code change a ticket or bug report asks for, then prove it with the repo''s own checks. Use when: told to fix, change or build something, such as "fix this bug".
---name: implementdescription: Make the code change a ticket or bug report asks for, then prove it with the repo''s own checks. Use when…---# plugin/skills/implement/SKILL.mdFAQ
Laden Sie plugin/skills/implement/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/boshu2/agentops.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.
gapsgit status --porcelain,
git diff --name-only <base>), never from memory;
ao provenance manifest --root <repo> with one --include <path> per
declared path digests only the paths you declare and runs no Git. A delegated
increment awaiting integration returns an exact commit or runtime-derived
content digests, author context ID and check facts in the existing handoff.
Copy that ID from the session, subagent or thread ID the runtime exposes, or
label a caller-supplied one as supplied; otherwise report it as unknown,
never made up. The integrating caller derives subject-manifest.v1 (AgentOps
schema subject-manifest.v1.schema.json, AgentOps source checkout only) over the complete final
subject before judgment; an independently judged increment needs its own
manifest. Do not generate both merely because work was delegated. Where the
repository records AgentOps evidence bindings, also run the advisory
ao provenance evidence-orphans --root <repo-root> with one --changed <path>
per derived path. Disclose the rows whose cause is changed_path or both
(they bind your paths); count the rest under gaps as pre-existing drift,
and refresh a binding only when its owner asks. Without ao, list it under
not run.