Menu
Use the Milknado MCP tools to pick and execute the next ready node from the Mikado graph, apply file changes, and run quality gates.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Staff Engineer code review orchestrator. Runs nine orthogonal LLM dimensions over a diff and emits a stake-weighted report plus hash-anchored sidecar JSON.
Finish what /age started. Loads both sidecars (fixes + suggestions), renders a unified stake table, gates on user approval, routes each approved item to the right handler (/cleanup or a cook sub-agent), then re-ages the touched paths up to a hard 3-turn cap.
Iterative thinking amplifier for fuzzy ideas. Routes input to the right starting mode (Explore, Ground, Shape, Sketch, Grill, Diagnose), runs Validate Cycles to anchor claims, locks down interfaces in pseudocode, and only curdles a spec (and optional issues) after a two-key handshake plus a coherence self-check.
Scan a codebase for custom code that duplicates what open-source libraries already do, then recommend which libraries to adopt. Detects hand-rolled utility functions, custom retry logic, manual validation, DIY date handling, home-grown argument parsers, and other reinvented wheels. Cross-checks against installed dependencies and open specs. Returns scored migration recommendations with effort estimates. Use when the user mentions reinventing the wheel, asks if there is a library for something they built, wants a build-vs-buy audit, asks "should we just use lodash for this", or wants to find dependency opportunities.
AST-aware code search using tilth MCP. Finds definitions first, then usages. Use tree-sitter structural matching instead of blind text grep. Understand dependencies and call graphs. Use when: finding where symbols are defined, tracing call chains, understanding code structure, finding all callers of a function. Do NOT use for reading files — use cheez-read. Do NOT use for editing — use cheez-write. Examples: "find where handleAuth is defined", "what calls validateToken?", "trace the ServeHTTP, HandlersChain, Next functions", "find all implementations of the UserService interface".
Mechanical apply of /age's hash-anchored sidecar fixes via tilth_edit. The cleanup-wolf sub-agent is the only LLM in the path, fired per anchor mismatch.
| name | milknado-execute |
| description | Use the Milknado MCP tools to pick and execute the next ready node from the Mikado graph, apply file changes, and run quality gates. |
| license | MIT |
| compatibility | Requires the milknado MCP server to be configured and running. |
| allowed-tools | ["read","write","bash","mcp__milknado__milknado_graph_summary","mcp__milknado__milknado_add_node"] |
Use this skill to work through a Milknado graph one node at a time. Each invocation picks the next ready node, applies the required changes, validates them with quality gates, and reports the outcome.
milknado-plan has populated the graph with pending work nodes.milknado_graph_summary to find pending nodes
whose prerequisites are all done. (Eligibility is computed by the engine;
there is no stored ready status — the summary only shows the persisted
pending/running/done/blocked/failed values.)pending node. Read its description carefully — it is the primary context.edit_kind in the node description
(add, modify, delete, or rename). Keep changes strictly scoped.milknado_add_node to record it as a new
prerequisite (with parent_id set to the current node), then leave the
current node open for re-dispatch.| Tool | Purpose |
|---|---|
milknado_graph_summary | Read the graph to find pending nodes whose prerequisites are done. |
milknado_add_node | Record a newly discovered blocker as a prerequisite node. |