implementation-strategy
Skill2 starsChanged 7 months agoMITView on GitHub
Decide how to implement runtime and API changes before editing code. Use when a task changes exported APIs, MCP tool definitions, runtime behavior, or configuration, and you need to choose the compatibility boundary and implementation shape.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- py-econometrics/pyfixesttheir own version, first seen Oct 8, 2026
- openai/openai-guardrails-jstheir own version, first seen Sep 10, 2026
- openai/openai-agents-pythontheir own version, first seen Sep 8, 2026
- openai/openai-guardrails-pythontheir own version, first seen Aug 25, 2026
- xavigiro5ta/agentops-governance-templatetheir own version, first seen Jun 12, 2026
- openai/openai-agents-jstheir own version, first seen Feb 3, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- openai/openai-agents-python★ 31ksame name
- openai/openai-agents-js★ 4ksame name
- py-econometrics/pyfixest★ 363same name
- openai/openai-guardrails-python★ 265same name
- openai/openai-guardrails-js★ 113same name
- xavigiro5ta/agentops-governance-template★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-mcp-serverSkill
- code-change-verificationSkill
- docs-syncSkill
- pr-draft-summarySkill
- typescriptSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill before editing code when the task changes runtime behavior or anything that might look like a compatibility concern.
- Distinctive: line 20
Prefer the simplest implementation.
- Distinctive: line 21
Add a compatibility layer only when there is a concrete released consumer or the user explicitly asks for a migration path.
- Distinctive: line 28
Internal helpers, private types, tests, and fixtures: update directly.
- Distinctive: line 32
Prefer deletion or replacement over shims and feature flags when the old shape is unreleased.
- Distinctive: line 33
Do not preserve a confusing abstraction just because it exists in the current branch diff.
- Distinctive: line 34
If a change truly crosses the latest released contract boundary, call that out explicitly.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Implementation Strategy
Overview
Use this skill before editing code when the task changes runtime behavior or anything that might look like a compatibility concern. The goal is to keep implementations simple while protecting real released contracts.
Quick start
- Identify the surface you are changing: released MCP tool API, unreleased branch-local API, internal helper, configuration surface, or docs only.
- Determine the latest release boundary:
git tag -l 'v*' --sort=-v:refname | head -n1 - Judge breaking-change risk against that latest release tag, not against unreleased branch churn.
- Prefer the simplest implementation. Update callers, tests, and docs directly instead of preserving superseded unreleased interfaces.
- Add a compatibility layer only when there is a concrete released consumer or the user explicitly asks for a migration path.
Compatibility boundary rules
- Released MCP tool API or documented external behavior: preserve compatibility or provide an explicit migration path.
- Configuration, environment variables, and externally consumed settings: treat as compatibility-sensitive when part of the latest release.
- Interface changes on the current branch or after the latest release tag: not a compatibility target. Rewrite directly.
- Internal helpers, private types, tests, and fixtures: update directly.
Default implementation stance
- Prefer deletion or replacement over shims and feature flags when the old shape is unreleased.
- Do not preserve a confusing abstraction just because it exists in the current branch diff.
- If a change truly crosses the latest released contract boundary, call that out explicitly.
When to stop and confirm
- The change would alter behavior shipped in the latest release tag.
- The change would modify MCP tool schemas that clients depend on.
- The user explicitly asked for backward compatibility or migration support.
Output
State the decision briefly:
Compatibility boundary: latest release tag v0.x.y; branch-local interface rewrite, no shim needed.Compatibility boundary: released tool schema; preserve compatibility and add migration path.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.