SkillsAdd

mindfold-ai/trellis

trellis-spec-bootstrap

Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow.

First seen Jun 23, 2026

Installation

$ npx skills add mindfold-ai/trellis --skill trellis-spec-bootstrap
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
azure-enterprise-infra-planner Shared topics
microsoft/azure-skills

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…

402.8K installs

Also in this package

Other skills from mindfold-ai/trellis · top by installs.

npx skills add mindfold-ai/trellis
trellis-meta 383 trellis-brainstorm 144 trellis-finish-work 128 trellis-check 125 trellis-continue 122 trellis-before-dev 117 trellis-update-spec 114 trellis-start 113 trellis-break-loop 113 python-design 104

Browse all from mindfold-ai/trellis

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 14.5K
License LICENSE
Default branch main
Open issues 45
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,679 B
  • docs SUMMARY.md 355 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 89 installs

SKILL.md

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

  1. Confirm Trellis is initialized and inspect the current .trellis/spec/ tree.
  2. Analyze the repository architecture with the best available tools: GitNexus, ABCoder, language tooling, and direct source reads.
  3. Decompose the spec work by package and layer only when that reflects the actual codebase.
  4. Fill or reshape the spec files with concrete patterns, file paths, examples, and anti-patterns from the project.
  5. Verify that the final specs are internally consistent and contain no template placeholders.

Reference Routing

Need Read
Repository architecture analysis [references/repository-analysis.md](references/repository-analysis.md)
Spec work decomposition and task planning [references/spec-task-planning.md](references/spec-task-planning.md)
Writing high-signal Trellis spec files [references/spec-writing.md](references/spec-writing.md)
GitNexus and ABCoder MCP setup [references/mcp-setup.md](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.md files match the final spec file set.
  • Any required setup or analysis assumptions are documented in the relevant spec or task notes.