trellis-update-spec

To document executable contracts after debugging, capture new signatures, payload fields, and boundary behaviors into centralized .trellis/spec/ documents, preserving implementation knowledge for future sessions and onboarding.

The best way to preserve design decisions for environment keys is recording them as code-spec in .trellis/spec/ files, creating a traceable history of validation rules and boundary behaviors for future reference.

Structure spec files by delivering a seven-section output covering scope, signatures, contracts, validation and error matrix, good/base/bad cases, tests, and wrong versus correct implementations to capture validation rules comprehensively.

You need to update .trellis/spec documents during debugging, implementation, or design discussions whenever new or changed signatures, environment keys, and validation rules emerge, ensuring executable contracts remain current.

Yes, you can use .trellis/spec to onboard new team members because it stores concrete signatures, payload fields, and coding conventions as a traceable record of design decisions and patterns learned from prior sessions.

Include the seven required sections—scope and trigger, signatures, contracts, validation and error matrix, good/base/bad cases, tests, and wrong versus correct—to fully capture boundary behaviors and payload fields as executable contracts.