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/ guidelines grounded in real source files, tests, and architecture. ## Core Features & Use Cases - Repository Analysis: Uses GitNexus code knowledge graphs, ABCoder UniAST parsing, and direct source reads to discover package boundaries, runtime layers, and core abstractions. - Spec Decomposition & Planning: Splits spec work by package or layer only when it matches real ownership boundaries, with a PRD-shaped task template for traceability. - Evidence-Backed Spec Writing: Writes spec files with concrete file paths, examples, and anti-patterns, then verifies no placeholder text or broken index files remain. - Use Case: After initializing Trellis in a monorepo, run this Skill to analyze each package with GitNexus and ABCoder, then produce tailored .trellis/spec/ docs that teach 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.