Results for “run-order”

Turn raw MATLAB code into a published .mltbx toolbox — full pipeline from scope definition through packaging and release. Drives 8 phases with human checkpoints, enforcing ordering and dependencies. Use when asked to package, create a toolbox, or run the files-to-package pipeline.

Run structured What-If scenario analysis with 4-6 branch possibility exploration (best, likely, worst, wild card, contrarian, second-order). Use for speculative questions about uncertain futures, strategic forks, contingency planning, or stress-testing decisions.

Run a full pipeline for a task. Orchestrates roles through stages (standalone or HOTL-integrated).

Turn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty, simplicity, and any LLM / VLM / Diffusion / RL-based contribution.

Use the status-briefing skill to run `pk-reconcile session-start`, then

Manage R&D program budgets with F&A splits, track burn rate and runway against milestones, and route capitalize-vs-expense decisions to a named finance owner.

Append structured execution traces across operational, cognitive, and contextual surfaces with minimal overhead. Load when inspecting agent runs, logging tool calls and observations, enabling post-run debugging, or pairing with structured-planning step IDs. Also triggers on "trace this run", "log execution", "agent observability", "run log", or when fault-localize needs evidence. Default-on during multi-step plans. Traces live at .agent-loom/traces/ — git-ignored by default.

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

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

Provides a sandboxed execution environment for running code, scripts, and automated workflows with resource capping and network isolation.

PR Fleet

Provides a Codex-native entry point for the rch operator skill, directing the agent to load the source skill and follow its runtime contract.

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

Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation. Use when marketing, sales, and customer success workflows need clearer operational structure.

Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation. Use when marketing, sales, and customer success workflows need clearer operational structure.

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

Provides a sandboxed execution environment for running code snippets, automating tasks, and deploying logic across multiple languages with resource capping and network isolation.

Use to find where support routing is failing — misrouted contacts, reassignment chains, unassigned work, and queues nobody owns. Trigger for "why do tickets bounce between teams", "are we routing correctly", "tickets sitting unassigned", "how many tickets get reassigned", ticket ping-pong, or reviewing routing rules and queue design.

Write an operational runbook any qualified operator can execute under pressure, with verification, failure paths, and escalation.

The instruction to profile before optimizing survives because intuition about

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.

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does, ranking failure modes by impact, likelihood, and cheapness to test.

Run shell commands in the background with output capture and completion callbacks. Use when a command might take more than ~30 seconds (builds, tests, deployments, data processing) and you want to keep working while it runs.

Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.

Burn HUD

Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation. Use when marketing, sales, and customer success workflows need clearer operational structure.

Designing GitHub Actions workflows in depth: trigger strategy, security hardening, performance optimization, PR automation, and Reusable Workflow design.

Apply Boyd's OODA loop to navigate fast-moving, uncertain, or competitive situations — Observe what is actually happening, Orient through mental models and context, Decide on the clearest path, Act quickly, then loop again. Load when the situation is changing faster than the current plan, when a competitive response is needed, when the user is stuck in analysis paralysis in a dynamic environment, when shipping under uncertainty, or when deep-thinking diagnoses a fast-moving / competitive frame. Triggers on "what should we do right now", "the situation is changing", "how do we respond to this", "competitive response", "we need to move fast", or "we're stuck deciding". Based on John Boyd's OODA loop — Observe, Orient, Decide, Act — adapted for product and business contexts (OODA Canvas 2026).

Coaches runners with training plans, pace calculations, race strategies, and form analysis

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