plan-writer

Temporary implementation plans should be stored in the tmp/ directory to prevent docs/ from becoming bloated. This keeps one-off or iterative planning notes organized and separate from permanent project documentation.

Name temporary planning files using the convention implementation_plan_{issue_number}.md inside the tmp/ directory. This standardizes drafting implementation plans and documenting findings for specific issues during development workflows.

Use the tmp directory for project documentation when drafting one-off implementation plans, documenting quick investigations, or planning issue resolutions. It enforces temporary-file placement so permanent docs stay clean and only contain finalized content.

The best way to manage temporary planning files is to enforce lifecycle hygiene by placing drafts in tmp/ and deleting or archiving them once plans are finalized. This prevents permanent drafts from accumulating in docs/.

Yes, you can promote a temporary implementation plan from tmp/ to permanent docs or an ADR when the plan is complete and requires long-term retention. Otherwise, delete the file per project policy to keep the repository clean.

Your docs directory fills up with drafts because temporary implementation plans and investigation notes are not being directed to tmp/. Enforcing temporary-file placement in tmp/ with proper naming conventions prevents permanent drafts in docs.