openspec-apply-change
Skill1.1k starsChanged 26 days agoLicence not identifiedView on GitHub
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. Also use when the user says "openspec apply", "opsx apply", or "openspec implement".
149 other projects use a version of this, 139 of them edited.
Trending
More talk lately.thin dataabout the whole repository
Most recently taken up by
- ValorVie/custom-skillsedited, first seen Nov 8, 2026
- full-stack-skills/electron-skillsedited, first seen Nov 8, 2026
- halo-dev/plugin-ai-foundationedited, first seen Nov 8, 2026
- ptonlix/OneSelfedited, first seen Nov 8, 2026
- FuDesign2008/open-skillsedited, first seen Nov 6, 2026
- feimacode/open-design-agent-kitedited, first seen Nov 6, 2026
Who's talking about jamro/tiny-engineer
The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.
Used with
Projects with it also use source-command-opsx-apply, source-command-opsx-archive and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
antech2-asyncSkillsource-command-opsx-apply
Implement tasks from an OpenSpec change (Experimental)
Also in 5 projects that use this
- antech2-asyncSkill
source-command-opsx-archive
Archive a completed change in the experimental workflow
Also in 5 projects that use this
ElasticSkillopenspec-continue-change
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
Also in 62 projects that use this
MicrosoftSkillopenspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Also in 58 projects that use this
- MicrosoftSkill
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
Also in 55 projects that use this
- ElasticSkill
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
Also in 62 projects that use this
- +2 more from antech2-async
- +1 more from microsoft
Other versions149 projects use a version of this.
Word for word · 4
- epam/ai-dial-core★ 663100% same
- vicharanashala/vibe★ 111100% same
- ECG-Rudy-Glt/RELAI★ 2100% same
- ndthanhdev/aio★ 1100% same
Edited · 139
- Fission-AI/OpenSpec★ 74k98% same
- halo-dev/halo★ 40k85% same
- alibaba/druid★ 28k80% same
- databasus/databasus★ 9.3k83% same
- RostislavDugin/postgresus★ 9.3k83% same
- fonoster/fonoster★ 8.2k77% same
- fleetdm/fleet★ 7.2k82% same
- PBH-BTN/PeerBanHelper★ 6.4k78% same
- KunAgent/Kun★ 6.4k82% same
- XingYu-Zhong/DeepSeek-GUI★ 6.4k82% same
129 more not listed
Wrote their own version · 6
- studyzy/imewlconverter★ 10ksame name
- studyzy/OpenSpec-cn★ 1.3ksame name
- henhen6/mdp★ 133same name
- charliehzm/medharness★ 85same name
- beautifulSoup/speccoding-template★ 62same name
- redhat-developer/rhdh-skills★ 20same 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/compile-after-changes.mdcCursor rule
- .cursor/rules/conventional-commits.mdcCursor rule
- .cursor/rules/sync-api-endpoints.mdcCursor rule
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
- easyeda-to-kicadSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
- verify-jlcpcb-bomSkill
- tiny-engineer-playSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
30 rules. 12 are common, 6 are distinctive, and 12 are very specific to this project.
12
Common
Most of the 141 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 141 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.
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.