trellis-spec-bootstrap
Skill2 starsChanged 26 days agoMITView on GitHub
Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.
17 other projects use a version of this, 1 of them edited; 2 new projects in the last 4 weeks, against 1 the 4 before.
Adopted by
Rising: 2 new projects took it in the last 4 weeks, 2× the 4 weeks before.thin data
Most recently taken up by
- phoben/agent-skillsedited, first seen Nov 8, 2026
- vibex-ai/vibexword for word, first seen Nov 8, 2026
- mipawn/cc-useword for word, first seen Nov 1, 2026
- deequoique/stashseekword for word, first seen Oct 20, 2026
- zhexin233-ui/easytoagentsword for word, first seen Oct 11, 2026
- CharTyr/STS2-Agentword for word, first seen Oct 8, 2026
Other versions17 projects use a version of this.
Word for word · 16
- mindfold-ai/Trellis★ 15k100% same
- EcoPasteHub/EcoPaste★ 7.5k100% same
- QiaoKes/fntv-electron★ 1.3k100% same
- CharTyr/STS2-Agent★ 357100% same
- hsingjui/ContextWeaver★ 295100% same
- fy-agent/fyagent★ 218100% same
- vibex-ai/vibex★ 70100% same
- deequoique/stashseek★ 58100% same
- mipawn/cc-use★ 9100% same
- xhl592576605/agent-skills-mesh★ 8100% same
6 more not listed
Edited · 1
- phoben/agent-skills★ 096% same
Wrote their own version · 0
None found.
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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- source-command-trellis-continueSkill
- source-command-trellis-finish-workSkill
- trellis-before-devSkill
- trellis-brainstormSkill
- trellis-break-loopSkill
- trellis-channelSkill
- trellis-checkSkill
- trellis-continueSkill
- trellis-finish-workSkill
- trellis-metaSkill
- trellis-session-insightSkill
- trellis-startSkill
- trellis-update-specSkill
- trellis-before-devSkill
- trellis-brainstormSkill
- trellis-break-loopSkill
- trellis-channelSkill
- trellis-checkSkill
- trellis-metaSkill
- trellis-session-insightSkill
- trellis-spec-bootstrapSkill
- trellis-update-specSkill
- delegate-with-codedeckSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 16
Verify that the final specs are internally consistent and contain no template placeholders.
- Distinctive: line 29
Treat templates as starting points, not contracts.
- Distinctive: line 30
Prefer source-backed rules over generic advice.
- Distinctive: line 31
Keep execution single-owner by default.
- Distinctive: line 32
Do not write platform-specific instructions unless the target project already standardizes on that platform.
- Very specific: line 33
Do not leave placeholder text, empty headings, or copied boilerplate in .trellis/spec/.
≈ “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
Trellis Spec Bootstrap
Use this skill to create or refresh .trellis/spec/ guidelines from the real codebase. One capable agent owns the full loop: analyze the repository, choose the spec boundaries, write the docs, and verify the result. The workflow does not depend on a specific host, CLI, or agent brand.
Workflow
- Confirm Trellis is initialized and inspect the current
.trellis/spec/tree. - Analyze the repository architecture with the best available tools: GitNexus, ABCoder, language tooling, and direct source reads.
- Decompose the spec work by package and layer only when that reflects the actual codebase.
- Fill or reshape the spec files with concrete patterns, file paths, examples, and anti-patterns from the project.
- Verify that the final specs are internally consistent and contain no template placeholders.
Reference Routing
| Need | Read |
| Repository architecture analysis | references/repository-analysis.md |
| Spec work decomposition and task planning | references/spec-task-planning.md |
| Writing high-signal Trellis spec files | references/spec-writing.md |
| GitNexus and ABCoder MCP setup | references/mcp-setup.md |
Operating Rules
- Treat templates as starting points, not contracts. Delete, rename, split, or add spec files when the repository calls for it.
- Prefer source-backed rules over generic advice. Every important recommendation should point at a real file or repeated local pattern.
- Keep execution single-owner by default. Optional helper agents are an implementation detail, not a requirement or user-visible dependency.
- Do not write platform-specific instructions unless the target project already standardizes on that platform.
- Do not leave placeholder text, empty headings, or copied boilerplate in
.trellis/spec/.
Done Criteria
.trellis/spec/describes the project as it exists now.- Each relevant package or layer has practical coding guidance with real examples.
- Non-applicable template sections are removed.
index.mdfiles match the final spec file set.- Any required setup or analysis assumptions are documented in the relevant spec or task notes.
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.