plan-archive

To archive abandoned plans with context, provide the plan name and rationale, generate an archive.md note in the plan directory, then move the folder to plans/archive/ and commit. This enforces a standard workflow preserving decision context for future reference.

Maintaining an audit trail for obsolete workflows requires recording the archive reason in archive notes before relocating plan directories. This documents the rationale for abandoned or superseded plans, providing a reference for future learning and work.

You need to move superseded plans to an archive directory when plans become abandoned, obsolete, or replaced and require documented rationale. This preserves decision context by generating archive notes and relocating the plan folders for version-control tracking.

Yes, you can record rationale for abandoned plans without losing context by generating an archive.md file with notes. The workflow moves the plan directory to plans/archive/ while preserving the decision context and reasons for future reference.

Yes, archiving plans requires version-control commits to finalize the process. After moving the plan directory to plans/archive/, committing the changes ensures the audit trail and archived decision context are permanently tracked in the project workflow history.