sync-design
Skill0 starsChanged 8 months agoMITView on GitHub
Procedure for reverse-syncing architectural changes from a completed/blocked task back into the Design document.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sahildave/skilltopiatheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sahildave/skilltopia★ 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 repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- code-reviewSkill
- cpp-opencl-devSkill
- design-creationSkill
- gradingSkill
- readme-creationSkill
- sync-readmeSkill
- task-creationSkill
- technical-auditSkill
- ux-reviewSkill
- validate-dodSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read the Task: Read the specified task file in workflow/tasks/.
- Very specific: line 10
Read the Design: Read the parent workflow/design/design_[module].md.
- Distinctive: line 12
If the task required a change in architecture, update the "Key Decisions and Rationale" section in the Design doc.
- Distinctive: line 13
If the task failed due to a limitation, add it to the "Known Issues & Risks" section.
- Distinctive: line 14
Update the "Roadmap & Status" checkboxes accordingly.
- Distinctive: line 15
Save: Write the changes securely to the Design document.
≈ “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
Sync Design (Reverse Update) Skill
Instructions
- Read the Task: Read the specified task file in
workflow/tasks/. Look closely at the "Execution Report", "Status", and any notes about blockers or required architectural changes. - Read the Design: Read the parent
workflow/design/design_[module].md. - Apply the Pivot/Evolution:
- If the task required a change in architecture, update the "Key Decisions and Rationale" section in the Design doc.
- If the task failed due to a limitation, add it to the "Known Issues & Risks" section.
- Update the "Roadmap & Status" checkboxes accordingly.
- Save: Write the changes securely to the Design document.
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.