trellis-update-spec

You can capture executable contracts and coding conventions into .trellis/spec documents to preserve debugging learnings for future sessions. This converts integration decisions into concrete, testable rules including signatures, payload fields, and error behavior.

Executable contracts are concrete, testable specifications that define function signatures, payload fields, validation rules, and error behavior. You need them during debugging, implementation, or discussions to lock in design decisions and guide future code reviews.

Run the update flow to capture new executable contracts and design decisions into the .trellis/spec/ directory. This creates standardized docs that convert session learnings into testable contracts, ensuring future implementations follow validated rules.

The skill applies during debugging, implementation, or discussions to output code-spec sections within the .trellis/spec structure. It requires no external dependencies to generate documents containing signatures, contracts, validation rules, and test points.

The best way is capturing executable contracts into .trellis/spec documents, which preserves validation rules and test points as standardized docs. This ensures future AI-assisted sessions reference concrete specifications rather than losing prior debugging context.

Coding conventions get lost when session context expires without durable documentation. Prevent this by capturing executable contracts into .trellis/spec documents, which locks in decisions, signatures, and validation rules for rapid knowledge retention across sessions.