timjensgrossinger

threnody-fast-review

Fast broad code review swarm: one read-only host agent per file, then one synthesis agent. Use when asked for a fast swarm review, one-agent-per-file review, broad review sweep, ordinary swarm review, or when reviewing many files where coverage and speed matter more than per-dimension depth.

threnody-fullstack

Build frontend, backend, and API in parallel with Threnody using contract-first DAG waves. Use for full-stack app scaffolding, OpenAPI-first development, parallel UI and service agents, or integration smoke tests after fanout.

threnody-plan

Threnody planning mode for normal orchestration and swarms. Use when user asks to plan, decompose, show waves, dry run, preview swarm, or before multi-file work. Supports plan-only (stop for approval) or plan-then-execute.

threnody-routing

Threnody MCP routing and host-native execution. Use when route_task, routing guard, execution_hint, host_spawn, HostNativeRequired, or utility-only delegation (delegation_utilities_enabled) is involved.

threnody-swarm-review

Run a complexity-gated review swarm: fans out one agent per (file × dimension) — logic, security, edge/null, types, performance — then synthesizes findings into a ranked report. Model selection per agent routed through Threnody. Use for deep parallel review, security-critical audit, threat-modeling, or explicit dimension-focused review. For broad or ordinary swarm review, prefer threnody-fast-review. Read-only — never writes or edits target files.

threnody-swarm

Start and run Threnody execute_swarm with host-native host_spawn_waves, topology selection (dag/star/hierarchical/auto), budget preview, and resume. Use when user asks to swarm, fan out agents, or run multi-agent waves with swarm_id persistence.

threnody-task

Threnody normal orchestration via plan_task, decompose_task, and fleet_plan. Use for multi-file tasks, wave-based host Agent execution, or /fleet planning without a full execute_swarm contract.

threnody-workflow

Run a Threnody swarm with multi-queen consensus and learning THROUGH the Claude Code Dynamic Workflow feature, then save the run as a permanent, pre-tuned, zero-config /workflow command for coworkers. Use when asked to run a workflow, workflow-swarm, tier-aware workflow, or to save/share a reusable multi-agent workflow. Claude Code only.

threnody-subtasks

Monitor and control Threnody utility execute_subtask calls via list_subtasks, stop_subtask, and resume_subtask. Use when tracking delegated utility work (OpenCode, Aider, local endpoints) — not host-native swarms.