trellis-spec-bootstarp

To generate coding specifications from an existing monorepo, bootstrap project-specific Trellis spec documents by analyzing repository architecture, decomposing package boundaries and runtime layers, and writing evidence-based rules backed by source files.

Creating architecture documentation without template placeholders involves applying a spec creation workflow that requires source-backed guidance, concrete file references, synchronized index files, and the explicit removal of any template artifacts.

Yes, Trellis spec bootstrap optionally integrates GitNexus or ABCoder analysis to inspect project structure, package boundaries, and source files, ensuring that the generated coding specs are accurately evidence-based.

To refresh outdated development guidelines in a .trellis/spec directory, apply a consistency verification workflow that analyzes existing specifications, updates package and layer decomposition, and rewrites rules based on the current codebase state.

You need to decompose documentation by package and layer ownership when initializing a monorepo's spec directory, because artificial templates fail to reflect actual project structure and lead to generic or outdated development guidance.

Yes, you can verify coding specification consistency by applying a final verification workflow that checks practical rules, navigation indexes, and anti-patterns against concrete file references and source-backed guidance from the repository.