feat(be38-5524): GREEN — add artifact review before writing to both skills

Add artifact review sections to both onboarding and architect-foundation
SKILL.md files. Present artifacts for approval, show diffs for existing.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: JoeOakhartNava

plugins/dso/skills/architect-foundation/SKILL.md

@@ -160,6 +160,15 @@ The accepted recommendations from this phase will be materialized into `ARCH_ENF
 
 ---
 
+## Phase 2.75: Artifact Review Before Writing
+
+Before generating or writing any enforcement artifact to disk, present the full content for user review and approval.
+
+- **Present each artifact** in a fenced code block so the user can review the complete content before it is written.
+- **For files that already exist** (such as `CLAUDE.md` or `ARCH_ENFORCEMENT.md`), show a diff against the existing content rather than presenting full replacement. The existing diff makes it clear which lines are being added, modified, or removed without silently overwriting prior decisions.
+- Ask: "Does this look right? Should I write this file?"
+- Wait for explicit approval before using the Write tool.
+
 ## Phase 3: The Enforcer (Deterministic Guardrails)
 
 Treat "Architecture" as something that can be tested. Generate **Fitness Functions** and **enforcement infrastructure** using tools appropriate for the chosen stack. Architecture enforcement operates at multiple layers — each layer catches violations at a different point in the development cycle.

plugins/dso/skills/onboarding/SKILL.md

@@ -299,6 +299,15 @@ Any corrections before I finalize this?
 
 Wait for the user to confirm or correct. Update the scratchpad with any corrections.
 
+### Step 1.5: Artifact Review Before Writing
+
+Before writing any artifact to disk, present the full content for user review and approval. Do NOT write files without explicit approval.
+
+- **Present each artifact** in a fenced code block so the user can review the complete content before it is written.
+- **For files that already exist** (such as `.claude/dso-config.conf` or `CLAUDE.md`), show a diff against the existing content rather than presenting full replacement. Highlight only the lines being added, changed, or removed so the user can see exactly what will change. Showing the existing diff lets the user verify that no existing configuration is being silently overwritten.
+- Ask: "Does this look right? Should I write this file?"
+- Wait for explicit approval before using the Write tool.
+
 ### Step 2: Write .claude/project-understanding.md
 
 After the user confirms the summary (or provides corrections), write the findings to a structured, human-readable artifact using the Write tool. This file is the lasting record of everything the onboarding conversation learned.