trellis-update-spec

To document executable contracts after debugging, you can capture signatures, payload fields, and boundary behaviors into structured .trellis/spec/ documents, preserving institutional memory for future cross-team alignment.

Preserving institutional memory is achieved by codifying testable contracts and coding conventions into actionable code-spec documents with explicit triggers, validation, and case guidance, ensuring audit-ready consistency.

Yes, you can enforce code-spec discipline across teams by applying a mandatory 7-section structure that codifies explicit triggers, signatures, contracts, and error handling within the shared .trellis/spec/ documents.

Capturing testable contracts into code-spec documents improves future sessions by providing structured templates that document triggers, validation, and boundary behaviors, preventing the loss of concrete decisions made during discussions.

No specific external framework is required, as the skill autonomously applies a structured template to codify payload fields, environment keys, and boundary behaviors directly into the local .trellis/spec/ directory.

Teams lose testable contracts during implementation because concrete decisions are often not codified, which this skill solves by automating the capture of executable contracts into actionable code-spec documents.