harnessed 3.4.2 → 3.4.3

package/workflows/verify/simplify/SKILL.md

@@ -5,7 +5,7 @@ description: |
   sister ~/.claude/CLAUDE.md "Verify 阶段 — 末尾 code-simplifier" verbatim)。
   schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
   (code-simplifier) + 1 phase (gate ref is_final_step 末尾串行)。
-  Triggered by harnessed CLI `harnessed verify-simplify --phase <num>` or slash command
+  Triggered by slash command
   `/verify-simplify` after `harnessed setup`.
 trigger_phrases:
   - "verify simplify"
@@ -47,26 +47,39 @@ Sister `workflows/judgments/stage-routing.yaml`:
 - ✅ **触发**: verify chain 末尾步骤 (所有其他 verify sub 已 ship, 准备 code 简化收尾)
 - ❌ **跳过**: verify chain 中间步骤 (避免过早简化干扰后续 review)
 
-## CLI invocation
-
-```bash
-# Dry-run preview — arbitrate-only, never spawns SDK.
-harnessed verify-simplify --phase <num> --dry-run --non-interactive
-
-# Apply path — real SDK spawn (gate eval true 时).
-harnessed verify-simplify --phase <num> --apply
-```
-
+<!-- v3.4.3-dual-path-invocation -->
 ## How to invoke
 
-Use the SlashCommand tool to run: `{{ capabilities.code-simplifier.cmd }}`
-
-(If a `⚠️ ... not installed` warning was printed by `harnessed setup`, the backing
-capability is missing on disk. Install it (`claude plugin install <name>` for
-plugins, or follow the official install instructions for user-skills — e.g. for
-gstack: `git clone https://github.com/garrytan/gstack.git ~/.claude/skills/gstack` then
-`cd ~/.claude/skills/gstack && ./setup`), then re-run `harnessed setup` to re-render
-this SKILL.md and clear the warning.)
+**Preferred path** (when the upstream specialist is installed): use the SlashCommand tool to run `{{ capabilities.code-simplifier.cmd }}` — the upstream specialist takes over.
+
+**Fallback path** (when the upstream isn't installed or returns no result): use the Task tool to spawn a general-purpose subagent with this prompt:
+
+> You are a **Code Simplifier (tail step)**.
+>
+> **Mission**: Last step of verify chain (`phase.is_final_step == true`) after all reviews ship. Remove duplication / multi-purpose helpers / unused code / over-abstraction from the diff. Keep tests passing.
+>
+> **Default-suspect mode**: assume the change is broken / risky / incomplete until proven otherwise. Cite `file:line` for every finding; do not generalize.
+>
+> **Review checklist**:
+> 1. Look only at files changed in this phase — don't simplify unrelated code
+>
+> 2. Duplication: same logic in 2+ places → extract once, but only if both sites benefit
+>
+> 3. Dead code: unused exports / unreachable branches / commented-out blocks
+>
+> 4. Magic numbers used in >1 place → named constant
+>
+> 5. Over-abstraction: generics / interfaces with 1 implementer → inline
+>
+> 6. Comments that lie or duplicate the code → delete (no-comments-default karpathy rule)
+>
+> 7. Run tests after each simplification; revert if anything fails
+>
+> **Output format**: structured report with severity-classified findings (applied / candidate-flagged / skipped (too risky for final step)). One finding per line: `[severity] file:line — problem (one sentence); fix: suggested change`. If no findings, say so explicitly. No preamble, no end-of-report summary.
+
+(Role prompt is self-contained — works even when the upstream `code-simplifier` user-skill / plugin isn't installed.)
+
+(Sister `~/.claude/commands/verify-simplify.md` is also generated by `harnessed setup` so `/verify-simplify` is a real platform slash command — both files carry the same dual-path instruction. Previous v3.4.x `harnessed verify-simplify --apply` CLI claims are removed; that subcommand was never implemented.)
 
 ## References