What problem does it solve? Teams adopting Trellis often end up with generic template specs that do not reflect their actual codebase, giving future agents misleading or empty guidance. This Skill bootstraps or refreshes .trellis/spec/ documentation grounded in real source files, patterns, and anti-patterns. ## Core Features & Use Cases - Repository Analysis: Uses GitNexus code knowledge graphs, ABCoder AST parsing, and direct source reads to map package boundaries, runtime layers, and data flow before writing any rule. - Spec Decomposition & Writing: Splits spec work by package or layer only when the codebase justifies it, then writes concrete guidance with real file paths, examples, and anti-patterns. - Verification Pass: Checks for placeholder text, broken links, stale index files, and template leftovers so the final spec tree matches the project as it exists. - Use Case: After initializing Trellis in a monorepo, run this Skill to analyze each package with GitNexus and ABCoder, then produce tailored .trellis/spec/ files 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 .trellis/spec/ with project-specific guidance.
