Menu
Orchestrate firmware rollouts with canary deployment and anomaly-gated advancement
Spawn nested sub-agents (agents that spawn sub-agents, up to depth=5) via Claude Code's native Task tool — for context-managed deep delegation
Author a workflow — either an MCP workflow template (persisted, lifecycle) or a native .claude/workflows/*.js orchestration script (agent/parallel/pipeline fan-out)
Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool
Side-by-side comparison of ruflo vs HAL vs other GAIA harnesses — capability gaps, design decisions, and improvement roadmap
Diagnose why a GAIA question failed — extract trace, classify failure mode, and propose a fix
Walk through a complete GAIA benchmark→submit flow — from key resolution through HAL-compatible package generation
| name | iot-firmware |
| description | Orchestrate firmware rollouts with canary deployment and anomaly-gated advancement |
| allowed-tools | Bash(npx *) mcp__claude-flow__memory_store mcp__claude-flow__memory_search Read |
| argument-hint | <deploy|advance|rollback|status|list> [options] |
Manage firmware rollouts across device fleets.
deploy: npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware deploy FLEET_ID --version VERSION
advance: npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware advance ROLLOUT_ID
rollback: npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware rollback ROLLOUT_ID
status: npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware status ROLLOUT_ID
list: npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware list
Rollout stages: pending → canary → rolling → complete (or rolled-back)
