design-compounder

To preserve design learnings from a completed sprint, you queue the finished feature IDs and extract artifact-backed lessons into durable memory and design references. This process evaluates sprint outcomes to capture cross-sprint knowledge without re-opening runnable sprint slots.

Capturing cross-sprint design knowledge with provenance requires enforcing checks that accept only artifact-backed lessons from sprint outcomes. This governance step updates durable knowledge stores, ensuring future design work and roadmaps rely on verified evidence.

You update design references after a sprint by aligning extracted lessons with the compound_pending_feature_ids queue. This non-runnable governance step updates memory stores while explicitly avoiding the re-opening of runnable sprint slots to prevent rework.

Yes, linked artifacts are required to extract durable design lessons from sprint outcomes. The extraction process enforces provenance checks and accepts only artifact-backed lessons to ensure the captured cross-sprint knowledge is verifiable and durable.

Yes, you can use sprint outcomes to guide future design roadmaps and reviews by extracting durable learnings into memory and design references. This captured knowledge operates as a governance step that informs and aligns future design documentation.

You should avoid using a design compounding step when sprint outcomes lack linked artifacts or provenance evidence. The process strictly enforces provenance checks and rejects lessons without artifact backing, making it unsuitable for undocumented sprint results.