sdcorejs-auto-plans

Plan persistence automatically snapshots user-approved coding plans into a track-scoped corpus, allowing future session planning to reuse your chosen granularity, phase grouping, and verification cadence without repetitive reformatting.

Cross-session memory is needed when you want to maintain consistent plan formatting across multiple development workflows. It loads frontmatter and phase headers from the latest approved plans to guide new structure without copying full task lists.

Yes, plan snapshots apply consistently across angular-portal, nestjs, and nextjs workflows. They maintain spec and plan pairing via the sourceSpecPath variable while operating in read-only mode at session start.

To save an approved plan, ask the agent to proceed after you explicitly approve the 06-review-plan contract. The system then writes a new timestamped markdown file into the .sdcorejs/plans directory for later reuse.

Coding plans are not saved automatically due to approval-gated safety. The system writes a new plan file only after receiving an explicit affirmative approval signal, preventing corpus corruption from draft plans or silence.

The best way to ensure consistent phase headers is through automatic style loading. The system loads frontmatter and phase headers from the latest three approved plans to guide new plan structure across sessions.