From a8a389e0b41078b6d6567a19b517ef450db2e51a Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 21 Aug 2026 11:33:03 +0000 Subject: [PATCH] The post-merge follow-ups promise what the prompt queues: maintainability and security MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The feature line also named readability, but on_before_mergeable_prompt.md has only ever queued the maintainability and security-audit presets — and under the spec-driven thesis, humans read specs while agents work the code, so per-merge readability passes are the one follow-up the methodology de-prioritizes. The readability preset stays in the catalog, on demand and in the maintenance sweep. Approved by the human per the features rule. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_011XvEviGLEJZsp1h6iWzgma --- FEATURES-SPEC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FEATURES-SPEC.md b/FEATURES-SPEC.md index 93c23dc14..87c20c698 100644 --- a/FEATURES-SPEC.md +++ b/FEATURES-SPEC.md @@ -111,7 +111,7 @@ happens while nobody is at the keyboard. - Handoff panel: push / open PR / merge, as buttons - A withheld merge is reported with its reason - Agent history archived on the `tf-data` branch under per-user directories — pushed the moment a session settles -- Post-merge quality follow-ups queued (maintainability / security / readability) +- Post-merge quality follow-ups queued (maintainability / security) - Knowledge folded back into `DECISIONS.md` / `FACTS.md` / `INSIGHTS.md` at merge ## Autonomy — what happens when nobody is at the keyboard