trellis-update-spec

Documenting API validation rules after debugging requires capturing concrete contracts, signatures, and error behavior. This skill records exact request and response rules plus test assertions into `.trellis/spec/` documents, ensuring the fix stays durable for future implementation work.

Persisting software engineering conventions involves logging design decisions, patterns, and anti-patterns for later reuse. This skill captures executable code-specs and project conventions in `.trellis/spec/` files, preventing future work from repeating the same integration mistakes.

Yes, you can record both backend and frontend cross-layer behavior. This skill safely extends specifications across layers by requiring concrete signatures, environment keys, validation rules, and clear examples to accurately document cross-layer behavior.

Yes, executable test assertions are required to write project specifications using this method. The skill mandates concrete signatures, contracts, and validation rules to ensure captured code-specs remain executable and durable for future implementation work.

Projects repeat the same bugs when hard-won implementation knowledge is not preserved as executable code-specs. This skill solves the problem by capturing learned fixes, patterns, and common mistakes in `.trellis/spec/` documents for later reuse.