trellis-spec-bootstarp

To generate codebase-backed Trellis specifications, inspect the repository structure, packages, and source files to create evidence-based guidelines with implementation patterns. This produces accurate .trellis/spec documentation grounded in your actual architecture.

Trellis spec documentation provides coding guidelines organized by real package, layer, or cross-cutting ownership boundaries. It includes source-backed conventions, anti-patterns, and verification steps to help coding agents follow repository-specific implementation patterns.

Yes, you can refresh .trellis/spec directories across multiple packages, layers, CLI workflows, and shared architecture boundaries. It decomposes guidance by real ownership boundaries and verifies that placeholder content is removed.

To remove placeholder content when initializing architecture specifications, inspect the codebase source files and replace generic templates with source-backed conventions. Verification ensures template-only documentation is eliminated from the spec indexes.

The best way to document repository architecture boundaries is through codebase analysis that maps source files and tests into coherent spec indexes. This creates practical rules grounded in the repository's actual implementation rather than generic templates.