trellis-update-spec

To document code-specs after a debugging session, you can automate capturing executable code-specs using a structured 7-section template. This preserves concrete signatures, payload structures, and cross-layer contracts for future implementation.

Recording cross-layer contracts is best handled by enforcing a standardized code-spec template with required frontmatter. This captures precise signatures and environment requirements to guide future development and prevent regressions.

Yes, you can use this workflow to document both bug fixes and feature implementations. It applies to any scenario where precise signatures, change history, and validation steps must be recorded to maintain code-spec accuracy.

You prevent regressions by recording change history, tests, and validation steps within the code-spec. This ensures that every documented design decision and payload structure can be tested and validated against future updates.

Yes, you need frontmatter containing a name and description to store updated code-specs. This requirement enforces consistent metadata tagging across all documented design decisions and debugging sessions.

Yes, the code-spec template supports optional resources folders for extended context. This allows you to store additional environment details and supporting files alongside the core 7-section code-spec documentation.