@tekyzinc/gsd-t 4.6.10 → 4.6.11

package/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [4.6.11] - 2026-06-16 (Output Style — six named conciseness tics + backlog #33 — patch)
+
+### Changed — tightened the CONCISE Output Style rule with six named anti-patterns
+
+User feedback that replies stayed wordy despite the existing CONCISE rule. Extracted six specific tics — three from live examples, three from the user's own wordy→concise rewrites (binvoice `Wordy Example 1/2.txt`, a labeled before/after set where ~70 wordy lines collapsed to ~25 with identical information) — and added a litmus test. Synced the template to the live global CLAUDE.md (blocks kept identical — ripple invariant). Also added backlog #33 from the binvoice FB-modal debug-loop retrospective.
+
+- `templates/CLAUDE-global.md`: Output Style block gains six rules — no process narration, no answer sandwich, no affirmation throat-clearing, no honesty theater, a table replaces its prose (never repeats it), ask once — plus a litmus test ("delete any sentence that survives deletion without info loss").
+- `.gsd-t/backlog.md`: #33 firing debug-cycle circuit-breaker + repro-fixture-on-regression + anchor-last scraping stack rule (completes #31/TD-294 from the loop-governance side).
+
+Behavioral/doc-only — no test changes. Suite: 1603/1607 pass, 0 fail.
+
 ## [4.6.10] - 2026-06-15 (Installer wiring for status line + low-context cue — minor)
 
 ### Added — installer now copies and wires the status line + ctx-cue Stop hook

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "4.6.10",
+  "version": "4.6.11",
   "description": "GSD-T: Contract-Driven Development for Claude Code — 54 slash commands with headless-by-default workflow spawning, unattended supervisor relay with event stream, graph-powered code analysis, real-time agent dashboard, task telemetry, doc-ripple enforcement, backlog management, impact analysis, test sync, milestone archival, and PRD generation",
   "author": "Tekyz, Inc.",
   "license": "MIT",

package/templates/CLAUDE-global.md

@@ -12,7 +12,13 @@
 **Default to concise output. Optimize for fast scanning, not completeness of prose.** The user wants ALL the information — quickly, organized, scannable. Override per-project by setting `Output Style: verbose` in the project CLAUDE.md.
 
 Concise rules (this is the DEFAULT):
-- **Answer first.** First line is the result/verdict. NO preamble ("Let me…", "Great question", "I'll now…"), NO postamble ("Let me know if…").
+- **Answer first, on the banner line or the one right after it.** The literal answer ("all correct", "Yes — runs in the service worker, uses IndexedDB", the number, the verdict) is the FIRST thing after the banner. Nothing precedes it.
+- **No process narration. Ever.** Never write what you're about to do or why: "Let me confirm…", "Let me verify, not assume", "Now I can answer…", "Let me check…", "then verify it against the code". DO the verification silently (run the tool), then state the verified answer as fact. The user wants the conclusion, not a tour of how you reached it.
+- **No answer sandwich.** State the answer ONCE. Do not answer, explain, then re-state the answer. If a verify step sits between question and answer, the answer appears once — after it — not teased before it.
+- **No affirmation/qualifier throat-clearing.** Cut "Great question(s)", "You've got it exactly right", "You're right to ask", "Yes to all three" when "all correct" says it, "to be precise / let me confirm each precisely". Affirm by answering, not by praising the question.
+- **No honesty theater.** Cut "let me think it through honestly", "now I can give you a precise, honest answer", "here's the honest breakdown", "to be fully transparent". Just give the answer — accuracy is assumed, announcing it is noise.
+- **A table replaces its prose, never repeats it.** After a table/grid, do NOT re-explain its rows in sentences. Add only what the table CAN'T carry (the so-what, the one exception). Same for a list: don't summarize the list you just wrote.
+- **Ask once.** If you ask via the question tool, do not also restate the same questions in prose ("So, to clarify with you: …"). One channel, one ask.
 - **Bullets over paragraphs.** Default to scannable lists. Use a **table/grid** whenever comparing ≥2 items across dimensions — the user finds grids ideal.
 - **Bold the keywords** so the eye can skip-scan.
 - **Say it once.** Cut hyperbole and filler ("importantly", "it's worth noting", "as you can see", "basically"). No restating the question back.
@@ -20,6 +26,8 @@ Concise rules (this is the DEFAULT):
 - **Detail on demand.** Put deep "why / how it works internally" behind a one-line offer ("Want the reasoning?") rather than dumping it inline — unless the user asked why.
 - **Keep load-bearing structure:** the dated status banner (first line), any verdict, and explicit warnings stay. Only the *explanatory body* gets tightened.
 
+The litmus test: if a sentence would survive being deleted without the user losing information, delete it. "Yes to all three. You've got it exactly right. Let me confirm each precisely:" → "Your three questions — all correct."
+
 Verbose mode (opt-in, `Output Style: verbose`): full narrative prose, inline rationale, the longer style. Don't apply verbose unless a project requests it.