garrytan · agrawalparth08 · Jul 24, 2026
diff --git a/SKILL.md b/SKILL.md
@@ -452,51 +452,13 @@ At skill END before telemetry:
 ```
 
 
-## Model-Specific Behavioral Patch (claude)
+## Shared Conduct
 
-The following nudges are tuned for the claude model family. They are
-**subordinate** to skill workflow, STOP points, AskUserQuestion gates, plan-mode
-safety, and /ship review gates. If a nudge below conflicts with skill instructions,
-the skill wins. Treat these as preferences, not rules.
-
-**Todo-list discipline.** When working through a multi-step plan, mark each task
-complete individually as you finish it. Do not batch-complete at the end. If a task
-turns out to be unnecessary, mark it skipped with a one-line reason.
-
-**Think before heavy actions.** For complex operations (refactors, migrations,
-non-trivial new features), briefly state your approach before executing. This lets
-the user course-correct cheaply instead of mid-flight.
-
-**Dedicated tools over Bash.** Prefer Read, Edit, Write, Glob, Grep over shell
-equivalents (cat, sed, find, grep). The dedicated tools are cheaper and clearer.
-
-## Voice
-
-Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler.
-
-No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do.
-
-The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.
-
-## Completion Status Protocol
-
-When completing a skill workflow, report status using one of:
-- **DONE** — completed with evidence.
-- **DONE_WITH_CONCERNS** — completed, but list concerns.
-- **BLOCKED** — cannot proceed; state blocker and what was tried.
-- **NEEDS_CONTEXT** — missing info; state exactly what is needed.
-
-Escalate after 3 failed attempts, uncertain security-sensitive changes, or scope you cannot verify. Format: `STATUS`, `REASON`, `ATTEMPTED`, `RECOMMENDATION`.
-
-## Operational Self-Improvement
-
-Before completing, if you discovered a durable project quirk or command fix that would save 5+ minutes next time, log it:
-
-```bash
-~/.claude/skills/gstack/bin/gstack-learnings-log '{"skill":"SKILL_NAME","type":"operational","key":"SHORT_KEY","insight":"DESCRIPTION","confidence":N,"source":"observed"}'
-```
-
-Do not log obvious facts or one-time transient errors.
+Voice, model-specific behavioral patch, Completion Status Protocol, and
+Operational Self-Improvement rules shared by all gstack skills live in
+`~/.claude/skills/gstack/docs/shared-conduct.md`. Read it now with the Read
+tool unless it was already read earlier in this session, and apply it
+throughout this skill.
 
 ## Telemetry (run last)
 

diff --git a/autoplan/SKILL.md b/autoplan/SKILL.md
@@ -587,39 +587,13 @@ At skill END before telemetry:
 ```
 
 
-## Model-Specific Behavioral Patch (claude)
+## Shared Conduct
 
-The following nudges are tuned for the claude model family. They are
-**subordinate** to skill workflow, STOP points, AskUserQuestion gates, plan-mode
-safety, and /ship review gates. If a nudge below conflicts with skill instructions,
-the skill wins. Treat these as preferences, not rules.
-
-**Todo-list discipline.** When working through a multi-step plan, mark each task
-complete individually as you finish it. Do not batch-complete at the end. If a task
-turns out to be unnecessary, mark it skipped with a one-line reason.
-
-**Think before heavy actions.** For complex operations (refactors, migrations,
-non-trivial new features), briefly state your approach before executing. This lets
-the user course-correct cheaply instead of mid-flight.
-
-**Dedicated tools over Bash.** Prefer Read, Edit, Write, Glob, Grep over shell
-equivalents (cat, sed, find, grep). The dedicated tools are cheaper and clearer.
-
-## Voice
-
-GStack voice: Garry-shaped product and engineering judgment, compressed for runtime.
-
-- Lead with the point. Say what it does, why it matters, and what changes for the builder.
-- Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers.
-- Tie technical choices to user outcomes: what the real user sees, loses, waits for, or can now do.
-- Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path.
-- Sound like a builder talking to a builder, not a consultant presenting to a client.
-- Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay.
-- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant.
-- The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides.
-
-Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines."
-Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions."
+Voice, model-specific behavioral patch, Completion Status Protocol, and
+Operational Self-Improvement rules shared by all gstack skills live in
+`~/.claude/skills/gstack/docs/shared-conduct.md`. Read it now with the Read
+tool unless it was already read earlier in this session, and apply it
+throughout this skill.
 
 ## Context Recovery
 
@@ -751,26 +725,6 @@ Before building anything unfamiliar, **search first.** See `~/.claude/skills/gst
 jq -n --arg ts "$(date -u +%Y-%m-%dT%H:%M:%SZ)" --arg skill "SKILL_NAME" --arg branch "$(git branch --show-current 2>/dev/null)" --arg insight "ONE_LINE_SUMMARY" '{ts:$ts,skill:$skill,branch:$branch,insight:$insight}' >> ~/.gstack/analytics/eureka.jsonl 2>/dev/null || true
 ```
 
-## Completion Status Protocol
-
-When completing a skill workflow, report status using one of:
-- **DONE** — completed with evidence.
-- **DONE_WITH_CONCERNS** — completed, but list concerns.
-- **BLOCKED** — cannot proceed; state blocker and what was tried.
-- **NEEDS_CONTEXT** — missing info; state exactly what is needed.
-
-Escalate after 3 failed attempts, uncertain security-sensitive changes, or scope you cannot verify. Format: `STATUS`, `REASON`, `ATTEMPTED`, `RECOMMENDATION`.
-
-## Operational Self-Improvement
-
-Before completing, if you discovered a durable project quirk or command fix that would save 5+ minutes next time, log it:
-
-```bash
-~/.claude/skills/gstack/bin/gstack-learnings-log '{"skill":"SKILL_NAME","type":"operational","key":"SHORT_KEY","insight":"DESCRIPTION","confidence":N,"source":"observed"}'
-```
-
-Do not log obvious facts or one-time transient errors.
-
 ## Telemetry (run last)
 
 After workflow completion, log telemetry. Use skill `name:` from frontmatter. OUTCOME is success/error/abort/unknown.
@@ -878,6 +832,7 @@ Follow its instructions from top to bottom, **skipping these sections** (already
 - Search Before Building
 - Contributor Mode
 - Completion Status Protocol
+- Shared Conduct
 - Telemetry (run last)
 - Step 0: Detect platform and base branch
 - Review Readiness Dashboard

diff --git a/benchmark-models/SKILL.md b/benchmark-models/SKILL.md
@@ -456,51 +456,13 @@ At skill END before telemetry:
 ```
 
 
-## Model-Specific Behavioral Patch (claude)
+## Shared Conduct
 
-The following nudges are tuned for the claude model family. They are
-**subordinate** to skill workflow, STOP points, AskUserQuestion gates, plan-mode
-safety, and /ship review gates. If a nudge below conflicts with skill instructions,
-the skill wins. Treat these as preferences, not rules.
-
-**Todo-list discipline.** When working through a multi-step plan, mark each task
-complete individually as you finish it. Do not batch-complete at the end. If a task
-turns out to be unnecessary, mark it skipped with a one-line reason.
-
-**Think before heavy actions.** For complex operations (refactors, migrations,
-non-trivial new features), briefly state your approach before executing. This lets
-the user course-correct cheaply instead of mid-flight.
-
-**Dedicated tools over Bash.** Prefer Read, Edit, Write, Glob, Grep over shell
-equivalents (cat, sed, find, grep). The dedicated tools are cheaper and clearer.
-
-## Voice
-
-Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler.
-
-No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do.
-
-The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.
-
-## Completion Status Protocol
-
-When completing a skill workflow, report status using one of:
-- **DONE** — completed with evidence.
-- **DONE_WITH_CONCERNS** — completed, but list concerns.
-- **BLOCKED** — cannot proceed; state blocker and what was tried.
-- **NEEDS_CONTEXT** — missing info; state exactly what is needed.
-
-Escalate after 3 failed attempts, uncertain security-sensitive changes, or scope you cannot verify. Format: `STATUS`, `REASON`, `ATTEMPTED`, `RECOMMENDATION`.
-
-## Operational Self-Improvement
-
-Before completing, if you discovered a durable project quirk or command fix that would save 5+ minutes next time, log it:
-
-```bash
-~/.claude/skills/gstack/bin/gstack-learnings-log '{"skill":"SKILL_NAME","type":"operational","key":"SHORT_KEY","insight":"DESCRIPTION","confidence":N,"source":"observed"}'
-```
-
-Do not log obvious facts or one-time transient errors.
+Voice, model-specific behavioral patch, Completion Status Protocol, and
+Operational Self-Improvement rules shared by all gstack skills live in
+`~/.claude/skills/gstack/docs/shared-conduct.md`. Read it now with the Read
+tool unless it was already read earlier in this session, and apply it
+throughout this skill.
 
 ## Telemetry (run last)
 

diff --git a/benchmark/SKILL.md b/benchmark/SKILL.md
@@ -456,51 +456,13 @@ At skill END before telemetry:
 ```
 
 
-## Model-Specific Behavioral Patch (claude)
+## Shared Conduct
 
-The following nudges are tuned for the claude model family. They are
-**subordinate** to skill workflow, STOP points, AskUserQuestion gates, plan-mode
-safety, and /ship review gates. If a nudge below conflicts with skill instructions,
-the skill wins. Treat these as preferences, not rules.
-
-**Todo-list discipline.** When working through a multi-step plan, mark each task
-complete individually as you finish it. Do not batch-complete at the end. If a task
-turns out to be unnecessary, mark it skipped with a one-line reason.
-
-**Think before heavy actions.** For complex operations (refactors, migrations,
-non-trivial new features), briefly state your approach before executing. This lets
-the user course-correct cheaply instead of mid-flight.
-
-**Dedicated tools over Bash.** Prefer Read, Edit, Write, Glob, Grep over shell
-equivalents (cat, sed, find, grep). The dedicated tools are cheaper and clearer.
-
-## Voice
-
-Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler.
-
-No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do.
-
-The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.
-
-## Completion Status Protocol
-
-When completing a skill workflow, report status using one of:
-- **DONE** — completed with evidence.
-- **DONE_WITH_CONCERNS** — completed, but list concerns.
-- **BLOCKED** — cannot proceed; state blocker and what was tried.
-- **NEEDS_CONTEXT** — missing info; state exactly what is needed.
-
-Escalate after 3 failed attempts, uncertain security-sensitive changes, or scope you cannot verify. Format: `STATUS`, `REASON`, `ATTEMPTED`, `RECOMMENDATION`.
-
-## Operational Self-Improvement
-
-Before completing, if you discovered a durable project quirk or command fix that would save 5+ minutes next time, log it:
-
-```bash
-~/.claude/skills/gstack/bin/gstack-learnings-log '{"skill":"SKILL_NAME","type":"operational","key":"SHORT_KEY","insight":"DESCRIPTION","confidence":N,"source":"observed"}'
-```
-
-Do not log obvious facts or one-time transient errors.
+Voice, model-specific behavioral patch, Completion Status Protocol, and
+Operational Self-Improvement rules shared by all gstack skills live in
+`~/.claude/skills/gstack/docs/shared-conduct.md`. Read it now with the Read
+tool unless it was already read earlier in this session, and apply it
+throughout this skill.
 
 ## Telemetry (run last)
 

diff --git a/browse/SKILL.md b/browse/SKILL.md
@@ -454,51 +454,13 @@ At skill END before telemetry:
 ```
 
 
-## Model-Specific Behavioral Patch (claude)
+## Shared Conduct
 
-The following nudges are tuned for the claude model family. They are
-**subordinate** to skill workflow, STOP points, AskUserQuestion gates, plan-mode
-safety, and /ship review gates. If a nudge below conflicts with skill instructions,
-the skill wins. Treat these as preferences, not rules.
-
-**Todo-list discipline.** When working through a multi-step plan, mark each task
-complete individually as you finish it. Do not batch-complete at the end. If a task
-turns out to be unnecessary, mark it skipped with a one-line reason.
-
-**Think before heavy actions.** For complex operations (refactors, migrations,
-non-trivial new features), briefly state your approach before executing. This lets
-the user course-correct cheaply instead of mid-flight.
-
-**Dedicated tools over Bash.** Prefer Read, Edit, Write, Glob, Grep over shell
-equivalents (cat, sed, find, grep). The dedicated tools are cheaper and clearer.
-
-## Voice
-
-Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler.
-
-No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do.
-
-The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.
-
-## Completion Status Protocol
-
-When completing a skill workflow, report status using one of:
-- **DONE** — completed with evidence.
-- **DONE_WITH_CONCERNS** — completed, but list concerns.
-- **BLOCKED** — cannot proceed; state blocker and what was tried.
-- **NEEDS_CONTEXT** — missing info; state exactly what is needed.
-
-Escalate after 3 failed attempts, uncertain security-sensitive changes, or scope you cannot verify. Format: `STATUS`, `REASON`, `ATTEMPTED`, `RECOMMENDATION`.
-
-## Operational Self-Improvement
-
-Before completing, if you discovered a durable project quirk or command fix that would save 5+ minutes next time, log it:
-
-```bash
-~/.claude/skills/gstack/bin/gstack-learnings-log '{"skill":"SKILL_NAME","type":"operational","key":"SHORT_KEY","insight":"DESCRIPTION","confidence":N,"source":"observed"}'
-```
-
-Do not log obvious facts or one-time transient errors.
+Voice, model-specific behavioral patch, Completion Status Protocol, and
+Operational Self-Improvement rules shared by all gstack skills live in
+`~/.claude/skills/gstack/docs/shared-conduct.md`. Read it now with the Read
+tool unless it was already read earlier in this session, and apply it
+throughout this skill.
 
 ## Telemetry (run last)
 

diff --git a/canary/SKILL.md b/canary/SKILL.md
@@ -579,39 +579,13 @@ At skill END before telemetry:
 ```
 
 
-## Model-Specific Behavioral Patch (claude)
+## Shared Conduct
 
-The following nudges are tuned for the claude model family. They are
-**subordinate** to skill workflow, STOP points, AskUserQuestion gates, plan-mode
-safety, and /ship review gates. If a nudge below conflicts with skill instructions,
-the skill wins. Treat these as preferences, not rules.
-
-**Todo-list discipline.** When working through a multi-step plan, mark each task
-complete individually as you finish it. Do not batch-complete at the end. If a task
-turns out to be unnecessary, mark it skipped with a one-line reason.
-
-**Think before heavy actions.** For complex operations (refactors, migrations,
-non-trivial new features), briefly state your approach before executing. This lets
-the user course-correct cheaply instead of mid-flight.
-
-**Dedicated tools over Bash.** Prefer Read, Edit, Write, Glob, Grep over shell
-equivalents (cat, sed, find, grep). The dedicated tools are cheaper and clearer.
-
-## Voice
-
-GStack voice: Garry-shaped product and engineering judgment, compressed for runtime.
-
-- Lead with the point. Say what it does, why it matters, and what changes for the builder.
-- Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers.
-- Tie technical choices to user outcomes: what the real user sees, loses, waits for, or can now do.
-- Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path.
-- Sound like a builder talking to a builder, not a consultant presenting to a client.
-- Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay.
-- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant.
-- The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides.
-
-Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines."
-Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions."
+Voice, model-specific behavioral patch, Completion Status Protocol, and
+Operational Self-Improvement rules shared by all gstack skills live in
+`~/.claude/skills/gstack/docs/shared-conduct.md`. Read it now with the Read
+tool unless it was already read earlier in this session, and apply it
+throughout this skill.
 
 ## Context Recovery
 
@@ -725,26 +699,6 @@ Write (only after confirmation for free-form):
 
 Exit code 2 = rejected as not user-originated; do not retry. On success: "Set `<id>` → `<preference>`. Active immediately."
 
-## Completion Status Protocol
-
-When completing a skill workflow, report status using one of:
-- **DONE** — completed with evidence.
-- **DONE_WITH_CONCERNS** — completed, but list concerns.
-- **BLOCKED** — cannot proceed; state blocker and what was tried.
-- **NEEDS_CONTEXT** — missing info; state exactly what is needed.
-
-Escalate after 3 failed attempts, uncertain security-sensitive changes, or scope you cannot verify. Format: `STATUS`, `REASON`, `ATTEMPTED`, `RECOMMENDATION`.
-
-## Operational Self-Improvement
-
-Before completing, if you discovered a durable project quirk or command fix that would save 5+ minutes next time, log it:
-
-```bash
-~/.claude/skills/gstack/bin/gstack-learnings-log '{"skill":"SKILL_NAME","type":"operational","key":"SHORT_KEY","insight":"DESCRIPTION","confidence":N,"source":"observed"}'
-```
-
-Do not log obvious facts or one-time transient errors.
-
 ## Telemetry (run last)
 
 After workflow completion, log telemetry. Use skill `name:` from frontmatter. OUTCOME is success/error/abort/unknown.