spec
Skill27 starsChanged 8 months agoApache-2.0View on GitHub
Write a comprehensive product or engineering specification before implementation. Use when the user asks for `/spec`, PRDs, feature specs, API specs, refactor specs, acceptance criteria, user stories, edge cases, or open decision tracking before code is written.
168 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- varelaia/claude-skills-publictheir own version, first seen Nov 8, 2026
- mrlemoos/galiciatheir own version, first seen Nov 8, 2026
- PeanutGT/NutsSkillstheir own version, first seen Nov 8, 2026
- standardagents/skillstheir own version, first seen Nov 8, 2026
- Surething-io/cockpittheir own version, first seen Nov 8, 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-811Skill
ios-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 versions168 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 168
- garrytan/gstack★ 141ksame name
- getsentry/sentry-react-native★ 1.8ksame name
- JuliusBrussee/cavekit★ 1.1ksame name
- kdlbs/kandev★ 1.1ksame name
- getsentry/sentry-dart★ 878same name
- poshan0126/dotclaude★ 871same name
- codewithmukesh/dotnet-claude-kit★ 808same name
- SparkDevNetwork/Rock★ 701same name
- hyperlink-academy/leaflet★ 527same name
- strands-agents/box★ 503same name
158 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 repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- webapp-testingSkill
- env-hubSkill
- mcp-builderSkill
- mintlify-docs-updaterSkill
- reviewSkill
- shipSkill
- skill-creatorSkill
- internal-commsSkill
- ml-failure-auditSkill
- changelog-generatorSkill
- algorithmic-artSkill
- canvas-designSkill
- instagram-reel-editorSkill
- remotionSkill
- slack-gif-creatorSkill
- ab-test-setupSkill
- copywritingSkill
- humanizerSkill
- instagram-postingSkill
- marketing-ideasSkill
- seo-auditSkill
- claude-for-legalSkill
- contract-review-risk-scoringSkill
- doc-coauthoringSkill
- docxSkill
- legal-work-pluginSkill
- pdfSkill
- pptxSkill
- xlsxSkill
- pm-skillsSkill
- resume-tailoringSkill
- last30daysSkill
- brand-guidelinesSkill
- excalidrawSkill
- frontend-designSkill
- open-designSkill
- theme-factorySkill
- web-artifacts-builderSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 145 edited versions we read keep these.
3
Distinctive
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 10
Use this skill to turn a feature, API, refactor, or product idea into a clear specification that can feed planning and implementation.
- Distinctive: line 20
Keep the spec implementation-aware but avoid over-prescribing internal code structure unless required.
- Distinctive: line 24
Use this structure by default:
“Common” is measured: kept by at least 6 in 10 of the 145 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
Overview
Use this skill to turn a feature, API, refactor, or product idea into a clear specification that can feed planning and implementation. The output should reduce ambiguity before code is written.
Workflow
- Identify the problem, goal, users, constraints, and non-goals.
- Capture the current behavior or system context when relevant.
- Define user stories or use cases with acceptance criteria.
- Specify functional requirements, edge cases, error states, permissions, and data handling.
- Include API, UI, migration, observability, performance, or rollout requirements when applicable.
- List open decisions and assumptions explicitly.
- Keep the spec implementation-aware but avoid over-prescribing internal code structure unless required.
Output Pattern
Use this structure by default:
- Summary.
- Problem statement.
- Goals and non-goals.
- Users and use cases.
- Requirements.
- Acceptance criteria.
- Edge cases and risks.
- Observability, rollout, and rollback notes.
- Open questions.
Example Prompts
/spec - Build a CSV export feature for our analytics dashboard. Users need to export filtered data with custom date ranges. Support up to 100k rows./spec - Design a public webhooks API for our platform. Third-party apps need to subscribe to user events and receive payloads reliably with retry logic./spec - Refactor our authentication flow to support SSO. We need to keep existing email/password working and add Google and GitHub OAuth without breaking current sessions.
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.