Results for “rolldown”

Design a lead routing and SLA model someone can actually implement. The assignment rules, the round-robin or account-based logic, the SLA timers, and the fallbacks when a rep is out or a lead has no owner. Built for B2B RevOps teams, customizable to your CRM and your team shape. Trigger on "design lead routing", "who should get this lead", "build our SLA", "round robin rules", "leads are falling through", or any routing diagnostic.

Package an in-progress task on this cluster so a Claude agent on another cluster (MMM Young, CX3, HX1, Isambard) can pick it up, or resume a task handed off to this cluster. Use when the user says hand off / migrate / continue this on <cluster>, or asks you to pick up an existing handoff.

Sets up and audits the Claude Code harness for a project: CLAUDE.md, .claude/rules, skills, subagents, settings.json permissions, hooks, verification loop. Commands: kickoff (scaffold new setup), check-playbook (score an existing one), scouting-report (last scorecard), adjust (fix bloat/misplaced instructions), drill (turn advisory prose into real hooks/permissions/CI), decline (record an accepted risk), gameplan (work order with acceptance criteria before building), watch-film (check a diff against that order for scope creep/weakened tests/false claims). Use for setting up Claude Code, or on: "Claude ignores my CLAUDE.md", "it's huge and still misses things", "it said done but ran nothing", "it changed files I didn't ask about", "it weakened a test to pass", "rule, skill, or hook?", "is my setup any good". Not for code quality (code-audit), test coverage (test-assessment), one-off prompt wording (genie-proof-prompts), new skill authoring (skill-creator), or compacting a conversation (handoff).

Inspect, plan, and invoke safe cleanup for runtime-manager-owned state without binding the workflow to a specific host orchestrator or agent provider.

Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.

Launches a model evaluation batch with parameter collection, pre-flight checks, execution, and post-run analysis for interactive or foreground runs.

Drive a planned change to 100% coverage across an entire codebase when a prior agent run stopped early. Use whenever a refactor, migration, rename, rule-application, or sweeping edit was planned and partially executed but left incomplete — i.e.

Compact the current session into a single detailed handoff message that can be pasted into a fresh agent run. Use when switching context, ending a session, or avoiding context-window loss.