implementation-strategy Skill
Decide how to implement runtime and API changes in openai-agents-python before editing code. Use when a task changes exported APIs, runtime behavior, serialized state, tests, or docs and you need to choose the compatibility boundary, whether shims or migrations are warranted, and when unreleased interfaces can be rewri Published by openai in openai-agents-python.
What is implementation-strategy Skill?
Decide how to implement runtime and API changes in openai-agents-python before editing code. Use when a task changes exported APIs, runtime behavior, serialized state, tests, or docs and you need to choose the compatibility boundary, whether shims or migrations are warranted, and when unreleased interfaces can be rewri Published by openai in openai-agents-python. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use implementation-strategy Skill
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/openai-agents-python
- Skill file: .agents/skills/implementation-strategy/SKILL.md
What it does
Decide how to implement runtime and API changes in openai-agents-python before editing code. Use when a task changes exported APIs, runtime behavior, serialized state, tests, or docs and you need to choose the compatibility boundary, whether shims or migrations are warranted, and when unreleased interfaces can be rewri
Skill instructions
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 1. Identify the surface you are changing: released public API, unreleased branch-local API, internal helper, persisted schema, wire protocol, CLI/config/env surface, or docs/examples only. 2. Determine the latest release boundary from origin first, and only fall back to local tags when remote tags are unavailable: bash BASETAG="$(.agents/skills/final-release-review/scripts/findlatestreleasetag.sh origin 'v' 2/dev/null || git tag -l 'v' --sort=-v:refname | head -n1)" echo "$BASETAG" 3. Judge breaking-change risk against that latest release tag, not against unreleased branch churn or post-tag changes already on main. If the command fell back to local tags, treat the result as potentially stale and say so. 4. Prefer the simplest im
Explore related resources
Frequently asked questions
What is implementation-strategy?
implementation-strategy is a open-source AI agent skill with Copy skill directory. Decide how to implement runtime and API changes in openai-agents-python before editing code.
Who is implementation-strategy best for?
implementation-strategy is best for reusing agent instructions, scripts, and references, documentation workflows.
How do I install implementation-strategy?
Install or run implementation-strategy using Copy skill directory. Check implementation-strategy for the latest setup command.
Is implementation-strategy actively maintained?
implementation-strategy may need a closer maintenance check before production use.
Auto-fetched from GitHub.
