trellis-spec-bootstarp

Project-specific coding specs are generated by analyzing your repository's architecture and source code patterns to document package boundaries and runtime layers. This creates accurate .trellis/spec/ directory files reflecting real-world conventions.

Automating coding spec documentation for a complex monorepo analyzes source code patterns to create a comprehensive .trellis/spec/ directory. This reflects the real-world file structures, anti-patterns, and package boundaries for new agent onboarding.

Generating Trellis spec files requires GitNexus and ABCoder for repository graph analysis and AST-based structure inspection. These dependencies provide the evidence-based architecture analysis needed to map package boundaries and runtime layers.

The best way to document package boundaries and runtime layers automatically is through AST-based structure inspection and repository graph analysis. This evidence-based approach replaces generic placeholders with accurate, project-specific coding specifications.

To ensure no placeholder text remains in generated architecture documentation, the skill uses a structured loop for decomposing spec work and verifying consistency. This workflow integration systematically eliminates generic placeholders by analyzing actual source code patterns.