spec
Skill0 starsChanged 35 days agoApache-2.0View on GitHub
How to turn an idea into an agreed design before any code — clarify, explore approaches, write the spec, get approval.
173 other projects use a version of this.
Adopted by
Most recently taken up by
- chrisezedi/claude-skillstheir own version, first seen Nov 16, 2026
- ByteLab-dev-ar/skills-proyectostheir own version, first seen Nov 16, 2026
- devonbweaver/Spec-Looptheir own version, first seen Nov 16, 2026
- pushkincode/skillstheir own version, first seen Nov 16, 2026
- timursafiullin/aodtheir own version, first seen Nov 15, 2026
- RohiRIK/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use backprop, ios-clean and 10 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.
JuliusBrusseeSkillbackprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.
Also in 4 projects that use this
Saqlain-811Skillios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
Saqlain-811Skillios-fix
Autonomous iOS bug fixer. (gstack)
Also in 5 projects that use this
bastosSkillios-design-review
Review iOS app UI/UX design quality using Apple's design principles and the Liquid Glass-era design language from WWDC25/26. Use when asked for a design review, UX critique, visual design assessment, or evaluation of an app's interface quality, design intent, alignment with the new Apple design system, or usability. Triggers: "design review", "UX review", "visual design critique", "review the UI", "does this design work", "evaluate this interface", "design feedback", "Liquid Glass review".
Also in 5 projects that use this
ShreyRaviSkillplan-tune
Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.
Also in 7 projects that use this
timurgaleevSkilldocument-generate
Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.
Also in 6 projects that use this
- +2 more from Saqlain-811
Other versions173 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 173
- garrytan/gstack★ 142ksame name
- getsentry/sentry-react-native★ 1.8ksame name
- JuliusBrussee/cavekit★ 1.1ksame name
- kdlbs/kandev★ 1.1ksame name
- getsentry/sentry-dart★ 877same name
- poshan0126/dotclaude★ 871same name
- codewithmukesh/dotnet-claude-kit★ 808same name
- SparkDevNetwork/Rock★ 701same name
- strands-agents/box★ 547same name
- hyperlink-academy/leaflet★ 527same name
163 more not listed
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 repository21 other files it gives its agents.
- browserbaseSkill
- cairnSkill
- developmentSkill
- dispatchSkill
- house-styleSkill
- kimi-subagentSkill
- lean-design-standardSkill
- mergeSkill
- nexus-authSkill
- nexus-jiraSkill
- orchestrateSkill
- orchestratorSkill
- planningSkill
- releaseSkill
- remote-opsSkill
- reviewSkill
- securitySkill
- ticket-pipelineSkill
- vision-reviewSkill
- workflow-basicsSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 149 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Ask clarifying questions one at a time.
- Distinctive: line 14
If the request is really several subsystems, say so and decompose before designing.
- Very specific: line 17
Write the spec to docs/YYYY-MM-DD-<topic>-design.md and commit it.
- Distinctive: line 19
Ask the operator to review the written spec.
- Distinctive: line 24
After the spec is approved, load the planning skill.
“Common” is measured: kept by at least 6 in 10 of the 149 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.
Files
spec
Design before you build. Do not write code or scaffold anything until a design is written and the operator has approved it. This holds even when the task looks simple — simple tasks are where unexamined assumptions waste the most work.
Steps
- Explore the context first. Read the relevant files, docs, recent commits.
- Ask clarifying questions one at a time. Prefer multiple-choice. Cover purpose, constraints, success criteria.
- If the request is really several subsystems, say so and decompose before designing.
- Propose 2–3 approaches with trade-offs. Lead with your recommendation and why.
- Present the design in sections. Get the operator's approval before moving on.
- Write the spec to
docs/YYYY-MM-DD-<topic>-design.mdand commit it. - Self-review the spec: no TBD/placeholders, no contradictions, no ambiguity, single focused scope. Fix inline.
- Ask the operator to review the written spec. Only proceed when they approve.
Rules
- The operator is a peer. Don't survey endlessly — recommend.
- Skip the visual companion; this team is CLI-first.
- After the spec is approved, load the planning skill.
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.

