tt

# /tt — trigger-tree Execute the subcommand in `$1` (option/text in `$2` and beyond; `$ARGUMENTS` holds everything). **Output discipline — the most important rule:** work silently. No plan up front, no intermediate status lines, no explanation of what you are about to do or just did. Execute the steps and show only the end result in the format specified per subcommand below. Report an error in exactly one line. **Terminology — maturity model:** a file with zero reads is **untouched**, never "dead". Only when the stats JSON reports `maturity: "mature"` may untouched files be presented as **dead-path candidates**. During `cold-start` and `warming` the measurement is simply too young to judge. Scripts live in `${CLAUDE_SKILL_DIR}/scripts/`. Project data lives in `${CLAUDE_PROJECT_DIR}/.trigger-tree/`. ## `$1` = "help" or empty Show exactly this, nothing above or below it: > **🌳 trigger-tree** — measures which documentation your agents actually use > > | Command | Does | > |---------|------| > | `/tt status` | Snapshot: current heat, lifetime reads, untouched paths | > | `/tt watch` | Live dashboard; heat bars, injected context, privacy settings, and focus/hot/cold/A–Z/Z–A sorting | > | `/tt watch demo` | Dashboard with synthetic events (writes nothing) | > | `/tt watch replay` | Dashboard replaying the real history, accelerated | > | `/tt insights` | Analysis report: heat/cold map, untouched paths, hunting, trend + HTML | > | `/tt suggestions` | Max 5 prioritized, concre...