spec-update
Skill2 starsChanged 6 days agoMITView on GitHub
DEPRECATED. Split into two more specific skills. Use retroactive_spec_update for code-as-evidence catch-up (existing specs drifted from code). Use spec_authoring for new specs or new sections that need Interview-based User-Intent clarification.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- HHU3637kr/skillstheir own version, first seen Sep 22, 2026
- wilsto/claude-code-starter-kittheir own version, first seen Mar 7, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- HHU3637kr/skills★ 146same name
- wilsto/claude-code-starter-kit★ 0same 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 repository78 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adversary-test-planSkill
- api-and-interface-designSkill
- architecture-coherence-reviewSkill
- cavemanSkill
- consistency-checkSkill
- cross-spec-consistency-checkSkill
- deprecation-and-migrationSkill
- documentation-and-adrsSkill
- frontend-design-ttySkill
- frontend-ui-engineeringSkill
- get-api-docsSkill
- impl-plan-reviewSkill
- improve-codebase-architectureSkill
- knowledge-captureSkill
- knowledge-processorSkill
- pre-build-spec-auditSkill
- retroactive-spec-updateSkill
- scopingSkill
- sectional-deep-reviewSkill
- session-diagnosisSkill
- shipping-and-launchSkill
- show-open-tasksSkill
- source-spec-reduceSkill
- spec-authoringSkill
- task-creationSkill
- task-status-updateSkill
- transparency-headerSkill
- ux-authoringSkill
- youtube-subtitlesSkill
- adversary-test-planSkill
- api-and-interface-designSkill
- architecture-coherence-reviewSkill
- bedrock-drillSkill
- bootSkill
- cavemanSkill
- close-retroSkill
- code-review-boardSkill
- consistency-checkSkill
- convergence-loopSkill
- councilSkill
- cross-spec-consistency-checkSkill
- deprecation-and-migrationSkill
- documentation-and-adrsSkill
- frameSkill
- frontend-design-ttySkill
- frontend-ui-engineeringSkill
- get-api-docsSkill
- impl-plan-reviewSkill
- improve-codebase-architectureSkill
- knowledge-captureSkill
- knowledge-processorSkill
- pre-build-spec-auditSkill
- python-code-quality-enforcementSkill
- retroactive-spec-updateSkill
- return-summarySkill
- risk-followup-routingSkill
- root-cause-fixSkill
- scopingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 43
Do not use this skill. Pick the right successor from the table above.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: spec-update (DEPRECATED)
This skill was an early draft that conflated two different use cases:
- Retroactive catch-up: Code evolved, spec drifted, sync needed.
- Feature addition to existing spec: New functionality documented.
These are structurally different workflows — (1) has the code as evidence and needs no User-Intent interview, (2) requires an Interview-based clarification because the User-Intent is not yet captured anywhere.
Replacement
| Old use case | New skill |
| Retroactive catch-up | skills/retroactive_spec_update/SKILL.md |
| Feature addition to existing spec (needs Interview) | skills/spec_authoring/SKILL.md (§"Wann aufrufen" covers this) |
| Cross-spec consistency post-amendment | skills/spec_amendment_verification/SKILL.md |
| Spec quality review | skills/spec_board/SKILL.md |
Why deprecated
The skill had one phase labeled "Write entlang 5 Primitives" but the input to that phase was ambiguous — sometimes git log (retroactive), sometimes user-intent (feature addition). The two inputs require different workflows (code walkthrough vs interview), so splitting into two skills is cleaner.
Do not use this skill. Pick the right successor from the table above.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.