mcpField
T
trellis-spec-bootstrap

trellis-spec-bootstrap

github.com/mindfold-aiDevelopment15.0k104 installsUpdated 4w ago
Repository

About trellis-spec-bootstrap

A skill for creating or refreshing `.trellis/spec/` guidance based on a repository’s actual code and architecture. It is intended for agents working on codebases and covers analysis, document organization, writing, and verification in a single-owner process.

Key features

  1. 01Analyze repository architecture
  2. 02Choose specification boundaries
  3. 03Write source-backed project guidance
  4. 04Verify consistency and remove placeholders

Use cases

  1. 01Create specifications for a newly initialized Trellis repository
  2. 02Refresh guidance after repository changes
  3. 03Organize documentation by package or layer

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mindfold-ai/trellis --skill trellis-spec-bootstrap

After installing, type/trellis-spec-bootstrapin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
mcp-setup.md
repository-analysis.md
spec-task-planning.md
spec-writing.md

Details

From the project README

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

NeedRead
Repository architecture analysisreferences/repository-analysis.md
Spec work decomposition and task planningreferences/spec-task-planning.md
Writing high-signal Trellis spec filesreferences/spec-writing.md
GitNexus and ABCoder MCP setupreferences/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.

Comments

Markdown supported