- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add boshu2/agentops --skill plan -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add boshu2/agentops --skill plan -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add boshu2/agentops --skill plan -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add boshu2/agentops --skill plan -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/boshu2/agentops/tree/HEAD/plugin/skills/planFrom the publisher
Shape missing intent into one actionable slice, then stop. A clear change can proceed directly; load a specialist only for the question it answers. Prefer the caller's tracker, if any; otherwise use the conversation or supplied text. Supplied advice, such as an Idea Genie portfolio or challenge, is evidence to weigh, never a decision.
Write this block into the caller's existing intent when the request or existing authorization covers editing it (the conversation always does); otherwise return it as a proposed amendment. It is the whole plan.
Outcome: <who observes what, in the repository's terms>
Example: Given <state>, when <event>, then <observable result>
Slice: <the one end-to-end change that makes the example true>
Scope: <owners>; consumers: <live callers and tests>; generated: <class> | none
Check: <the test or observation that fails now and passes after the slice>
Question: <one caller choice, your recommendation, its tradeoff> | none
Later: <deferred item and the evidence that would make it next> | none
Add an Example line only for another consequential boundary, an Open line for a fact only a named person holds (with the drafted questions), and a non-goal only where it prevents a plausible scope mistake.
ao CLI, which the plugin does not ship, adds
ao provenance evidence-orphans --root <repo-root> --changed <path>; it
reads only AgentOps eval bindings under docs/evals/scorecards/ and
evals/skill-probes/, so an empty result rules out no other golden.
Across an epic, Navigate picks the next bead; Plan
shapes that bead.Stop planning once the implementer can act and the validator can judge. More research, decomposition or review must resolve a named remaining uncertainty; reserve capacity for implementation, integration and repair.
Resolve reversible implementation details within accepted scope. Mark inference and missing evidence; never promote either into a source fact or a settled caller choice. For consequential uncertainty that survives source checks and observation, an optional challenge returns advice or a next discriminator, never permission or acceptance. Memory recall helps only when prior evidence could change the next action.
Use real undo cost, affected users and existing authority. A material irreversible choice outside that authority goes to the caller, as does a slice that would cut against a recorded decision such as an ADR, a published contract or a declared non-goal: name that decision and the evidence for reopening it as the Question, and keep the slice within it until the caller answers. Prior authorization stays valid. Reviewer agreement is evidence, not permission to replace the caller's intent: explain a consequential disagreement and its support instead of silently changing acceptance. A proposed process artifact needs a concrete consumer, the decision it gates, an observed defect and a retirement condition; otherwise omit it.
An example can be plain text; BDD needs no .feature file or interview. In a
repository that calls queued work a Job (write "Job", not "task item"):
Given a Job has already completed, when the worker receives it again, then its completed result is returned and its side effect is not repeated.
Tests added after coding may supplement the accepted example but cannot redefine what was promised.
Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use when: planning, breaking down or scoping a change.
---name: plandescription: Shape a request into one end-to-end slice with observable behavior; review write scope and reversible…---# plugin/skills/plan/SKILL.mdFAQ
Download plugin/skills/plan/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/boshu2/agentops.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.