What problem does it solve? Generic spec templates produce placeholder-filled documentation that does not reflect how a repository actually works. This Skill bootstraps or refreshes .trellis/spec/ guidelines grounded in the real codebase, so future agents receive concrete, source-backed coding rules instead of boilerplate. ## Core Features & Use Cases - Repository Analysis: Uses GitNexus code knowledge graphs, ABCoder AST parsing, and direct source reads to map package boundaries, runtime layers, data flow, and error handling patterns. - Spec Decomposition and Writing: Splits spec work by package or layer only when the codebase justifies it, then writes rules with real file paths, examples, and anti-patterns. - Verification Pass: Checks for placeholder text, broken links, and index files that do not match the final spec set. - Use Case: After adopting Trellis in a monorepo, run this Skill to analyze each package and produce .trellis/spec/ docs that teach future agents the project's actual command handler, testing, and configuration conventions. ## Quick Start Analyze this repository and create project-specific Trellis spec files under .trellis/spec based on the real source code.
