trellis-spec-bootstrap

Bootstrap Trellis specs from a live codebase with concrete guidelines.

52|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/RebornQ/fl_api_hub --skill trellis-spec-bootstrap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-spec-bootstrap
Source: https://github.com/RebornQ/fl_api_hub/tree/main/.agents/skills/trellis-spec-bootstrap
Command: npx skills add https://github.com/RebornQ/fl_api_hub --skill trellis-spec-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams bootstrap project-specific Trellis specification guidelines directly from the current codebase, enabling accurate, code-aligned docs rather than generic templates.

Core Features & Use Cases

  • Analyze the repository and inspect the existing .trellis/spec/ tree to identify current state and gaps.
  • Decompose spec work by package and layer based on actual code architecture, then write concrete guidelines.
  • Verify final specs for consistency, remove template remnants, and ensure alignment with real files and patterns.
  • Use Case: start a new Trellis project or refresh specs after significant code changes to reflect real-world structure.

Quick Start

Analyze the repository and bootstrap the .trellis/spec guidelines from the current codebase.

Frequently Asked Questions about trellis-spec-bootstrap

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

FAQPage Schema
How do I bootstrap Trellis specs from my existing codebase?▼

To bootstrap Trellis specs, the skill analyzes your repository architecture and inspects the current .trellis/spec tree to identify gaps, then writes concrete, testable guidelines aligned with real files.

What is the best way to generate architecture documentation that aligns with my actual code?▼

Generating code-aligned architecture documentation requires analyzing your live codebase by package and layer, embedding actual file paths and patterns, and verifying final specs to remove generic template remnants.

When do I need to refresh .trellis/specs across packages and layers?▼

You need to refresh .trellis/specs when starting a new Trellis project or after significant code changes to ensure your specification guidelines accurately reflect the real-world code structure and architecture.

How do I ensure my project specifications include concrete, testable guidelines instead of generic templates?▼

To ensure testable guidelines, the skill decomposes spec work by package and layer based on actual code, embeds real file paths and anti-patterns in the docs, and provides verification steps for consistency.

Can I use trellis-spec-bootstrap to analyze architecture and produce docs without existing .trellis/spec directories?▼

Yes, you can use it to start a new Trellis project. The skill inspects the existing .trellis/spec tree to identify the current state and gaps, allowing it to bootstrap initial guidelines directly from your codebase.

What are the limitations of bootstrapping spec guidelines directly from a live codebase?▼

A limitation is that the produced docs depend entirely on the current codebase state; if the code contains anti-patterns, they may be documented unless verification steps are followed to ensure alignment with intended architecture.