Draek2077

release

Cut a release of Otto - the one streamlined runbook. Default is a stable patch. Use when the user says "release", "release otto", "ship", "ship stable", "cut a release", "new version", "release:patch", "promote", "release beta", or "/release". Handles stable-patch (default), beta, and promote in one place.

otto-loop

Run an agent loop until an exit condition is met. Use when the user says "loop", "babysit", "keep trying until", "check every X", "watch", or wants iterative autonomous execution.

otto-advisor

Spin up a single agent as an advisor - second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an outside take without delegating the work itself.

otto-committee

Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a hard planning problem.

otto-handoff

Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent.

Data & Documents Listed

archify

Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.

otto-ingest-project-knowledge

Convert a conversation, document, decision record, or research result into evidence-backed Otto project knowledge proposals. Use when a user asks to capture, ingest, remember, or preserve durable project information.

otto-onboard-project

Onboard a repository into Otto project knowledge by bootstrapping the `.otto` Markdown store, researching the codebase, documentation, Git history, active initiatives, and external references, and recording evidence-backed draft pages for review. Use when a user asks to onboard, initialize, seed, or build project knowledge for a new or existing repository.

otto-project-knowledge

Operate Otto's project knowledge safely: query pages, manage project charters and delivery, evaluate references, update current truth with reasons, append evidence, and review status. Use when an agent needs to read or change durable project knowledge.

otto

Otto reference for managing agents and worktrees. Load whenever you need to create agents, send them prompts, or manage worktrees.

otto-setup-project-knowledge

Initialize and verify Otto's project knowledge store for a project. Use when a user asks to set up, enable, initialize, or prepare project knowledge before seeding it.

otto-help

Answer questions about the Otto product and app, including setup, configuration, connectivity, providers, workspaces, updates, logs, and troubleshooting. Use when a user inside Otto asks how Otto works, how to configure it, or why something is broken; use the otto skill instead to operate agents and workspaces through MCP or the CLI.

otto-plugin

Build and manage trusted local Otto plugins. Use when the user asks to create, edit, install, reload, enable, disable, remove, or troubleshoot an Otto plugin; register a full agent provider or plugin settings screen; add lifecycle hooks; transform agent configuration, environment, MCP servers, or workspace creation; automate permissions or turn follow-ups; add a native surface, sidebar item, or workspace panel; add Command Center items or slash commands; add composer pills or attachment sources; transform, render, or append agent timeline items; contribute a theme; use Otto from plugin code; or add plugin RPCs.