to-spec
Skill1 starsChanged yesterdayMITView 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.
195 other projects use a version of this, 157 of them edited.
Adopted by
Most recently taken up by
- bamlab/flashlightedited, 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-maruedited, first seen Nov 16, 2026
Used with
Projects with it also use setup-ts-deep-modules, to-questionnaire 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.
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
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 103 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
AWSSkillimplement-spec
Implement the result of /to-spec and /to-tickets in code.
Also in 89 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
- +2 more from aws
Other versions195 projects use a version of this.
Word for word · 1
- lutzseverino/repo-standards★ 0100% same
Edited · 157
- mattpocock/skills★ 325k89% same
- The-Vibe-Company/quivr★ 40k89% same
- QuivrHQ/quivr★ 40k89% same
- formbricks/formbricks★ 13k89% same
- ArcReel/ArcReel★ 6.6k89% same
- vinvcn/mattpocock-skills-zh-CN★ 5.8k18% same
- withcoral/coral★ 5k89% same
- bestofjs/bestofjs★ 3.1k90% same
- bamlab/flashlight★ 1.6k89% same
- moeru-ai/xsai★ 66989% same
147 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- babysitSkill
- codebase-designSkill
- code-reviewSkill
- create-adopted-repoSkill
- create-repositorySkill
- diagnosing-bugsSkill
- domain-modelingSkill
- factorySkill
- grillingSkill
- grill-with-docsSkill
- implementSkill
- improve-codebase-architectureSkill
- orchestrateSkill
- prototypeSkill
- prSkill
- repository-standardsSkill
- researchSkill
- retroSkill
- reviewSkill
- tddSkill
- to-ticketsSkill
- triageSkill
- wayfinderSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 1 is common, 2 are distinctive, and 1 is very specific to this project.
1
Common
Most of the 182 edited versions we read keep these.
2
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 21
Before proposing an unanswered decision, read and apply the contribution guide's Triage inference test, inferred-list and owner-question …
- Distinctive: line 24
Write the spec using the template below.
- Common: line 74
Do NOT include specific file paths or code snippets.
- Very specific: line 115
If missing, use grilling's missing-guide fallback, independent exact-revision review and the tracker rules provided.
“Common” is measured: kept by at least 6 in 10 of the 182 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
A prompt or brief naming this skill is its invocation.
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.
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.
Reuse recorded test-seam decisions and plan approval with their dates and quoted words. Gather missing code facts and record seam evidence for review. Before proposing an unanswered decision, read and apply the contribution guide's Triage inference test, inferred-list and owner-question rules.
- Write the spec using the template below. Copy every relied-on owner decision
with its date and quoted words into the issue-facing contract; private records
are not required inputs. Publish one specification issue in the repository
containing most of the work, reading
.repo-standards/rules/comments.md#disclaimersfirst on a hosted tracker. Cross-repository tickets remain children of that one specification. Use the guide's direct-body-contract publication route. Return the exact published contract and factual/test-seam evidence to the orchestrating agent for its split decision and acceptance under the guide's Triage and Readiness sections and the installed parent-readiness rules.
Return the published specification's link and exact revision to the caller, which starts or resumes its ticket-publication step. For an amendment under the guide's Triage rules, consume the amendment grill's decisions, revise the specification and return its link and revision for the caller's delta-ticket step and the guide's acceptance process.
<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>Reads
Paths are relative to the repository root.
docs/agents/issue-tracker.mdanddocs/agents/triage-labels.md: the issue tracker and its triage label vocabulary. When the tracker config is missing and no tracker was provided, ask the user where to publish the spec; when the label config is missing, use the canonical role names as the label strings..repo-standards/rules/comments.md: the installed comment rules, whose section the posting steps name. When it is missing, post issue bodies and comments as the steps describe.GLOSSARY.mdand the ADRs indocs/adr/: the domain vocabulary and decisions to respect. When either is missing, use the codebase's own words.- The installed rules, such as the
github-repository-configurationrules, which therepository-standardsskill looks up: the companion labels readiness needs. When they are missing, readiness carries no companion labels. CONTRIBUTING.md: Triage inference, publication, amendments and readiness. If missing, usegrilling's missing-guide fallback, independent exact-revision review and the tracker rules provided; route unresolved owner choices to the user without repeating recorded answers.- The
grillingskill: the inference fallback, only when the contribution guide is missing. If also missing, report it and stop for the missing policy.
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.

