implementation-strategy Skill
Choose compatibility-aware scope for runtime and API changes in openai-agents-js. Use before initial implementation and each review-feedback batch to decide whether to patch, reset the design, preserve compatibility, or reject unsupported cases. Published by openai in openai-agents-js.
Decision snapshot
Is this a fit?
Documentation, Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
28 days ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is implementation-strategy Skill?
Choose compatibility-aware scope for runtime and API changes in openai-agents-js. Use before initial implementation and each review-feedback batch to decide whether to patch, reset the design, preserve compatibility, or reject unsupported cases. Published by openai in openai-agents-js. 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. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Design and media
- Documentation use cases
- Design and media use cases
Declared skill metadata
- Source file: .agents/skills/implementation-strategy/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use implementation-strategy Skill
- Use it for documentation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/openai-agents-js
- Skill file: .agents/skills/implementation-strategy/SKILL.md
What it does
Choose compatibility-aware scope for runtime and API changes in openai-agents-js. Use before initial implementation and each review-feedback batch to decide whether to patch, reset the design, preserve compatibility, or reject unsupported cases.
Skill instructions
Implementation Strategy Workflow 1. Identify the surface you are changing or reviewing: 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 tag to use as the compatibility baseline 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" Report a local-tag fallback as potentially stale. 3. Record the implementation scope contract below before coding. 4. Identify the nearest existing implementation pipeline and the functions, types, or modules that are the source of truth for each affected concern. Prefer adapting the required input into that pipeline over creating parallel schema, metadata, validation, identity, conversion, or execution machinery. 5. Choose the sma
Verified compatibility and discovery
Frequently asked questions
What is implementation-strategy?
implementation-strategy is a open-source AI agent skill with Copy skill directory. Choose compatibility-aware scope for runtime and API changes in openai-agents-js.
Who is implementation-strategy best for?
implementation-strategy is best for reusing agent instructions, scripts, and references, documentation workflows, design and media 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.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
