trellis-update-spec

To save executable contracts after debugging, codify concrete signatures, payload fields, and boundary behavior into .trellis/spec/ documents. This preserves implementation insights as verifiable specs for future sessions and cross-team reference.

Executable contracts are codified coding conventions that include concrete signatures, payload fields, environment keys, and boundary behavior. They are recorded as code-specs to keep cross-layer contracts synchronized and provide a reusable, test-verifiable reference.

Document environment keys and boundary behavior by capturing them as code-specs within .trellis/spec/ documents. This ensures the recorded contracts are verifiable by tests and provides a reliable reference for future development sessions.

You should update specifications after finishing a debugging session, making design decisions, or learning new patterns. Capturing these insights immediately ensures institutional memory is preserved and cross-layer contracts remain synchronized.

Yes, code-specs synchronize cross-layer contracts by recording concrete signatures and boundary behavior in .trellis/spec/ documents. This provides a reusable reference that ensures future work and cross-team development remain aligned.

No, the trellis-update-spec process requires no external dependencies. It directly codifies executable contracts and coding conventions into .trellis/spec/ documents using insights gathered from debugging, implementation, or discussions.