mifunedev

TRIGGER when: asked to delegate work, execute or parallelize a plan, "run this plan", "delegate this", or after /prd or plan creation. Decomposes work by dependency, launches worker sub-agents in parallel waves, validates completion, and reports results while preserving failure isolation and recursion limits.

Dispatcher for the harness wiki knowledge base — routes the first token of $ARGUMENTS to one of three subcommands: ingest, query, or lint. The corpus lives at .oh/skills/wiki/corpus/ (entity pages) and corpus/raw/ (immutable snapshots), owned by this skill and gitignored-by-default (curated entries are whitelisted into git with `git add -f`). Canonical schema: .oh/skills/wiki/references/schema.md. Full per-subcommand procedures live in references/{ingest,query,lint}.md. Always logs per the Memory Improvement Protocol. TRIGGER when: "add to wiki", "capture this page", "snapshot this source", "ingest <url|path>", or promoting a sub-agent draft -> ingest; "what does the wiki say about X", "find wiki entries for X", "look up X in the wiki" -> query; "lint the wiki", "regenerate the wiki index", "find stale/orphaned wiki entries" -> lint.

Turn a source scenario into a publishable blog post. First supported playbook: Loom/demo-to-blog, where a raw notes file plus Loom screenshots become a polished site post after Advisor briefing, photo/text alignment audit, site convention audit, narrative/fact-check audit, source-faithful image handling (exact URLs or local files downloaded from them), optional social/channel-promotion artifact generation, and build verification. Manual-invoke only because it writes content and may spawn delegates. TRIGGER when: /blog <scenario> invoked; asked to create a blog post from a Loom/video/demo/transcript/screenshots; asked to turn .claude/specs/<name>/ demo.md into an openharness-web blog post.

Start, inspect, or stop T3 Code (`npx t3`) in the Open Harness sandbox. Use this for the browser-based T3 Code harness on port 3773, including tmux launch, pairing URL discovery, logs, status, and shutdown. T3 Code wraps an already-authenticated Claude Code, Codex, or OpenCode backend. TRIGGER when: user asks to run T3 Code, start `npx t3`, open the T3 browser UI, get the T3 pairing URL, check T3 Code status/logs, or stop T3 Code.

Scientific session-closing retrospective: scan the current conversation, turn each signal into a falsifiable hypothesis, cite session evidence for AND against it, assign a verdict (supported / refuted / inconclusive) and a confidence level, then promote only supported, sufficiently-confident hypotheses into the harness memory tiers (.oh/memory/MEMORY.md, .oh/context/IDENTITY.md) behind a propose-then-confirm gate. Reflects on six learning/knowledge subsystems through the lens of this session — continual learning, context compression, reinforcement learning, wiki, docs, and memory scaffolding — and points at the deep-dive lint/audit skills rather than running them. Operationalizes the Memory Improvement Protocol (.oh/skills/retro/references/memory-protocol.md) as an explicit, evidence-driven, session-closing skill rather than a per-run afterthought. Always appends a log entry. TRIGGER when: /retro invoked, or session closing with decisions, surprises, or failures worth preserving.

Self-improvement loop: each hourly run implements the oldest open issue labeled `autopilot` that has no open PR. When the queue is empty it runs first-principles `/harness-audit` research, files its own `autopilot` ticket from the top-ranked finding, and builds that. Decomposes via the pm agent, then runs `/ship-spec --issue`, which owns the build end-to-end (the two compacts bracketing implement, a worktree Advisor, `/delegate` workers running `.oh/scripts/ralph.sh`, the `/eval` gate, and the `/pr-audit` promotable undraft) through to a ready-for-review PR whose description states why this item was selected. Harness-infra only (skills/rules/docs/scripts/crons/wiki) — never sandbox application code. Runs in its own per-run tmux session. Caps: 6 open autopilot PRs created per UTC day AND 10 total open; never auto-merges. TRIGGER when: the hourly .oh/crons/autopilot.md fires, or invoked manually on demand (e.g. /autopilot --dry-run to preview the next selection).

Open Harness git workflow: issues, branches, commits, PR titles/bodies, changelog discipline, worktrees, branch catch-up, stacked PRs, releases, and post-push CI checks. TRIGGER when: any chat mentions git, GitHub, branches, commits, pushes, pulls, PRs, issues, worktrees, merge conflicts, dirty workspaces, changelog entries, release branch/tag workflow, or project git conventions.

Explain the Open Harness architecture, layout, and conventions. Use this skill when the user asks about project structure, layout, git workflow, rules, or how things are organized. Returns specific file paths and `path:line` citations. TRIGGER when: asked about harness structure, layout, conventions, rules, process, or project organization.

Score the default-loaded context budget across 4 dimensions and emit KEEP/TRIM/DEMOTE/CUT verdicts per file. Optional Tier-2 ablation harness removes a target file, runs a fixed probe suite, and measures behavior degradation — the only provably safe gate for cutting load-bearing content. TRIGGER when: asked to audit context window, check default context load, "what's in my context", evaluate rules for signal vs noise, or before/after any change to context/rules/ or CLAUDE.md.

Deliberate whole-session memory pass: scan the current conversation for durable behavioral patterns, run the qualify filter, classify surviving lessons by memory tier, propose MEMORY.md / IDENTITY.md additions for confirmation, then write only what was approved plus the mandatory log entry. Operationalizes the Memory Improvement Protocol (context/rules/memory.md) as an explicit, session-closing skill rather than a per-run afterthought. TRIGGER when: /reflect invoked explicitly, or when the session is closing and contains decisions, surprises, or failure modes worth preserving.

Open a URL in the headless agent-browser, with a preflight health check. Verifies agent-browser is installed and Chromium launches before navigating. Errors out with a diagnostic trace if anything fails. TRIGGER when: asked to open a page, browse a URL, take a screenshot, or test a site with agent-browser.

Check the CI pipeline status for the current branch after pushing changes. Reports pass/fail with failure details. Use this after every push to confirm your changes are truly done — CI must be green. TRIGGER when: after git push, after committing changes, when asked to check CI, or when verifying that work is complete.

Parallel execution coordinator. Decomposes a plan into discrete tasks, identifies parallelism via dependency analysis, and spawns worker sub-agents in waves to maximize throughput without sacrificing quality. Collects results, validates completeness, and reports a structured summary. TRIGGER when: asked to delegate work, execute a plan, parallelize tasks, "run this plan", "delegate this", or after /prd or plan creation.

Spawn 4 parallel sub-agents (PM, Implementer, Critic, Explorer) to audit the harness for improvements. Synthesizes findings into tier-ranked actionable list. Outputs recommended next 3 actions. TRIGGER when: asked to audit the harness, find improvements, review system health, "what should we fix", or periodically via heartbeat.

Explain the Open Harness architecture, layout, and conventions. Use this skill when the user asks about project structure, layout, git workflow, rules, or how things are organized. Returns specific file paths and `path:line` citations. TRIGGER when: asked about harness structure, layout, conventions, rules, process, or project organization.

Adaptive pre-work clarifier. Picks 2–4 task-specific questions via AskUserQuestion, echoes a brief scope summary, then proceeds. Refuses for trivial tasks. TRIGGER when: /interview invoked explicitly, OR before non-trivial work where scope/intent/constraints are ambiguous AND the user hasn't already specified them.