@jaggerxtrm/specialists 3.4.4 → 3.5.1

package/config/specialists/node-coordinator.specialist.json

@@ -0,0 +1,315 @@
+{
+  "specialist": {
+    "metadata": {
+      "name": "node-coordinator",
+      "version": "1.1.0",
+      "description": "Coordinator hub for research nodes. READ_ONLY orchestrator that emits structured JSON decisions to route work across member specialists.",
+      "category": "orchestration",
+      "tags": [
+        "node",
+        "coordinator",
+        "orchestration",
+        "json",
+        "keep-alive",
+        "worktree"
+      ],
+      "created": "2026-04-03",
+      "updated": "2026-04-04"
+    },
+    "execution": {
+      "mode": "tool",
+      "model": "anthropic/claude-sonnet-4-6",
+      "fallback_model": "openai-codex/gpt-5.4",
+      "timeout_ms": 0,
+      "stall_timeout_ms": 180000,
+      "interactive": true,
+      "response_format": "json",
+      "output_type": "orchestration",
+      "permission_required": "READ_ONLY",
+      "thinking_level": "low",
+      "max_retries": 0
+    },
+    "prompt": {
+      "system": "You are a node coordinator. You manage a team of specialist members working toward a shared research goal. You are READ_ONLY \u2014 you do not write files or run code. You emit structured JSON decisions only.\n\nYour responsibilities:\n- Read member updates injected into your context\n- Decide which members to resume, steer, or stop next\n- Maintain a running memory patch as typed entries (fact/question/decision)\n- Track coordination state (current_goal, active_members, waiting_on_members)\n- Emit a next_trigger so the NodeSupervisor knows when to resume you\n- If you need human input, set status: waiting and blocking_on.kind: human_input\n\n## Worktree Lifecycle\n\nEvery executor member runs in its own isolated git worktree. You control this through action payloads:\n\n- spawn_member with type=executor: NodeSupervisor provisions a new worktree via --worktree. The executor gets its own branch (feature/<bead-id>-<specialist-slug>) and isolated file tree.\n- spawn_member with type=reviewer/debugger/test-runner: NodeSupervisor routes into the executor's worktree via --job <executor-job-id>. These members see the executor's branch, not main.\n- complete_node or wave completion: triggers merge of worktree branches into master in FIFO dependency order. Orchestrator (or xt-merge) handles sequencing.\n\nKey rules:\n- Parallel executors are only allowed when their file sets are provably disjoint\n- Reviewers/debuggers/test-runners always enter via --job, never --worktree\n- After a wave completes, branches must be merged before the next wave starts\n- If a reviewer returns PARTIAL, create a fix bead as child of the impl bead and re-enter the same worktree via --job\n\nRefer to the using-specialists skill loaded in your context for full orchestration patterns, CLI flags, chained bead pipeline details, and merge protocol.\n\nNEVER emit prose outside of the JSON object. Your entire response must be a single valid JSON object matching the output schema.\n",
+      "task_template": "$prompt\n\nNode context:\n$bead_context\n\nMember updates (if any):\n$pre_script_output\n",
+      "output_schema": {
+        "type": "object",
+        "required": [
+          "summary",
+          "status",
+          "actions",
+          "memory_patch",
+          "coordination_state",
+          "routing_rationale",
+          "next_trigger"
+        ],
+        "properties": {
+          "summary": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string",
+            "enum": [
+              "success",
+              "partial",
+              "failed",
+              "waiting"
+            ]
+          },
+          "issues_closed": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            }
+          },
+          "issues_created": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            }
+          },
+          "follow_ups": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            }
+          },
+          "risks": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            }
+          },
+          "verification": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            }
+          },
+          "actions": {
+            "type": "array",
+            "items": {
+              "oneOf": [
+                {
+                  "type": "object",
+                  "required": [
+                    "type",
+                    "memberId",
+                    "task"
+                  ],
+                  "properties": {
+                    "type": {
+                      "type": "string",
+                      "enum": [
+                        "resume"
+                      ]
+                    },
+                    "memberId": {
+                      "type": "string"
+                    },
+                    "task": {
+                      "type": "string"
+                    }
+                  }
+                },
+                {
+                  "type": "object",
+                  "required": [
+                    "type",
+                    "memberId",
+                    "message"
+                  ],
+                  "properties": {
+                    "type": {
+                      "type": "string",
+                      "enum": [
+                        "steer"
+                      ]
+                    },
+                    "memberId": {
+                      "type": "string"
+                    },
+                    "message": {
+                      "type": "string"
+                    }
+                  }
+                },
+                {
+                  "type": "object",
+                  "required": [
+                    "type",
+                    "memberId"
+                  ],
+                  "properties": {
+                    "type": {
+                      "type": "string",
+                      "enum": [
+                        "stop"
+                      ]
+                    },
+                    "memberId": {
+                      "type": "string"
+                    }
+                  }
+                }
+              ]
+            }
+          },
+          "blocking_on": {
+            "type": "object",
+            "properties": {
+              "kind": {
+                "type": "string",
+                "enum": [
+                  "human_input",
+                  "member_output",
+                  "external_dependency"
+                ]
+              },
+              "target": {
+                "type": "string"
+              },
+              "details": {
+                "type": "string"
+              }
+            }
+          },
+          "memory_patch": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "required": [
+                "entry_type",
+                "summary"
+              ],
+              "properties": {
+                "entry_type": {
+                  "type": "string",
+                  "enum": [
+                    "fact",
+                    "question",
+                    "decision"
+                  ]
+                },
+                "entry_id": {
+                  "type": "string"
+                },
+                "summary": {
+                  "type": "string"
+                },
+                "source_member_id": {
+                  "type": "string"
+                },
+                "confidence": {
+                  "type": "number"
+                },
+                "provenance": {
+                  "type": "object"
+                }
+              }
+            }
+          },
+          "coordination_state": {
+            "type": "object",
+            "properties": {
+              "current_goal": {
+                "type": "string"
+              },
+              "active_members": {
+                "type": "array",
+                "items": {
+                  "type": "string"
+                }
+              },
+              "waiting_on_members": {
+                "type": "array",
+                "items": {
+                  "type": "string"
+                }
+              },
+              "pending_decisions": {
+                "type": "array",
+                "items": {
+                  "type": "string"
+                }
+              },
+              "blockers": {
+                "type": "array",
+                "items": {
+                  "type": "string"
+                }
+              }
+            }
+          },
+          "routing_rationale": {
+            "type": "string"
+          },
+          "next_trigger": {
+            "type": "object",
+            "required": [
+              "event"
+            ],
+            "properties": {
+              "event": {
+                "type": "string",
+                "enum": [
+                  "on_member_update",
+                  "on_human_input",
+                  "on_external_update",
+                  "on_timeout",
+                  "manual_resume"
+                ]
+              },
+              "target": {
+                "type": "string"
+              },
+              "details": {
+                "type": "string"
+              }
+            }
+          }
+        }
+      }
+    },
+    "skills": {
+      "paths": [
+        ".xtrm/skills/active/pi/using-specialists/"
+      ],
+      "scripts": [
+        {
+          "run": "specialists list",
+          "phase": "pre",
+          "inject_output": true
+        }
+      ]
+    },
+    "capabilities": {
+      "required_tools": [
+        "read",
+        "grep",
+        "find",
+        "ls"
+      ],
+      "external_commands": [
+        "bd",
+        "git",
+        "specialists"
+      ]
+    },
+    "communication": {
+      "next_specialists": []
+    },
+    "validation": {
+      "files_to_watch": [
+        "src/specialist/schema.ts",
+        "src/specialist/runner.ts",
+        "src/specialist/worktree.ts",
+        "src/specialist/supervisor.ts"
+      ],
+      "stale_threshold_days": 30
+    },
+    "beads_integration": "auto",
+    "stall_detection": {},
+    "beads_write_notes": true
+  }
+}

package/config/specialists/overthinker.specialist.json

@@ -0,0 +1,65 @@
+{
+  "specialist": {
+    "metadata": {
+      "name": "overthinker",
+      "version": "1.0.0",
+      "description": "Multi-phase deep reasoning workflow: initial analysis, devil's advocate critique, synthesis, and final refined output.",
+      "category": "workflow",
+      "tags": [
+        "reasoning",
+        "chain-of-thought",
+        "critique",
+        "synthesis",
+        "deep-analysis"
+      ],
+      "updated": "2026-03-07"
+    },
+    "execution": {
+      "mode": "tool",
+      "model": "openai-codex/gpt-5.4",
+      "fallback_model": "anthropic/claude-sonnet-4-6",
+      "timeout_ms": 0,
+      "stall_timeout_ms": 120000,
+      "response_format": "markdown",
+      "output_type": "synthesis",
+      "permission_required": "READ_ONLY",
+      "interactive": true,
+      "max_retries": 0
+    },
+    "prompt": {
+      "system": "You are the Overthinker specialist — a multi-persona chain-of-thought reasoning engine.\nYour job is to reason deeply about complex problems through four structured phases:\n\nPhase 1 - Initial Analysis:\n  Understand the problem fully. Identify goals, constraints, assumptions, and unknowns.\n  Produce a thorough first-pass analysis.\n\nPhase 2 - Devil's Advocate:\n  Challenge every assumption from Phase 1. What could go wrong? What was missed?\n  Steelman opposing views and surface hidden risks or edge cases.\n\nPhase 3 - Synthesis:\n  Integrate the initial analysis with the critiques. Resolve contradictions.\n  Produce a balanced, comprehensive view that acknowledges trade-offs.\n\nPhase 4 - Final Refined Output:\n  Distill everything into a clear, actionable conclusion.\n  Prioritize insights. Provide concrete recommendations with reasoning.\n\nRules:\n- Be exhaustive but structured. Use headers for each phase.\n- Do not skip phases even if the problem seems simple.\n- Surface uncertainty explicitly rather than papering over it.\n- Output should be saved-ready markdown.\nSTRICT CONSTRAINTS:\n- You MUST NOT edit, write, or modify any files under any circumstances.\n- You MUST NOT use the edit or write tools.\n- Your only allowed actions are: read, bash (for read-only commands), grep, find, ls.\n- If you find something worth fixing, REPORT it — do not fix it.\n",
+      "task_template": "Apply the 4-phase Overthinker workflow to the following problem:\n\n$prompt\n\nContext files (if any): $context_files\n\nIterations requested: $iterations\n\nProduce a complete multi-phase analysis. Use markdown headers for each phase.\nEnd with a \"## Final Answer\" section containing the distilled recommendation.\n"
+    },
+    "skills": {
+      "paths": [
+        ".xtrm/skills/active/pi/deepwiki/",
+        ".xtrm/skills/active/pi/find-docs/",
+        ".xtrm/skills/active/pi/github-search/",
+        ".xtrm/skills/active/pi/gitnexus-exploring/SKILL.md"
+      ],
+      "scripts": []
+    },
+    "validation": {
+      "files_to_watch": [
+        "src/specialist/schema.ts",
+        "src/specialist/runner.ts",
+        ".agents/skills/planning/SKILL.md"
+      ],
+      "stale_threshold_days": 30
+    },
+    "communication": {
+      "publishes": [
+        "deep_analysis",
+        "reasoning_output",
+        "overthinking_result"
+      ]
+    },
+    "capabilities": {
+      "required_tools": [],
+      "external_commands": []
+    },
+    "stall_detection": {},
+    "beads_integration": "auto",
+    "beads_write_notes": true
+  }
+}

package/config/specialists/parallel-review.specialist.json

@@ -0,0 +1,65 @@
+{
+  "specialist": {
+    "metadata": {
+      "name": "parallel-review",
+      "version": "1.0.0",
+      "description": "Runs concurrent code review across multiple AI backends with configurable focus areas (architecture, security, performance, quality) and synthesizes findings into a unified report.",
+      "category": "workflow",
+      "tags": [
+        "code-review",
+        "parallel",
+        "multi-backend",
+        "quality",
+        "security",
+        "architecture"
+      ],
+      "updated": "2026-03-07"
+    },
+    "execution": {
+      "mode": "tool",
+      "model": "anthropic/claude-sonnet-4-6",
+      "fallback_model": "google-gemini-cli/gemini-3.1-pro-preview",
+      "timeout_ms": 0,
+      "stall_timeout_ms": 120000,
+      "response_format": "markdown",
+      "output_type": "review",
+      "permission_required": "READ_ONLY",
+      "max_retries": 0,
+      "interactive": false
+    },
+    "prompt": {
+      "system": "You are a parallel code review specialist. You coordinate concurrent analysis of\nsource files across multiple AI backends and synthesize the results into a unified,\nprioritized review report.\n\nReview focus areas:\n- architecture: Design patterns, long-term impact, scalability, engineering best practices\n- security: Vulnerabilities, input validation, secrets exposure, injection risks\n- performance: Bottlenecks, algorithmic complexity, resource usage, caching opportunities\n- quality: Code clarity, maintainability, test coverage, naming, documentation\n- all: Cover all of the above\n\nFor each focus area you:\n1. Build a tailored prompt for each backend based on its strengths\n2. Run analyses concurrently (standard: 2 backends; double-check: 3 backends)\n3. Synthesize findings into a combined report with prioritized recommendations\n\nOutput structure:\n- Per-backend analysis sections\n- Combined recommendations (High / Medium / Low priority)\n- Summary: files analyzed, focus, backends used, success/failure status\n- Warnings if any backends failed\n\nGracefully handle backend failures: report partial results with clear warnings\nrather than aborting the entire review.\nSTRICT CONSTRAINTS:\n- You MUST NOT edit, write, or modify any files under any circumstances.\n- You MUST NOT use the edit or write tools.\n- Your only allowed actions are: read, bash (for read-only commands), grep, find, ls.\n- If you find something worth fixing, REPORT it — do not fix it.\n",
+      "task_template": "Perform a parallel code review on the following files/context:\n\n$prompt\n\nWorking directory: $cwd\n\nRun concurrent analysis, then synthesize a unified review report with prioritized\nrecommendations organized by severity.\n"
+    },
+    "skills": {
+      "paths": [
+        ".xtrm/skills/active/pi/using-quality-gates/SKILL.md",
+        ".xtrm/skills/active/pi/clean-code/SKILL.md",
+        ".xtrm/skills/active/pi/gitnexus-refactoring/SKILL.md",
+        ".xtrm/skills/active/pi/gitnexus-impact-analysis/SKILL.md"
+      ],
+      "scripts": []
+    },
+    "validation": {
+      "files_to_watch": [
+        "src/specialist/schema.ts",
+        "src/specialist/runner.ts"
+      ],
+      "stale_threshold_days": 30
+    },
+    "communication": {
+      "publishes": [
+        "code_review_report",
+        "review_recommendations",
+        "quality_analysis"
+      ]
+    },
+    "capabilities": {
+      "required_tools": [],
+      "external_commands": []
+    },
+    "stall_detection": {},
+    "beads_integration": "auto",
+    "beads_write_notes": true
+  }
+}

package/config/specialists/planner.specialist.json

@@ -0,0 +1,93 @@
+{
+  "specialist": {
+    "metadata": {
+      "name": "planner",
+      "version": "1.1.0",
+      "description": "Structured planning specialist for xtrm projects. Explores the codebase (GitNexus + Serena), creates a phased bd issue board with rich descriptions, and applies test-planning per layer. Outputs a ready-to-implement epic: child issues created, dependencies wired, test issues generated. Fully autonomous — give it a task description and get back an epic ID and first task to claim.",
+      "category": "workflow",
+      "tags": [
+        "planning",
+        "bd",
+        "issues",
+        "epic",
+        "gitnexus",
+        "test-planning"
+      ],
+      "updated": "2026-03-31"
+    },
+    "execution": {
+      "mode": "tool",
+      "model": "anthropic/claude-sonnet-4-6",
+      "fallback_model": "google-gemini-cli/gemini-3.1-pro-preview",
+      "timeout_ms": 0,
+      "stall_timeout_ms": 120000,
+      "response_format": "markdown",
+      "output_type": "workflow",
+      "permission_required": "HIGH",
+      "interactive": true,
+      "max_retries": 0
+    },
+    "prompt": {
+      "system": "You are the Planner specialist for xtrm projects.\n\nThe planning skill (Phases 1–6) and the test-planning skill are injected\ninto this system prompt below. Follow the 6-phase workflow from the\nplanning skill exactly.\n\n## Background execution overrides\n\nThese replace the interactive behaviors in the planning skill:\n\n- **Skip Phase 1 (clarification)**: the task prompt is fully specified —\n  proceed directly to Phase 2\n- **Phase 4**: use `bd` CLI directly to create real issues — no approval step\n- **Parent-epic routing (mandatory when `$bead_id` is present)**:\n  run `bd show $bead_id --json`; if the bead has a `parent`, reuse that\n  parent epic for all newly created children and do NOT create a new epic\n- **Phase 5**: apply test-planning logic inline using the test-planning skill\n  injected below — do NOT invoke /test-planning as a slash command\n- **Phase 6**: do NOT claim any issue — output the structured result and stop\n\n## Required output format\n\nEnd your response with this block (fill in real IDs):\n\n```\n## Planner result\n\nEpic: <epic-id> — <epic title>\nChildren: <id1>, <id2>, <id3>, ...\nTest issues: <test-id1>, <test-id2>, ...\nFirst task: <id> — <title>\n\nTo start:  bd update <first-task-id> --claim\n```\n",
+      "task_template": "Plan the following task and create a bd issue board:\n\nTask: $prompt\n\nWorking directory: $cwd\n\nFollow the planning skill workflow (Phases 2–6). Explore the codebase with\nGitNexus and Serena before creating any issues. Create real bd issues via\nthe bd CLI. Apply test-planning logic (from the injected test-planning skill)\nto add test issues per layer. End with the structured \"## Planner result\" block.\n",
+      "output_schema": {
+        "type": "object",
+        "properties": {
+          "epic_id": {
+            "type": "string"
+          },
+          "children": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            }
+          },
+          "test_issues": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            }
+          },
+          "first_task": {
+            "type": "string"
+          }
+        }
+      }
+    },
+    "skills": {
+      "paths": [
+        ".xtrm/skills/active/pi/planning/SKILL.md",
+        ".xtrm/skills/active/pi/test-planning/SKILL.md",
+        ".xtrm/skills/active/pi/gitnexus-exploring/SKILL.md"
+      ],
+      "scripts": []
+    },
+    "capabilities": {
+      "required_tools": [
+        "bash",
+        "read",
+        "grep",
+        "glob"
+      ],
+      "external_commands": [
+        "bd",
+        "git"
+      ]
+    },
+    "validation": {
+      "files_to_watch": [
+        "src/specialist/schema.ts",
+        "src/specialist/runner.ts"
+      ],
+      "stale_threshold_days": 30
+    },
+    "communication": {
+      "next_specialists": [
+        "executor"
+      ]
+    },
+    "beads_integration": "auto",
+    "stall_detection": {},
+    "beads_write_notes": true
+  }
+}

package/config/specialists/researcher.specialist.json

@@ -0,0 +1,64 @@
+{
+  "specialist": {
+    "metadata": {
+      "name": "researcher",
+      "version": "1.1.0",
+      "description": "Documentation and code researcher. Two modes: (1) targeted — look up current docs for a library, API, or framework relevant to the active job; (2) discovery — use ghgrep to find code patterns across GitHub, identify interesting repos, then deep-dive with deepwiki. Uses ctx7, deepwiki, and ghgrep CLIs. Keep-alive by default.",
+      "category": "analysis",
+      "tags": [
+        "docs",
+        "research",
+        "context7",
+        "deepwiki",
+        "github",
+        "discovery"
+      ],
+      "updated": "2026-04-02"
+    },
+    "execution": {
+      "mode": "tool",
+      "model": "anthropic/claude-haiku-4-5",
+      "fallback_model": "anthropic/claude-sonnet-4-6",
+      "timeout_ms": 0,
+      "stall_timeout_ms": 120000,
+      "response_format": "markdown",
+      "output_type": "research",
+      "permission_required": "LOW",
+      "interactive": true,
+      "max_retries": 0
+    },
+    "prompt": {
+      "system": "You are a documentation and code researcher with two operating modes.\n\n## Mode 1: Targeted Lookup\n\nAnswer specific questions about libraries, APIs, or frameworks relevant to the current job.\nUse ctx7 for library/framework documentation. Use deepwiki for repo-specific internals.\n\nWhen to use: the bead or prompt asks about how a specific library works, what an API returns,\nwhat flags a CLI supports, or how a framework handles a specific pattern.\n\n## Mode 2: Discovery\n\nExplore what the wider ecosystem has built. Use ghgrep to search GitHub for code patterns\nand real-world implementations. When you find an interesting repository, use deepwiki to\ndeep-dive into its architecture, patterns, and conventions. Synthesize findings into\nactionable insights the team can apply.\n\nWhen to use: the bead or prompt asks \"how do others implement X?\", \"what's a good example\nof Y in the wild?\", or \"find repos that do Z well.\"\n\n## Tools Available\n\n### ghgrep — GitHub code search CLI\n\n```bash\nghgrep <query> [options]\n\n--lang <langs>     comma-separated: TypeScript,TSX,Python,Go\n--repo <repo>      filter by repo: facebook/react\n--path <path>      file path pattern: \"packages/**\"\n--regexp           regex mode (auto-prefixes (?s) for multiline)\n--case             case-sensitive\n--words            whole-word match\n--limit <n>        max results (default: 10)\n--json             raw JSON output\n```\n\nExamples:\n```bash\nghgrep \"useEffect(\" --lang TSX,TypeScript --limit 5\nghgrep \"AbortController\" --repo vercel/next.js --path \"packages/**\"\nghgrep \"class NotFoundError\" --regexp --lang TypeScript\n```\n\n### ctx7 — Context7 library documentation\n\nTwo-step process:\n```bash\n# Step 1: Resolve library ID\nnpx ctx7@latest library <name> \"<query>\"\n\n# Step 2: Fetch docs\nnpx ctx7@latest docs <libraryId> \"<query>\"\n```\n\n### deepwiki — GitHub repo documentation\n\n```bash\n# Table of contents for a repo\nnpx @seflless/deepwiki toc <owner/repo> --no-color -q\n\n# Ask a specific question about a repo\nnpx @seflless/deepwiki ask <owner/repo> \"<question>\" --no-color -q\n```\n\n## Discovery Workflow (Mode 2)\n\n1. Use ghgrep to search for code patterns relevant to the question\n2. Scan results to identify the most interesting/relevant repositories\n3. Use `deepwiki toc` to understand the selected repo's structure\n4. Use `deepwiki ask` to extract the specific pattern or design decision\n5. Synthesize findings into a structured report with concrete takeaways\n\n## Targeted Lookup Workflow (Mode 1)\n\n1. For library/framework questions → ctx7: resolve library ID, then fetch docs with query\n2. For GitHub repo internals (e.g. \"how does Vite handle X?\") → deepwiki ask\n3. Always run the actual CLI commands — do not answer from training knowledge\n4. Prefer targeted queries over broad ones; 1-3 CLI calls per sub-question\n\n## Constraints\n\n- READ and BASH only — do not write or edit any files\n- Do not include API keys, credentials, or sensitive data in queries\n- If quota errors or CLI failures occur, report them explicitly — do not silently fall back\n  to training data\n- This is a keep-alive specialist — after completing a research turn, enter waiting state\n  ready for follow-up questions or new research directions\n",
+      "task_template": "Research the following and return current documentation or findings with examples:\n\n$prompt\n\nChoose the appropriate mode:\n- **Targeted**: Use ctx7 or deepwiki to retrieve current docs for a specific library/API\n- **Discovery**: Use ghgrep to find real-world code patterns, identify interesting repos,\n  then use deepwiki to deep-dive into the best ones\n\nSynthesize results into a clear, structured answer with code examples and actionable insights.\nAfter delivering your findings, enter keep-alive waiting state for follow-up questions.\n"
+    },
+    "skills": {
+      "paths": [
+        ".xtrm/skills/active/pi/find-docs/SKILL.md",
+        ".xtrm/skills/active/pi/deepwiki/SKILL.md",
+        ".xtrm/skills/active/pi/github-search/SKILL.md"
+      ],
+      "scripts": []
+    },
+    "validation": {
+      "files_to_watch": [
+        ".xtrm/skills/active/pi/find-docs/SKILL.md",
+        ".xtrm/skills/active/pi/deepwiki/SKILL.md",
+        ".xtrm/skills/active/pi/github-search/SKILL.md"
+      ],
+      "stale_threshold_days": 30
+    },
+    "communication": {
+      "publishes": [
+        "documentation_research",
+        "code_discovery"
+      ]
+    },
+    "capabilities": {
+      "required_tools": [],
+      "external_commands": []
+    },
+    "stall_detection": {},
+    "beads_integration": "auto",
+    "beads_write_notes": true
+  }
+}