This skill does not describe the synchronization workflow. The workflow lives in one place: the companion file references/plan.md, beside this skill. That file is a complete VIPER plan and is the canonical source of truth. This skill only explains how to materialize it and run it.
How Hermes monitors and steers long-running sandboxed.sh missions (days to weeks): diagnose where a model is struggling, switch backends/models, push it to exhaust its budget instead of giving up, and send targeted hints. Trigger terms: mission, sandboxed.sh, babysit, monitor, /goal, switch backend, stalled, resume…
Argument shapes for the 5 built-in workflow patterns — deep-research, adversarial-review, code-review, multi-perspective, codebase-audit — runnable via the workflow tool's name input, without slash-command syntax. Use for requests like "research X", "fact-check/adversarially review this", "review this diff/PR"…
Usa esta skill cuando el usuario pida crear, redactar o revisar una especificación (spec) de una funcionalidad. Guía una entrevista de requisitos y produce un spec.md siguiendo la plantilla del equipo.
Turn any source that describes how a kind of task gets done (a SKILL.md, a chat log, a runbook, plain prose) into a runnable Morph trace. Lift it into a DAG, write a contract per step, place inputs, and drive the full run lifecycle to verify it. Use whenever someone wants to make a trace from a source.
Prescriptive Q&A workflow for designing agentic pipelines, multi-model councils, sub-agent hierarchies, and tool-loop hardening for any domain. Use when the user asks to "design an agent", "design a multi-agent system", "should I use a council/debate", "build a [domain] review agent" (HAZOP, finance, tutorial…
Produce a high-confidence, CONCISE implementation / architecture / strategy PLAN that follows the OMC plan system end to end. It first runs OMC's real requirements interview (auto-chains the omc-plan skill: one question at a time, explore-first, Analyst consult) to produce an initial plan in .omc/plans/, then DEEPENS…
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Doctor Strange — causal sand-table simulation via parallel universe subagents. Models actors, incentives, constraints, feedback loops, state changes, and failure modes before rendering how a future event may unfold step by step, like a human mentally rehearsing multiple futures. Stores simulations as persistent memory…
An effort-estimation method for agent-spec Task Contracts, which are structured descriptions of software work. It estimates work in rounds, meaning cycles of an AI agent doing and checking tasks.
Module Loop and Iteration Skill for orchestrating multi-phase penetration testing workflows. Use when coordinating sequential tool execution, managing dependencies between reconnaissance and vulnerability scanning modules, implementing adaptive fallback strategies, or managing workflow state across iterations.…
Plan and optionally execute a large pull request split into small stacked PRs. Use for PR breakdown, split PR, stacked PRs, branch decomposition, oversized diffs, gh-stack, Graphite, git range-diff, or PR too large.
Generate checklist-first CodexBridge /agent drafts from natural-language intake using bounded action routing, skill-owned task typing, scope clarification, and immutable prompt scaffolds. Use when implementing, testing, or simulating first-host /agent add or bare /agent draft creation, especially for repo-aware code…
A portable orchestrator that completes a high-level task through 5 stages — clarify → context-gather → plan → implement → verify. Each stage hands off via file artifacts, and a stage is skipped when its artifact already exists. The plan is decomposed into a task graph (DAG); independent nodes run in parallel…
Multi-LLM collaborative brainstorming and planning. Use when user explicitly requests consultation with multiple AI models (ChatGPT, Gemini, other LLMs) before presenting an implementation plan, or asks to "consult the council", "ask other models", or "get perspectives from other AIs". Queries external LLM APIs…
Get an independent architecture/implementation plan from Anthropic Claude (Fable, a different vendor's model) running Claude Code's native plan mode, from inside a non-Claude host such as Codex. Use mid-execution when work hits a genuine design fork or high-stakes decision that should not be settled unilaterally. Not…
Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).
A job-description analysis skill that turns a vacancy listing and a candidate’s background into an HTML report about fit, gaps, interview topics, and application strategy.
A control system for planning and continuing long Chinese fiction with recurring characters, multiple plotlines, and persistent world rules. It keeps project facts, chapter plans, style requirements, and changing story state in organized files.
Produce an implementation plan at .turbo/plans/ .md. Use when the user asks to "draft a plan", "draft the plan", "write an implementation plan", "plan this change", "create an implementation plan", or needs a first-draft plan file before refinement.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: