compound

To capitalize sprint learnings, trigger a capitalization command at sprint end to extract project, methodology, and competency insights. This generates a structured synthesis persisted to sprint artifacts and a compound.md file for traceability.

A structured post-sprint synthesis should crystallize patterns across three axes: project learnings, methodology feedback, and competency notes. This approach generates lessons learned, best practices, and technical debt items for documentation.

Extracting methodology feedback and competency notes requires applying a multi-axe workflow during end-of-sprint reviews. This process proactively generates learning notes and updates user profiles with competency calibrations to sustain growth.

Persist lessons learned and best practices to docs/sprints/sprint-{ NN }/compound.md. This archival persistence ensures traceability and drives continuous improvement across the sprint lifecycle by compounding knowledge.

Yes, generating technical debt items is a core feature of sprint capitalization. By crystallizing patterns and feedback at sprint end, the workflow outputs structured lessons learned and technical debt items directly to your sprint documentation.

No specific dependencies are required to run this multi-axe sprint capitalization workflow. The process applies prerequisites, execution steps, and archival persistence directly to generate structured post-sprint syntheses without external tools.