speckit-promote-lessons

To convert approved retrospective lessons into durable documentation, promote them into narrow target locations like workflow files, checklist gates, or memory notes while generating a traceable report of all changes made.

Updating spec-kit repositories with process improvements involves parsing retrospective artifacts, verifying human approval status, and writing confirmed lessons into the narrowest applicable durable files without modifying product code.

Promoting retrospective lessons to project memory works by filtering out pending or rejected items, selecting the narrowest durable home for approved lessons, and producing a traceable promotion report showing what changed and why.

Yes, you can use this to update workflow files and checklist gates after a retrospective. It targets durable guidance locations like spec-kit templates and team documentation, ensuring only human-approved lessons are applied.

No, promoting retrospective lessons does not modify product code. It strictly preserves approval status and targets only durable documentation locations like memory notes and workflow files, leaving product code untouched.

Retrospective lessons are skipped during the promotion process if they lack human approval. The system checks approval status and ignores any pending or rejected artifacts to ensure only confirmed improvements become durable guidance.