Langsmith Observability
Orchestra-Research/AI-Research-SKILLs
LLM observability platform for tracing, evaluation, and monitoring.
Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions.
Apache-2.0Auto-check passed
Install Plan
$ npx skills add boshu2/agentops --skill plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boshu2/agentops plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/plan .claude/skills/plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plan" agent skill from https://github.com/boshu2/agentops/tree/main/skills/plan into .claude/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/boshu2/agentops/tree/main/skills/planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add boshu2/agentops --skill plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boshu2/agentops plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/plan .agents/skills/plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan" agent skill from https://github.com/boshu2/agentops/tree/main/skills/plan into .agents/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boshu2/agentops --skill plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boshu2/agentops plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/plan .cursor/skills/plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan" agent skill from https://github.com/boshu2/agentops/tree/main/skills/plan into .cursor/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/boshu2/agentops.git --path skills/plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add boshu2/agentops --skill plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boshu2/agentops plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/plan .gemini/skills/plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan" agent skill from https://github.com/boshu2/agentops/tree/main/skills/plan into .gemini/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install boshu2/agentops planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add boshu2/agentops --skill plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/plan .github/skills/plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan" agent skill from https://github.com/boshu2/agentops/tree/main/skills/plan into .github/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boshu2/agentops --skill plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boshu2/agentops plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/plan .opencode/skills/plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan" agent skill from https://github.com/boshu2/agentops/tree/main/skills/plan into .opencode/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plan- GitHub stars
- 447
- Used in
- 1 other repo
- Token cost
- ~1.8k tokens
- SKILL.md length
- 874 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions.
- Works in 6 steps: One slice, not a roadmap. Shape the… → An example before any design. Write at… → Look up facts; ask only for choices.… → …
- Scoping a change
- SKILL.md covers A plan meets these rules, Output, Workflow and Route uncertainty, plus 3 more sections
- Runs Shell scripts from its folder
What it does
Plan is an agent skill from boshu2/agentops. 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.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/challenge.md`, `references/ground-truth-routing.md` and `references/resume-and-handoff.md`).
The repository describes itself as: DevOps discipline for AI coding agents: shape the work, track it as a graph, and get each change judged by a context that didn't write it. The licence is Apache-2.0.
When your agent uses it
- Scoping a change
Example prompts
- “/plan”
Requirements
- A Bash shell
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- One slice, not a roadmap. Shape the narrowest change that produces an
- An example before any design. Write at least one Given/When/Then with
- Look up facts; ask only for choices. Read code, docs and the tracker
- The repository's words. Reuse the term its code, glossary or tracker
- Scope by consumer. Name the owners to edit, every live caller and test
- A discriminating check: what fails today and passes after the slice.
What it can do on your machine
Read from SKILL.md and the folder at commit 3bdbfed. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Plan loads about 1.8k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 43 tokens; SKILL.md has 874 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from boshu2/agentops at commit 3bdbfed, republished under its Apache-2.0 licence (© boshu2). 874 words, ~1,838 tokens.
Download SKILL.mdSave it as
.claude/skills/plan/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- plan
- description
- 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.
- practices
- bdd-gherkin, design-by-contract, ddd-bounded-context
- hexagonal_role
- domain
- output_contract
- in-place caller intent update or concise proposed amendment; never an AgentOps planning artifact
- skill_api_version
- 1
- user-invocable
- true
- metadata.graph_root
- true
- metadata.tier
- execution
- metadata.capabilities
- shape_intent, define_acceptance, bound_write_scope, resume_discovery
- metadata.effects
- update_intent_source
- metadata.canonical_status
- canonical
Plan
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. Planning produces no AgentOps packet.
A plan meets these rules
- One slice, not a roadmap. Shape the narrowest change that produces an observable result end to end, through every layer it touches. No phases, no layer-by-layer breakdown, no backlog: later work stays one coarse line each until new evidence makes it the next slice.
- An example before any design. Write at least one Given/When/Then with an observable result. Cover the boundary where a mistake is costly to undo, such as a repeated or external side effect, lost data or widened access, not only the happy path.
- Look up facts; ask only for choices. Read code, docs and the tracker instead of asking. Ask the caller at most one question, only for a choice no source can answer, with your recommendation and its tradeoff.
- The repository's words. Reuse the term its code, glossary or tracker defines; never coin a parallel name.
- Scope by consumer. Name the owners to edit, every live caller and test of the changed behavior, and generated companions as a class. Scope is authority, not a predicted file count.
- A discriminating check: what fails today and passes after the slice.
Output
Write this block into the caller's existing intent (tracker item or conversation). 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> | noneAdd an Example line only for another consequential boundary, and a non-goal only where it prevents a plausible scope mistake.
Workflow
- Read the accepted intent, any existing plan or native handoff, and the relevant source owners and active constraints. Reuse the acceptance already supplied in the conversation or bead; clarify only what prevents action or judgment. To resume or replace another context, hand a slice on, plan code together with a requested retrospective, or keep an exact snapshot of conversation intent, follow resume and handoff.
- Route only the uncertainty that could change the slice (table below).
- Fill the block. A mechanical cross-cutting migration that cannot stay
working slice by slice uses expand, migrate, contract and states where
integration is required. Include recapture of affected bound evidence where
necessary; in repositories with AgentOps provenance bindings,
ao provenance evidence-orphansfinds it. Across an epic, Navigate picks the next bead; Plan shapes that bead. - When evidence disproves an approach, keep the failed assumption, its evidence and the revised check in the existing intent. An approach change within accepted outcome and scope needs no new permission; acceptance or scope expansion needs the caller. Never relabel a failed acceptance condition as a caveat to obtain green.
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.
Show full SKILL.md (385 more words)Show less
Route uncertainty
| Uncertainty | Next action |
|---|---|
| Fact a source can answer | Inspect the smallest authoritative source and cite it. Research owns deeper tracing; Domain owns disputed vocabulary. Never ask the caller to recite it. |
| Caller choice | Recover existing authorization first. What remains is the one question, with its concrete tradeoff; an agent cannot supply the caller's answer. |
| Assumption only an observation can settle | State the competing predictions and the smallest observation that separates them, using an optional probe or prototype. A persuasive design or an agent vote cannot settle unobserved behavior. |
| Safely deferred | Put it under Later with the event or evidence that would make it relevant. Deferral cannot hide an unanswered acceptance condition. |
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.
Who decides
Use real undo cost, affected users and existing authority. A material irreversible choice outside that authority goes to the caller; 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.
Examples and naming
An example can be plain text; BDD needs no .feature file or interview. In a
repository that calls queued work a Job:
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.
Write "Job", not a parallel label such as "task item". Keep the accepted example available to Implement and Validate; tests added after coding may supplement it but cannot redefine what was promised. For product planning, separate demonstrated behavior from aspiration; an ordinary feature needs no product document.
Scope
Use normalized repository-relative scope patterns. An uncovered live consumer needs a concise exact-file amendment to the caller; continue independent in-scope work meanwhile. Generated companions already in scope need no extra permission. Boundaries keep work and status in the caller's tracker and delivery under repository policy.
© boshu2, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (scripts, references) in skills/plan of boshu2/agentops.
- SKILL.md
- references/challenge.md
- references/ground-truth-routing.md
- references/plan.feature
- references/resume-and-handoff.md
- scripts/validate.sh
Open the folder on GitHubat commit 3bdbfed
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in boshu2/agentops, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan this skillboshu2/agentops | 447 | 1 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Langsmith ObservabilityOrchestra-Research/AI-Research-SKILLs | 13k | 3 repos | ~2.4k | Automated safety check: Pass | MIT | |
| ObservabilityBuilderIO/agent-native | 7.1k | — | ~7k | Automated safety check: Pass | None | |
| Frontend Observabilitysickn33/agentic-awesome-skills | 47k | 1 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Ebpf Observabilitysickn33/agentic-awesome-skills | 47k | 2 repos | ~3.3k | Automated safety check: Notes | MIT | |
| Python Observabilitywshobson/agents | 40k | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Observability
BuilderIO/agent-native
Agent observability, evals, feedback, and experiments. An agent skill from BuilderIO/agent-native.
Frontend Observability
sickn33/agentic-awesome-skills
A portable, framework-agnostic field-side observability system for any React or React Native app.
Ebpf Observability
sickn33/agentic-awesome-skills
Use eBPF for deep kernel-level observability — trace syscalls, network flows, and application behavior without code changes using Cilium, Tetragon, and bpftrace.
Python Observability
wshobson/agents
Python observability patterns including structured logging, metrics, and distributed tracing.
Observability Designer
alirezarezvani/claude-skills
Design production-ready observability strategies combining metrics, logs, and traces.
More from boshu2/agentops
All 31 skills in this repoAgent Native
boshu2/agentops
Dispatch independent tasks to parallel workers or subagents without write collisions.
Council
boshu2/agentops
Compare independent opinions from several models or contexts without inflating agreement.
Craft Goal
boshu2/agentops
Draft or lint a bounded long-running goal prompt with a finish line and hard limits.
Doc
boshu2/agentops
Write or update READMEs, docs, repo instructions and handoff notes, checked against source.
Idea Genie
boshu2/agentops
Brainstorm evidence-backed options for what to build, or stress-test an idea.
Implement
boshu2/agentops
Change or repair code, config or services without weakening tests; report what ran and what did not.
Questions about Plan
What does Plan do?
Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Plan is an agent skill from boshu2/agentops. Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions.
When should I use Plan?
Plan fits situations like: scoping a change.
How do I install Plan in Claude Code?
Run `npx skills add boshu2/agentops --skill plan -a claude-code`. Or copy the skill folder (skills/plan in boshu2/agentops) into .claude/skills/plan in your project. Claude Code loads it when a task matches its description.
How do I install Plan in Codex?
Run `npx skills add boshu2/agentops --skill plan -a codex`. Or copy the skill folder (skills/plan in boshu2/agentops) into .agents/skills/plan in your project. Codex loads it when a task matches its description.
Can I use Plan in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add boshu2/agentops --skill plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan, .gemini/skills/plan, .github/skills/plan and .opencode/skills/plan in your project.
What does Plan need to run?
Going by SKILL.md and its folder, Plan needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Plan access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Plan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Plan use?
Plan is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Plan use?
About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.
What are the alternatives to Plan?
Skills that share tags, products or a category with Plan: Langsmith Observability (Orchestra-Research/AI-Research-SKILLs, 13k stars), Observability (BuilderIO/agent-native, 7.1k stars), Frontend Observability (sickn33/agentic-awesome-skills, 47k stars) and Ebpf Observability (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan?
boshu2 (a GitHub user) maintains it in boshu2/agentops, which has 447 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.
Source: boshu2/agentops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.