[FEATURE] Deprecate implemented plans or move them to /plans/archive
Resolved 💬 3 comments Opened Dec 24, 2025 by mintmcqueen Closed Feb 14, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
All the new /plans features are great, only there are sometimes unnecessary re-reads that happen when Claude tries to determine whether or not to build on or move on from a previously implemented plan. Wastes tokens and time.
Proposed Solution
Move implemented plans to /plans/archive.
Establish /plans/index.json (where each plan gets a natural language summary).
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
File operations
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗