Trellis Spec Bootstrap
SkillAI & modelsThis skill lets your AI create or refresh coding guidelines for your project based on how the code actually works. It analyzes your codebase and writes spec documents that reflect real code, kept as .trellis/spec guidelines. Use it when starting a new project's guidelines or updating existing ones.
Available today. Use it from your connected AI after setup.
No other account needed.
Add the skill, then ask your AI to create or refresh your project's coding guidelines. It will analyze the codebase and write the spec docs for you.
Then ask your AI: use the Trellis Spec Bootstrap skill
What your AI can do with it
- Create or refresh project coding guidelines in .trellis/spec
- Analyze a codebase using GitNexus, ABCoder, or direct source inspection
- Write spec documents backed by real code from the project
- Break spec work down by package or layer
- Run as a single-agent workflow that is not tied to one platform
What this skill tells your AI
The instructions your AI receives, as published by fy-agent/fyagent in .agents/skills/trellis-spec-bootstrap/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 1k
- Forks
- 133
- Last commit
- Sep 2026
ahel review
K1binfo
installs-packages (in references/mcp-setup.md)
Automated review, not a security audit. Ruleset v1+k2.
Others that do the same job
Advanced
- Catalog kind
- skill
- Gateway key
trellis-spec-bootstrap- Source
- github.com/fy-agent/fyagent