What problem does it solve? Teams adopting Trellis often end up with generic template specs that contain placeholder text and boilerplate advice unrelated to their actual codebase. This Skill bootstraps or refreshes .trellis/spec/ guidelines grounded in real source files, package boundaries, and local patterns. ## Core Features & Use Cases - Repository Analysis: Inspects architecture using GitNexus code knowledge graphs, ABCoder AST parsing, and direct source reads before writing any rule. - Spec Decomposition: Splits spec work by package, layer, or cross-cutting concern only when the codebase structure justifies it. - Evidence-Backed Writing: Produces spec files with concrete file paths, real examples, anti-patterns, and verification checks, removing all template placeholders. - Use Case: After initializing Trellis in a TypeScript monorepo, run this Skill to analyze each package and generate .trellis/spec/ docs that teach future agents the project's actual conventions. ## Quick Start Ask the agent to bootstrap the Trellis specs for this repository by analyzing the codebase and filling the .trellis/spec directory with project-specific guidance.