toga-ai 1.0.178 → 1.0.179

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.178",
+  "version": "1.0.179",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",

package/skills/kickoff/SKILL.md

@@ -375,6 +375,29 @@ Ready to proceed?
 or "you have full access" — proceed without further permission prompts, but still flag any
 write outside the expected scope.
 
+### Write discipline — stub-first to avoid the GateGuard double-emit tax
+
+The ECC fact-forcing gate (`gateguard-fact-force.js`, a `PreToolUse` hook) **denies the
+first Write/Edit to each new file path per session**, then allows the retry. The gate keys
+**only on `file_path` — it never inspects content** (verified in the hook: it `markChecked`s
+the path on the deny, so any subsequent write to that path is allowed regardless of content).
+
+That means generating a large file's full content on the first attempt is wasted: the attempt
+is denied and you must re-emit the entire content on the retry — paying ~2× output tokens for
+every large new file.
+
+**Rule — when creating a new file (or fully rewriting a large one):**
+
+1. First Write to that path is a **minimal stub** (one line, or empty).
+2. Present the gate's facts / do the real investigation (this is the gate's actual quality
+   purpose — keep it for code).
+3. Write the **full content** on the second call — it passes on the first real attempt.
+
+Full content is emitted **once**. Scope note: the win is **large new-file Writes**. `Edit`s
+also gate once per file, but `old_string`/`new_string` are small, so stub-first isn't worth
+it there. Markdown doc trees are already gate-exempt via `GATEGUARD_EDIT_EXEMPT` — no stub
+needed for those.
+
 ---
 
 ### Agent selection (how to build the plan internally)