docs: add plan management workflow and lab-monitoring MCP server

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CLAUDE.md

@@ -60,6 +60,13 @@ Secrets are handled by sops. Do not edit any `.sops.yaml` or any file within `se
 
 When starting a new plan or task, the first step should typically be to create and checkout a new branch with an appropriate name (e.g., `git checkout -b dns-automation` or `git checkout -b fix-nginx-config`).
 
+### Plan Management
+
+When creating plans for large features, follow this workflow:
+
+1. When implementation begins, save a copy of the plan to `docs/plans/` (e.g., `docs/plans/feature-name.md`)
+2. Once the feature is fully implemented, move the plan to `docs/plans/completed/`
+
 ### Git Commit Messages
 
 Commit messages should follow the format: `topic: short description`