dannylee1020

Create or update Murph channel plugins for custom messaging providers. Use when the operator asks to add Slack or Discord style channel support outside Murph core.

Create or update Murph scoped plugins for integrations, tools, context sources, skills, or bundles. Use when the operator asks to add a local Murph capability without editing core source.

Create, preview, or switch Murph policy profiles. Use when the operator asks about autonomy, dry-run, queueing, send behavior, or policy rules.

Diagnose Murph setup, local server, provider, integration, plugin, and policy readiness. Use when the operator asks why Murph is not working or how to configure it.

Create or revise Murph runtime skills and Murph Agent Pi skills. Use when the operator asks to add guidance, skills, or behavior instructions.

Durable constrained optimization execution loop for long-running coding work. Use when a coding agent should capture user meaning, discover repo constraints and validation paths, build an optimization model and execution contract, create a file-backed workspace, execute with continuation, validate with evidence, re-optimize when new facts invalidate the plan, and continue through goal-mode tools until acceptance criteria or stop conditions are met.

Deep constrained optimization modeling for coding and product-engineering decisions. Use when a coding agent should capture user meaning, discover repo constraints and validation paths, inspect the system, identify objectives, system state, decision variables, domains, hard and soft constraint contracts, selected-plan binding constraints, execution-contract implications, multiple feasible models or architectures, sensitivity analysis, and interactive user tradeoffs before any implementation.

Execute an existing KKT model with deterministic drift guardrails. Use when a coding agent should pick up a completed kkt-model workspace, preserve the optimized model and guardrail contract, check model-readiness before mutation, implement the selected plan, validate with evidence, and finish without the long-running kkt-loop continuation machinery.

Constrained optimization workflow for ordinary coding requests. Use when a coding agent should capture user meaning, discover repo constraints and validation paths, build a mathematical-style optimization model, derive an execution contract, select a feasible implementation plan, execute the change, validate with evidence, and finish with a constraint audit.

Delegate an implementation or agent-driven end-to-end test through Nox in an isolated sandbox, or report the status of Nox tasks already dispatched in the current thread. Implementation runs publish successful changes; test runs retain validation evidence without publishing code. Use only when the user explicitly invokes $nox, asks to delegate a task, or asks for Nox task status.