ss-sdd-maintaining-memory-file

To prevent stale or bloated agent memory, update the memory file only with significant project-level truth changes from spec, plan, and ADR outputs while enforcing a strict character cap.

The best way to update project conventions in an SDD pipeline is dispatching a subagent during the memory maintenance stage to ingest artifacts and apply earned-its-place updates to the memory file.

To manage architectural decision records in agent memory, ingest ADR outputs during the post-implementation stage and add or edit rules only for significant architectural changes, avoiding transient content.

You should not write to an agent memory file when no memory file path is configured or when the target file is missing on disk, as the update process requires strict path validation before writing.

Yes, the agent memory maintenance process enforces a configurable character budget to prevent bloating, ensuring only significant project-level truths are kept accurate and lean.

The purpose of the memory maintenance stage in spec-driven development is to produce incremental, budgeted updates to the project memory file based on spec, plan, and ADR outputs before pipeline completion.