oh-my-customcode 0.59.0 → 0.60.0

package/dist/cli/index.js

@@ -9325,7 +9325,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.59.0",
+    version: "0.60.0",
     description: "Batteries-included agent harness for Claude Code",
     type: "module",
     bin: {

package/dist/index.js

@@ -1672,7 +1672,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "0.59.0",
+  version: "0.60.0",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "0.59.0",
+  "version": "0.60.0",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {

package/templates/.claude/rules/MUST-agent-design.md

@@ -32,6 +32,7 @@ escalation:              # Model escalation policy (optional)
   threshold: 2           # Failures before advisory
 soul: true                 # Enable SOUL.md identity injection
 isolation: worktree | sandbox  # worktree = git worktree, sandbox = restricted bash
+sandboxFailIfUnavailable: true  # Exit if sandbox unavailable (v2.1.83+)
 background: true           # Run in background
 maxTurns: 10               # Max conversation turns
 maxTokens: 100000          # Per-turn token ceiling
@@ -39,6 +40,7 @@ mcpServers: [server-1]     # MCP servers available
 hooks:                     # Agent-specific hooks
   PreToolUse:
     - matcher: "Edit"
+      if: "Edit(*.md)"      # Conditional filter (permission rule syntax, v2.1.85+)
       command: "echo hook"
 permissionMode: bypassPermissions  # Permission mode
 disallowedTools: [Bash]    # Tools to disallow
@@ -48,7 +50,7 @@ limitations:               # Negative capability declarations
 domain: backend              # backend | frontend | data-engineering | devops | universal
 ```
 
-> **Note**: `isolation`, `background`, `maxTurns`, `maxTokens`, `mcpServers`, `hooks`, `permissionMode`, `disallowedTools`, `limitations` are supported in Claude Code v2.1.63+. Hook types `PostCompact`, `Elicitation`, `ElicitationResult` require v2.1.76+.
+> **Note**: `isolation`, `background`, `maxTurns`, `maxTokens`, `mcpServers`, `hooks`, `permissionMode`, `disallowedTools`, `limitations` are supported in Claude Code v2.1.63+. Hook types `PostCompact`, `Elicitation`, `ElicitationResult` require v2.1.76+. `CwdChanged`, `FileChanged` hook events and `managed-settings.d/` drop-in directory require v2.1.83+. Conditional `if` field for hooks requires v2.1.85+.
 
 <!-- DETAIL: Isolation/Token/Limitations/Escalation details
 ### Isolation Modes

package/templates/.claude/skills/evaluator-optimizer/SKILL.md

@@ -33,6 +33,27 @@ evaluator-optimizer:
   max_iterations: 3               # Default, hard cap: 5
 ```
 
+### Pre-Negotiation (Sprint Contract Pattern)
+
+Optional phase where generator and evaluator agree on rubric interpretation before the first iteration. Inspired by Anthropic's harness design for long-running applications.
+
+```yaml
+evaluator-optimizer:
+  pre_negotiation:
+    enabled: true              # Default: false
+    rounds: 1                  # Negotiation rounds (1-2)
+  generator:
+    agent: fe-design-expert
+    ...
+```
+
+When enabled:
+1. Generator receives the rubric and proposes its interpretation + planned approach
+2. Evaluator reviews and may adjust rubric weights or add clarifications
+3. Both proceed with aligned expectations, reducing wasted iterations
+
+Use when: tasks requiring 3+ iterations consistently, or when generator-evaluator score disagreements exceed 0.3.
+
 ### Parameter Details
 
 | Parameter | Required | Default | Description |
@@ -307,3 +328,38 @@ When ecomode is active (R013), compress output:
 - The evaluator prompt MUST include the full rubric to ensure consistent scoring
 - Iteration state (best score, best output) is tracked by the orchestrator
 - The hard cap of 5 iterations prevents runaway refinement loops
+
+## Domain Examples
+
+### UI Generation (Anti-AI-Slop)
+
+For UI/design generation tasks, use weighted rubrics that penalize generic AI patterns:
+
+```yaml
+evaluator-optimizer:
+  generator:
+    agent: fe-design-expert
+    model: sonnet
+  evaluator:
+    agent: fe-design-expert
+    model: opus
+  rubric:
+    - criterion: originality
+      weight: 0.40
+      description: "No stock patterns (centered hero + 3-card grid). Unique layout, typography choices, color relationships."
+    - criterion: craft
+      weight: 0.35
+      description: "Intentional spacing, consistent type scale, purposeful color usage. Details that show care."
+    - criterion: functionality
+      weight: 0.25
+      description: "Accessibility (WCAG 2.1 AA), responsive behavior, interaction states."
+  quality_gate:
+    type: score_threshold
+    threshold: 0.85
+  pre_negotiation:
+    enabled: true
+```
+
+Weight ordering (originality > craft > functionality) follows Anthropic's anti-slop principle: functionality is table stakes, but originality and craft distinguish quality output from generic AI generation.
+
+Integration: Works with [impeccable-design](/skills/impeccable-design) skill for design language enforcement.

package/templates/.claude/skills/professor-triage/SKILL.md

@@ -156,7 +156,7 @@ Template:
 ## Pending Actions (Confirmation Required)
 ```
 
-**5B: Issue comments** — Delegate to mgr-gitnerd to post on each analyzed issue:
+**5B: Issue comments (MANDATORY)** — Every analyzed issue MUST receive a triage comment. This is not optional — even for issues created in the same session or with existing analysis. Skipping comments breaks the triage audit trail. Delegate to mgr-gitnerd to post on each analyzed issue:
 
 ```
 ## 🔬 Professor Triage — Cross-Analysis Result
@@ -170,6 +170,15 @@ Template:
 _Cross-analyzed by `/professor-triage` with {N} related issues_
 ```
 
+### Phase 5C: Comment Verification Gate
+
+Before proceeding to Phase 6, verify ALL analyzed issues received comments:
+```bash
+# For each issue NNN in the batch:
+gh issue view NNN --json comments --jq '.comments | map(select(.body | contains("Professor Triage"))) | length'
+# Must be >= 1 for every issue. If any is 0, Phase 5B was skipped — go back and post.
+```
+
 ### Phase 6: Act
 
 Delegate ALL GitHub operations to mgr-gitnerd.

package/templates/.claude/skills/stuck-recovery/SKILL.md

@@ -25,6 +25,7 @@ Detects when tasks are stuck in repetitive failure loops and advises recovery st
 | Model escalation | Agent retry loop | Trigger model-escalation advisory |
 | Alternative approach | Edit loop detected | Suggest different file/method |
 | Human intervention | All automated strategies exhausted | Ask user for guidance |
+| Context reset | Long-running task (>30min) or context >80% | Structured handoff: save state to memory, create fresh session with task summary |
 
 ## Architecture
 
@@ -53,3 +54,26 @@ PostToolUse (Edit, Write, Bash, Task) → stuck-detector.sh
 - Respects R010 (advisory only, orchestrator decides)
 - Uses same PPID-scoped temp file pattern as other hooks
 - Works with task-outcome-recorder.sh data when available
+
+## Context Reset Strategy
+
+For long-running tasks (>30 minutes) or when context usage exceeds 80%, context reset is preferred over compaction:
+
+1. **Save state**: Write current progress, decisions, and open items to native auto-memory
+2. **Create handoff**: Generate structured task summary with:
+   - Completed steps and their outcomes
+   - Current step and its state
+   - Remaining steps
+   - Key decisions made and their rationale
+3. **Reset**: Start fresh session with handoff document as input
+
+Context reset preserves decision quality by avoiding the information loss inherent in compaction. Based on Anthropic's finding that models experience "context anxiety" — prematurely concluding tasks due to perceived token limits.
+
+### When to Use
+
+| Condition | Strategy |
+|-----------|----------|
+| Context < 60% | Continue normally |
+| Context 60-80% | Consider `/compact` |
+| Context > 80% OR duration > 30min | Context reset recommended |
+| Repeated compaction in same session | Context reset required |

package/templates/.claude/skills/workflow/SKILL.md

@@ -1,20 +1,20 @@
 ---
-name: workflow
-description: Invoke YAML-defined workflows by name — /workflow omcustom-dev runs the full pipeline
+name: omcustom:workflow
+description: Invoke YAML-defined workflows by name — /omcustom:workflow auto-dev runs the full pipeline
 scope: harness
 user-invocable: true
 effort: high
 argument-hint: "<workflow-name> | (no args to list available)"
 ---
 
-# /workflow — Workflow Invocation
+# /omcustom:workflow — Workflow Invocation
 
 ## Usage
 
 ```
-/workflow omcustom-dev     # Run the omcustom-dev workflow
-/workflow                  # List available workflows
-/workflow:resume           # Resume a halted workflow
+/omcustom:workflow auto-dev     # Run the auto-dev workflow
+/omcustom:workflow                  # List available workflows
+/omcustom:workflow:resume           # Resume a halted workflow
 ```
 
 ## Behavior
@@ -24,7 +24,7 @@ argument-hint: "<workflow-name> | (no args to list available)"
 Scan `workflows/*.yaml` and display:
 ```
 Available workflows:
-  omcustom-dev — verify-done issues release batch: triage → plan → implement → verify → PR
+  auto-dev — verify-done issues release batch: triage → plan → implement → verify → PR
 ```
 
 ### Run Mode (with workflow name)
@@ -35,7 +35,7 @@ Available workflows:
 4. Invoke workflow-runner skill with the loaded definition
 5. Report completion or failure
 
-### Resume Mode (/workflow:resume)
+### Resume Mode (/omcustom:workflow:resume)
 
 1. Check for state file: `/tmp/.claude-workflow-*-{PPID}.json`
 2. If found: show halted workflow name and failed step

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.59.0",
+  "version": "0.60.0",
   "lastUpdated": "2026-03-24T00:00:00.000Z",
   "components": [
     {

package/templates/workflows/{omcustom-dev.yaml → auto-dev.yaml}

@@ -1,8 +1,8 @@
-# /workflow:omcustom-dev — Full-auto release pipeline
-# Collects verify-done issues → triage → plan → implement → verify → PR
+# /omcustom:workflow auto-dev — Full-auto release pipeline
+# Collects verify-done issues → triage → plan → implement → verify → PR → followup
 
-name: omcustom-dev
-description: "verify-done issues release batch: triage → plan → implement → verify → PR"
+name: auto-dev
+description: "verify-done issues release batch: triage → plan → implement → verify → PR → followup"
 mode: auto
 error: halt-and-report
 
@@ -33,3 +33,7 @@ steps:
   - name: release
     action: create-pr
     description: Create release branch and pull request
+
+  - name: followup
+    skill: post-release-followup
+    description: Recommend follow-up actions — user chooses to execute now or register as issues