trellis-spec-bootstrap

Name: trellis-spec-bootstrap
Availability: InStock
Author: tincopper

Analyze a repository and write source-backed .trellis/spec guidance.

10|Updated Mar 21, 2026

Search Tags:#architecture #documentation #codebase #repository analysis #specs #trellis

Ready to run

npx skills add https://github.com/tincopper/neeko --skill trellis-spec-bootstrap-tincopper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-spec-bootstrap
Source: https://github.com/tincopper/neeko/tree/main/.agents/skills/trellis-spec-bootstrap
Command: npx skills add https://github.com/tincopper/neeko --skill trellis-spec-bootstrap-tincopper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you convert a live repository into accurate Trellis spec guidance, so future work is based on the codebase that actually exists instead of generic templates.

Core Features & Use Cases

Repository Analysis: Inspect the project structure, package boundaries, and runtime layers before writing any guidance.
Spec Decomposition: Split documentation by package, layer, or cross-cutting concern only when the codebase really needs it.
Source-Backed Writing: Produce .trellis/spec/ docs with concrete file paths, examples, and anti-patterns from the repository.
Verification and Cleanup: Confirm the final spec tree is coherent, complete, and free of placeholder text.
Use Case: A team onboarding a new codebase can use this Skill to generate practical Trellis specs that match the repository’s current architecture and conventions.

Quick Start

Use the trellis-spec-bootstrap skill to inspect this repository and draft accurate .trellis/spec guidance for its real packages and layers.

Frequently Asked Questions about trellis-spec-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate spec documentation from an existing codebase?▼

Spec documentation should be split by package, layer, or cross-cutting concern only when the codebase actually requires it. This ensures the guidance matches the repository's real architecture instead of generic templates.

How do I structure .trellis/spec files for a complex repository?▼

Trellis spec bootstrap requires a live repository to analyze. It inspects the project structure, package boundaries, and runtime layers before writing any guidance, ensuring all docs reflect the codebase that actually exists.

Can I create architecture docs that reference real file paths instead of templates?▼

After drafting the spec tree, verify and clean up the documentation to confirm it is coherent, complete, and free of placeholder text. This final check ensures the generated guidance remains useful for future development.

What is the best way to document package boundaries and cross-cutting workflows?▼

You should not use this approach if your repository is not yet initialized or lacks a stable structure. It requires a live codebase to inspect for source-backed rules, real file references, and coherent index files without placeholders.