Results for “run-order”

Design and optimize revenue operations, including lead lifecycle rules, scoring, routing, handoffs, and CRM process automation for marketing, sales, and customer success alignment.

Routes requests into the correct obsidian-mind mode: install, daily session loop, capture, review, maintenance, multi-agent wiring, or semantic search, using a ready-made Obsidian vault template for persistent agent memory.

Tracks team OKRs with quarter banner, objective columns, key result progress bars, owner avatars, and status pills.

Drafts structured goal-loop prompts for long-running agent work with verifiable stop conditions, validation commands, and documentation requirements.

Resume an interrupted workflow run with verify-first strategy — loads sidecar state, verifies the last step, and continues execution.

Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session

Builds, validates, schedules, and dynamically modifies DAG execution graphs. Decomposes problems into nodes with dependencies, performs topological sorting, detects cycles, resolves conflicts, and schedules wave-based parallel execution. Use when designing a DAG structure, validating dependencies, planning execution order, or modifying a DAG at runtime. Activate on "build DAG", "plan workflow", "DAG dependencies", "topological sort", "schedule execution", "modify DAG", "replan". NOT for executing DAGs (use dag-runtime), validating outputs (use dag-quality), or matching skills to nodes (use dag-skills-matcher).