plan-retire

To clean up project plans after a feature merge, run the retirement process to delete non-essential plans while preserving durable decisions. This ensures your project history remains clean, useful, and maintainable post-merger.

Plan retirement is the process of retiring project plans after successful feature merges. It involves documenting durable decisions for knowledge preservation and removing obsolete plans to maintain a clean project knowledge base.

To preserve decision documentation when deleting old plans, use a retirement workflow that captures and documents durable decisions before removing non-essential files. This maintains knowledge integrity for future reference.

Yes, you need main branch access to retire merged project plans. The process requires verifying the merged state on the main branch and updating project documentation and knowledge graphs accordingly.

Plan retirement affects the project knowledge graph by updating the plans index and rebuilding the graph as necessary. This ensures the knowledge base accurately reflects current project history without obsolete plan references.

You should not use an automated plan retirement process if durable decisions from the feature plan have not yet been extracted and documented, as deleting non-essential plans prematurely risks losing critical project history.