From 4e8cc124f2786c1f46566166e291258a73637b35 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Torjus=20H=C3=A5kestad?= Date: Thu, 5 Feb 2026 00:21:08 +0100 Subject: [PATCH] docs: add plan management workflow and lab-monitoring MCP server Co-Authored-By: Claude Opus 4.5 --- .mcp.json | 8 ++++++++ CLAUDE.md | 7 +++++++ 2 files changed, 15 insertions(+) diff --git a/.mcp.json b/.mcp.json index 80f0818..ca4db92 100644 --- a/.mcp.json +++ b/.mcp.json @@ -13,6 +13,14 @@ "env": { "NIXPKGS_SEARCH_DATABASE": "sqlite:///run/user/1000/labmcp/nixpkgs-search.db" } + }, + "lab-monitoring": { + "command": "nix", + "args": ["run", "git+https://git.t-juice.club/torjus/labmcp#lab-monitoring", "--", "serve", "--enable-silences"], + "env": { + "PROMETHEUS_URL": "https://prometheus.home.2rjus.net", + "ALERTMANAGER_URL": "https://alertmanager.home.2rjus.net" + } } } } diff --git a/CLAUDE.md b/CLAUDE.md index a28b754..7db25b4 100644 --- a/CLAUDE.md +++ b/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`