update-spec

Capture design decisions and coding guidelines by classifying insights from debugging sessions into patterns, conventions, or gotchas, and update relevant spec files using provided templates to maintain institutional memory.

Capture project conventions by translating newly learned insights into up-to-date specifications using template-driven documentation, creating a reliable record of decisions and rationale to prevent knowledge loss across tasks.

Update spec files by running a structured flow after completing tasks to identify what was learned, classifying it into design decisions or common mistakes, and storing it in appropriate spec files with guided templates to keep documentation current.

Yes, you can classify new patterns and common mistakes into existing project specifications by identifying what was learned during feature work and applying template-driven updates to relevant spec files to guide future work.

Template-driven documentation works for onboarding new team members by creating a reliable record of design decisions and rationale, ensuring consistent documentation and maintaining context across tasks to guide future work.