trellis-spec-bootstrap
Generates codebase-backed coding guidelines and specifications for project-specific needs.
Install
mkdir -p .claude/skills/trellis-spec-bootstrap && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16602" && unzip -o skill.zip -d .claude/skills/trellis-spec-bootstrap && rm skill.zipInstalls to .claude/skills/trellis-spec-bootstrap
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Create or refresh `.trellis/spec/` guidelines
- →Analyze repository architecture with available tools
- →Decompose spec work by package and layer
- →Fill spec files with concrete patterns and examples from the project
- →Verify internal consistency of final specs
- →Ensure no placeholder text remains in `.trellis/spec/`
How it works
This skill bootstraps project-specific Trellis coding specs by analyzing the repository architecture, decomposing spec work, and populating spec files with concrete patterns and examples derived from the codebase. It ensures the specs are consistent and free of placeholders.
Inputs & outputs
When to use trellis-spec-bootstrap
- →Initializing new project spec guidelines
- →Refreshing existing coding specifications
- →Documenting architecture patterns from source
- →Decomposing spec work by layer
About this skill
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.
When not to use it
- →When the task is not related to creating or refreshing Trellis coding specs
- →When the task does not involve analyzing a codebase to derive spec guidelines
- →When the goal is to write generic advice without source-backed rules
Limitations
- →The skill focuses on `.trellis/spec/` guidelines
- →The skill emphasizes source-backed rules over generic advice
- →The skill requires the final specs to contain no template placeholders
How it compares
This skill provides a platform-neutral, single-agent workflow for creating codebase-backed Trellis specs, ensuring they reflect the actual project architecture rather than generic templates or placeholder text.
Compared to similar skills
trellis-spec-bootstrap side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| trellis-spec-bootstrap (this skill) | 0 | 1mo | No flags | Intermediate |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| repo-research-analyst | 1 | 6mo | Review | Intermediate |
| c4-component | 1 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
repo-research-analyst
parcadei
Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase
c4-component
sickn33
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.
agent-pseudocode
ruvnet
Agent skill for pseudocode - invoke with $agent-pseudocode
spec
matteocervelli
>
cs-arch
wildlily1021
维护 `codestable/architecture/` 这份只记现状的系统地图，三种模式 update / check / backfill。触发：用户说"刷新 architecture"、"做架构检查"、"补这个模块的架构文档"、"方案和代码对得上吗"，或 feature 阶段需要先做架构动作。不写未来规划（走 cs-roadmap）。