trellis-update-spec

You can preserve coding conventions and executable contracts by automating spec updates in .trellis/spec/ directories. This captures design decisions, signatures, and contracts directly after debugging or feature implementation to maintain codebase consistency.

You need to update code specifications when changes affect command signatures, cross-layer contracts, or infrastructure integrations. The process automatically triggers spec generation for these new feature implementations, design decisions, and bug fixes.

Documenting design decisions and code contracts is best handled by generating structured spec documents. These specifications include signatures, contracts, validation rules, and tests to ensure clarity and consistency across the codebase.

Capture knowledge from discussions by running an update command to write valuable insights directly into relevant code-spec documents. This preserves the learned conventions and executable contracts within the .trellis/spec/ directory structure.

The trellis-update-spec process does not require external dependencies. It operates independently using internal scripts and references to automate the creation and updating of code specifications within your project.

A code specification document should include signatures, contracts, validation, and tests. This structure ensures that executable contracts and coding conventions are captured with precision for future reference and consistency.