← ClaudeAtlas

tendril-debug-planlisted

Debug a Tendril plan by analyzing its execution logs, session JSONL, verification results, and checking infrastructure. Produces actionable bugfix and improvement recommendations. Use when the user wants to investigate why a plan failed, behaved unexpectedly, or to audit plan execution quality.
Ivy-Interactive/Ivy-Tendril · ★ 150 · Code & Development · score 70
Install: claude install-skill Ivy-Interactive/Ivy-Tendril
# tendril-debug-plan Debug and analyze Tendril plan executions end-to-end — from plan creation through checking/verification — and produce a set of concrete bugfix and improvement recommendations. ## Invocation ``` /tendril-debug-plan <planid> <note> ``` * **planid** — 5-digit Tendril plan ID (e.g., `03451`) * **note** — free-text context about what to look for (e.g., "verification passed but shouldn't have", "took forever", "got stuck in Building state") ## What This Skill Does 1. Gathers all artifacts for a plan: `plan.yaml`, revisions, logs, costs, verification reports, session JSONL 2. Analyzes the execution timeline, token usage, tool call patterns, and error loops 3. Cross-references findings with Tendril source code and promptware instructions 4. Produces a structured recommendations report with concrete fixes ## Execution Steps ### Phase 1 — Gather Plan Artifacts Resolve paths from environment: * `TENDRIL_HOME` — base config/data directory * `TENDRIL_PLANS` — plans directory (defaults to `$TENDRIL_HOME/Plans`) * `REPOS_HOME` — for locating Tendril source code Read these files from the plan folder (`$TENDRIL_PLANS/{planid}-*/`): | File | Purpose | | ------------------- | ---------------------------------------------------------------------------------------------------------- | | `plan.yaml` | Plan metadata: state, repos, commits, PRs, v