trellis-update-spec

Capture debugging insights and design decisions into durable code-spec documentation. This records concrete implementation rules, signatures, payload fields, validation behavior, and error handling expectations for future development sessions.

Code-spec documentation is structured contract documentation covering signatures, test expectations, and implementation guidance. You need it during feature development, bug fixes, and architectural decisions to prevent valuable implementation knowledge from being lost.

Evaluate whether learned information represents executable contracts or broader architectural guidance. Concrete signatures, validation behavior, and test expectations belong in code-spec files, while overarching design conventions fit higher-level guides.

Yes, you can capture cross-layer API request and response contracts, validation rules, and test requirements. This ensures future developers and AI agents implement changes consistently without repeating common mistakes.

Executable contract documentation should include function signatures, payload fields, validation behavior, error handling expectations, and test expectations. It must provide implementation guidance that future sessions can directly apply to maintain coding conventions.