to-spec
Skill2 starsChanged 10 days agoMITView on GitHub
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
223 other projects use a version of this, 102 of them edited; 45 of 100 edited versions we compared changed its rules; 9 new projects in the last 4 weeks, against 10 the 4 before.
How people change it
45 of 100 edited versions changed its rules, and some changes recur.
Of the 100 edited versions we compared: 54 keep every rule, 1 is an older text, 45 made changes of their own.
Not in older versions
- Write the spec using the template below, then publish it to the project issue tracker. Apply the
ready-for-agenttriage label - no need for additional triage.missing from 1 of 1
Rules people drop
- Write the spec using the template below, then publish it to the project issue tracker. Apply the
ready-for-agenttriage label - no need for additional triage.dropped by 36 of 45 - Check with the user that these seams match their expectations.dropped by 18 of 45
- Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.dropped by 8 of 45
Rules people add
- A rule we can't quote: its licence doesn't allow itadded by 4 of 45
- A rule we can't quote: its licence doesn't allow itadded by 2 of 45
- A rule we can't quote: its licence doesn't allow itadded by 2 of 45
- Write the spec using the template below, then publish it to the project issue tracker.added by 2 of 45
- A rule we can't quote: its licence doesn't allow itadded by 2 of 45
- No tracker configured (no MCP server, or the IDs are blank): write the spec to
docs/plans/<feature-slug>/spec.mdinstead, creating the directory if needed.docs/plans/is local-only;scripts/pre-commitrefuses to commit it.added by 2 of 45 - Write the spec using the template below, then publish it: on a tracker,
mcp__linear-server__save_issuewith the spec as the markdown body and the spec label applied; otherwise the local file above.added by 2 of 45 - A rule we can't quote: its licence doesn't allow itadded by 2 of 45
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Steady: 9 new projects took it in the last 4 weeks, 0.9× the 4 weeks before.
Most recently taken up by
- bamlab/flashlightword for word, first seen Nov 16, 2026
- moisesrj97/skillsedited, first seen Nov 16, 2026
- endalk200/skillsedited, first seen Nov 16, 2026
- atiq-r/skillsedited, first seen Nov 16, 2026
- gfunc/skillsedited, first seen Nov 16, 2026
- devdeepjs/kobayashi-maruword for word, first seen Nov 16, 2026
Used with
Projects with it also use setup-ts-deep-modules, loop-me and 6 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.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 49 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 56 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 59 projects that use this
richard12511Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 45 projects that use this
LesaniSkillwriting-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
Also in 56 projects that use this
simo97Skillmigrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Also in 53 projects that use this
- +1 more from Lesani
Other versions223 projects use a version of this.
Word for word · 84
- mattpocock/skills★ 325k100% same
- The-Vibe-Company/quivr★ 40k100% same
- QuivrHQ/quivr★ 40k100% same
- formbricks/formbricks★ 13k100% same
- ArcReel/ArcReel★ 6.6k100% same
- withcoral/coral★ 5k100% same
- bamlab/flashlight★ 1.6k100% same
- moeru-ai/xsai★ 669100% same
- aws/graph-explorer★ 492100% same
- biersoeckli/QuickStack★ 367100% same
74 more not listed
Edited · 102
- vinvcn/mattpocock-skills-zh-CN★ 5.8k18% same
- bestofjs/bestofjs★ 3.1k98% same
- nodetool-ai/nodetool★ 63749% same
- hcloud-talos/terraform-hcloud-talos★ 36498% same
- loulanyue/skills★ 23196% same
- tt-a1i/matt-skills-with-to-goal★ 19271% same
- rengwu/wayfinder-maps★ 13775% same
- Dimon94/dverity★ 10749% same
- Dimon94/skills★ 10749% same
- HarryMtv/create-frontstack★ 10396% same
92 more not listed
Wrote their own version · 37
- DanMcInerney/architect-loop★ 626same name
- stevesolun/ctx★ 583same name
- devcxl/mattpocock-skills-zh★ 543same name
- blockscout/frontend★ 310same name
- Integralist/agent-skills★ 29same name
- helderberto/agent-skills★ 19same name
- assisjp/specflow★ 17same name
- GulajavaMinistudio/polya-sdlc-coder★ 16same name
- mhmzdev/hisab-whatsapp★ 9same name
- flpbalada/fb-skills★ 8same name
27 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 repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- site/llms.txtllms.txt
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- setup-matt-pocock-skillsSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 2 are common, 0 are distinctive, and 1 is very specific to this project.
2
Common
Most of the 127 edited versions we read keep these.
0
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
- Common: line 17
Check with the user that these seams match their expectations.
- Very specific: line 19
Write the spec using the template below, then publish it to the project issue tracker.
- Common: line 55
Do NOT include specific file paths or code snippets.
“Common” is measured: kept by at least 6 in 10 of the 127 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
This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know.
The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.
Process
- Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
- Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
Check with the user that these seams match their expectations.
- Write the spec using the template below, then publish it to the project issue tracker. Apply the
ready-for-agenttriage label - no need for additional triage.
<spec-template>Problem Statement
The problem that the user is facing, from the user's perspective.
Solution
The solution to the problem, from the user's perspective.
User Stories
A LONG, numbered list of user stories. Each user story should be in the format of:
- As an
<actor>, I want a<feature>, so that<benefit>
<user-story-example>
1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
</user-story-example>This list of user stories should be extremely extensive and cover all aspects of the feature.
Implementation Decisions
A list of implementation decisions that were made. This can include:
- The modules that will be built/modified
- The interfaces of those modules that will be modified
- Technical clarifications from the developer
- Architectural decisions
- Schema changes
- API contracts
- Specific interactions
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.
Testing Decisions
A list of testing decisions that were made. Include:
- A description of what makes a good test (only test external behavior, not implementation details)
- Which modules will be tested
- Prior art for the tests (i.e. similar types of tests in the codebase)
Out of Scope
A description of the things that are out of scope for this spec.
Further Notes
Any further notes about the feature.
</spec-template>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.

