trellis-spec-bootstarp

Generate source-backed Trellis coding specs from repository analysis.

10|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/tincopper/neeko --skill trellis-spec-bootstarp-tincopper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-spec-bootstarp
Source: https://github.com/tincopper/neeko/tree/main/.omp/skills/trellis-spec-bootstarp
Command: npx skills add https://github.com/tincopper/neeko --skill trellis-spec-bootstarp-tincopper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork from creating or refreshing Trellis coding specs by grounding every rule in the actual repository structure, source files, and project conventions.

Core Features & Use Cases

  • Repository Analysis: Inspects the codebase to identify real packages, layers, and spec boundaries before writing guidance.
  • Spec Authoring: Produces concrete .trellis/spec/ docs with file paths, examples, anti-patterns, and navigation indexes.
  • Verification Workflow: Checks for placeholder text, mismatched indexes, and incomplete spec content so the final spec set is usable.
  • Use Case: A team inherits a large repository and needs an AI-ready spec tree that reflects current architecture instead of generic templates.

Quick Start

Ask the assistant to inspect the repository and refresh the .trellis/spec guidelines with source-backed rules, real file references, and a cleaned index.

Frequently Asked Questions about trellis-spec-bootstarp

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

FAQPage Schema
How do I generate architecture documentation from an existing codebase?

Generate source-backed architecture documentation by inspecting the repository to identify real packages and layers, then authoring concrete spec files with actual file paths and examples.

What is source-backed specification verification for repository analysis?

Source-backed specification verification checks generated coding specs for placeholder text, mismatched indexes, and incomplete content to ensure the final spec set reflects the actual repository structure.

How do I bootstrap .trellis/spec guidelines for an inherited project?

Bootstrap .trellis/spec guidelines by asking the assistant to inspect the repository and refresh the specs with real file references, source-backed rules, and a cleaned navigation index.

Can I use generic templates for Trellis specs on a large codebase?

Generic templates are insufficient for large codebases; this approach grounds every rule in the actual repository structure and project conventions to produce an AI-ready spec tree.

Does bootstrapping Trellis specs require concrete file references?

Yes, bootstrapping Trellis specs requires concrete file references, real examples, and index consistency to ensure the generated documentation is source-backed and completely placeholder-free.