Debug
Turns a dependency graph into debug playbooks
Produces a debug playbook, incident template, tracing rules, and a root-cause checklist derived from the repo's actual dependency hotspots rather than generic advice. Free tier.
What it does
Debug documentation is usually written once, at the wrong level of abstraction, and never opened again. This derives it from where the dependency graph says failures will actually cluster.
Output is four files: a playbook, an incident template, tracing rules, and a root-cause checklist.
What it emits
4 artifacts, every run. This list is generated from Iliad's program manifest, which its CI checks against the generators themselves — it is what the program actually writes, not a description of it.
debug-playbook.mdincident-template.mdtracing-rules.mdroot-cause-checklist.md
Listing a tool here
Listing is free and permanent, same as the app directory. If your tool can be called by an agent, it belongs here whether it is an MCP server, a REST endpoint, or a single generator buried in a larger toolbox.