trellis-update-spec

You document engineering discoveries into executable code specifications by capturing contracts, validation rules, and implementation learnings into structured spec documents. This ensures valuable coding knowledge from features and bug fixes is preserved for future development.

Preserving API contracts and coding conventions after a bug fix involves recording the request contracts, error cases, and correct implementation patterns into durable code-spec documentation. This prevents valuable debugging knowledge from being lost over time.

You need to update code-spec documentation during software development whenever you complete feature work, bug fixes, refactors, design decisions, API changes, or database updates that reveal new implementation patterns or validation rules.

Yes, you can use code-spec updates to document database changes and validation rules. The process captures technical discoveries and converts them into structured specifications with contracts, test expectations, and maintainable implementation guidance.

Capturing implementation knowledge works by applying structured specification updates to record contracts, conventions, and patterns. It guides developers and AI agents to document decisions from completed engineering tasks into the appropriate code-spec files.

Converting debugging discoveries into code specs requires structured updates containing contracts, validation rules, and test expectations. The process applies specifically to software development scenarios and needs implementation learnings to be clearly defined for durable documentation.