From b55ba1327758dcc0d0a6b834138993aa4fbbc836 Mon Sep 17 00:00:00 2001 From: Keysat Date: Sun, 14 Jun 2026 11:22:17 -0500 Subject: [PATCH] Fix doc drift surfaced by doc-auditor: mark /roundup built, correct Current state and a cross-ref --- AGENTS.md | 15 ++++++++------- ROADMAP.md | 29 +++++++---------------------- guides/retrofit.md | 3 ++- 3 files changed, 17 insertions(+), 30 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index cb1834f..a17332b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -91,10 +91,11 @@ should carry this so any vendor's agent surfaces pending items at session start: - `/roundup` is built: a cross-project status report that reads every repo's AGENTS.md/ROADMAP.md plus the inbox and groups all to-dos by priority — reads and reports only; deciding focus stays with the user. -- Specced in `ROADMAP.md`, not built: the `new-project` bootstrap, the cross-repo - quality-gate standard (linters/hooks/CI), and the optional SessionStart hook. -- The portable inbox-check line is still not in *other* repos' AGENTS.md nor the retrofit - playbook template — threading it (and the canonical `.gitignore`) into bootstrapping is a - ROADMAP item. -- Next: thread the standards into `retrofit-playbook.md`; then build the quality-gate hook - or the `new-project` bootstrap. +- The inbox-check line and canonical `.gitignore` are now threaded into the retrofit flow + (playbook + `/retrofit` guide), so new repos inherit them — but they're **not yet in other + *existing* repos**; a shallow scan shows the `.claude`/git setup is inconsistent across + repos. +- Specced in `ROADMAP.md`, not built: the cross-repo git-hygiene audit (item 6, HIGH), the + `new-project` bootstrap, the cross-repo quality-gate standard, and the SessionStart hook. +- Next: run the cross-repo git-hygiene audit (ROADMAP item 6), then the quality-gate hook or + the `new-project` bootstrap. diff --git a/ROADMAP.md b/ROADMAP.md index 8fd759b..fee46f2 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -42,29 +42,14 @@ how the standard gets *adopted* into a repo (a `/harden` command that installs t linter+hook for the detected stack?); whether to define a minimal "agentic-ops baseline" checklist doc alongside the other four standards docs. -## 2. `roundup` — cross-project status agent (the inverse of capture/triage) +## 2. `roundup` — cross-project status command ✅ BUILT -**Why:** a global "what should I do next / which project to focus on" view. Capture/triage -push items *down* into project repos; roundup reads back *up* across all of them. - -**Shape:** a command (`/roundup`, run from `~/Projects`) that fans out one read-only -subagent per repo to read that repo's `AGENTS.md` (`## Current state`) and `ROADMAP.md`, -plus reads the standards `INBOX.md` for not-yet-triaged items. It synthesizes **one -aggregated to-do list across all projects, grouped by priority**, including items that -haven't been pushed down to a repo yet. Mirror `full-eval`'s orchestrator pattern: fan out, -then synthesize into one report; the per-repo readers can be the generic `Explore` agent or -a small dedicated reader. - -**Division of labor (the user's explicit call):** the agent *reads and reports* — it -gathers and presents findings grouped by priority; it does **not** decide the best use of -time. Prioritizing across projects is a back-and-forth the user does on top of the report. -So the output is a clean, evidence-backed inventory, and the "what's actually worth doing -now" conversation happens after, in the main thread. - -**Open questions:** which folders count as "my projects" (scan `~/Projects`, skip non-repos -and the standards repo itself?); how to keep it cheap (cap readers, summarize hard); whether -roundup output is ephemeral or written to a `STATUS.md` in the standards repo for diffing -over time like `EVALUATION.md`. +Built and live: `guides/roundup.md` + `adapters/claude/commands/roundup.md`. Fans out a +read-only reader per repo over AGENTS.md/ROADMAP.md, folds in the inbox, and synthesizes one +priority-grouped to-do list across all projects; reads and reports only (prioritizing stays +with the user). **Remaining option:** output is shown inline by default — decide later +whether to also persist a `STATUS.md` in the standards repo for diffing over time like +`EVALUATION.md`. ## 3. Deterministic inbox surfacing — SessionStart hook (optional upgrade over the portable line) diff --git a/guides/retrofit.md b/guides/retrofit.md index 230b091..b200e42 100644 --- a/guides/retrofit.md +++ b/guides/retrofit.md @@ -90,7 +90,8 @@ AGENTS.md now exists but is a strong draft, not yet checked against reality. what's whole-repo versus subsystem is a judgment call that's theirs. Then report what moved where. - Ensure AGENTS.md carries the **inbox-check line** (the portable surfacing mechanism; see - `retrofit-playbook.md` Step 1 / `portability.md`). If it's missing, propose adding it. + `retrofit-playbook.md` Step 1, and the canonical wording in the standards repo's own + `AGENTS.md`). If it's missing, propose adding it. ## Phase 5 — Independent checks (delegate)