Search the AgentSkills specification. Use when creating, validating, structuring skills, or understanding the SKILL.md format.

Installe les outils CLI prérequis (gh, glab, jq), guide l'authentification GitHub/GitLab, installe uvx et configure le serveur MCP mcp-atlassian pour Jira dans OpenCode. Idempotent : relancer le skill est sans danger. Déclenché quand l'utilisateur dit « setup », « install prerequisites » ou « configurer jira ».

Facilitate a live problem discovery session with a client or stakeholders. Designed for use during a meeting or call — helps the PM guide structured exploration of a problem space before any requirements are written. Produces a discovery summary in Google Drive that seeds capture-requirements. Works in Claude Cowork and Claude Code.

Facilitate a live problem discovery session with a client or stakeholders. Designed for use during a meeting or call — helps the PM guide structured exploration of a problem space before any requirements are written. Produces a discovery summary in Confluence that seeds capture-requirements. Works in Claude Cowork and Claude Code.

Generate an audience-appropriate stakeholder update by pulling live Jira sprint data, GitHub PR/pipeline status, and Confluence artifacts. Produces human-facing communication from AI-native project artifacts — status reports, client updates, executive summaries, engineering updates. Works in Claude Cowork and Claude Code.

Investigate distributed traces and spans in OpenSearch. Use this skill when the user wants to analyze traces, investigate slow spans, find error spans, track agent invocations, measure token usage, reconstruct trace trees, query service maps, or debug distributed systems through trace data. Activate even if the user says traceId, spanId, OpenTelemetry, OTel, distributed tracing, latency, span duration, service map, or trace investigation without mentioning OpenSearch.

Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.

Enforces workflow discipline across ALL projects. Ensures Claude checks for specialized agents before responding, announces skill/agent usage, and creates TodoWrite todos for multi-step tasks. Triggers: automatic on all sessions, use the right agent, follow workflow.

Guidance for the bundled Zoom Whiteboard MCP connector. Use for Whiteboard MCP auth, endpoints, ID mapping, and tool workflows such as list_whiteboards and get_a_whiteboard. Prefer this skill when the request is specifically about Whiteboard MCP rather than general Zoom MCP.

Audits any AI instruction set for over-prompting using the core test: would a smarter model make this rule unnecessary? Applies Five Questions to every rule — Does Claude already do this? Contradiction? Redundant? One-off fix? Vague? — then classifies each as CUT / RESOLVE / MERGE / EVALUATE / SHARPEN / MOVE / KEEP. Two workflows: Audit (full system — reads all force-loaded files from settings.json, reports token savings estimate) and QuickCheck (single file, fast keep/cut/sharpen verdict). Outputs categorized report with estimated line and token savings. Core principle: less scaffolding = better output — every unnecessary rule competes for attention and degrades the rules that matter. Anti-fragile rules to KEEP: verification harnesses, ISC, data pipelines, specific DO/DON'T examples, tool preferences, routing rules. Fragile rules to CUT: CoT orchestrators, format parsers, retry cascades, numeric personality scales, abstract value statements. Requires loadAtStartup and postCompactRestore.fullFiles to stay in sync in settings.json — removing a file from one requires checking the other. NOT FOR general code simplification or refactoring (use simplify skill). NOT FOR attacking logical or strategic flaws in ideas (use RedTeam for that). USE WHEN BPE, bitter pill, audit setup, over-prompting, trim instructions, audit rules, dead weight, redundant rules, simplify setup, instruction audit, prompt hygiene, check these rules, clean up CLAUDE.md.

Generate Ableton Live project files (.als) for testing. Use this skill when the user wants to create test .als files with specific configurations (tempo, tracks, clips, devices, etc.). The skill parses user prompts, applies changes via Ableton MCP tools, saves the project using ableton-save skill, and returns the saved file path.

Use for live browser automation via the agent-browser CLI — open URLs, snapshot pages, click/fill/screenshot, inspect elements, scrape or read web pages. Ref-based workflow for AI agents. Not for writing Playwright test files (use playwright or web-test).

Create or update root and nested AGENTS.md files that document scoped conventions, monorepo module maps, cross-domain workflows, and (optionally) per-module feature maps (feature -> paths, entrypoints, tests, docs). Use when the user asks for AGENTS.md, nested agent instructions, or a module/feature map.

Track and analyze content performance across Instagram, YouTube, LinkedIn, Twitter/X, and Reddit using anysite MCP server. Measure engagement metrics, analyze post effectiveness, benchmark content strategy, identify top-performing content, and optimize posting strategies. Use when users need to measure content ROI, optimize social strategy, identify viral content patterns, or analyze content engagement across platforms.

Execute architectural refactoring from an assessment document with deterministic, chunked operations and aggressive verification at every step. Use when you have an architectural assessment, clean architecture review, refactoring recommendations, or seam-ripper output and need to actually perform the refactoring safely. Also use when asked to "refactor based on this assessment", "execute these architectural recommendations", "fix architectural drift", "refactor in chunks", or any request to systematically restructure a codebase according to a plan. Designed specifically to prevent the kind of agent drift that causes architectural problems in the first place.

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.

Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session. Use this skill whenever the user asks to orchestrate agents, create or steer worker sessions, run a workflow-like effort, fan out audits/research/migrations, coordinate parallel implementation streams, monitor other project sessions, or compare this control-session pattern to Claude Code dynamic workflows. This skill is especially relevant when the current session can spawn persistent project sessions and those sessions can spawn their own subagents, creating a two-level orchestration hierarchy.

Use when the user wants Codex to delegate a bounded task to Cursor CLI / Cursor Agent as an external terminal subagent, especially with model composer-2.5, headless runs, secondary code review, or small implementation shards.

Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when onboarding to a project with existing agents, after adding new agents to a fleet, or when an orchestrator consistently selects the wrong agent.

Audit Claude Code hooks defined in settings.json files for validity, performance safety, and correctness. Resolves each command against the filesystem, checks exit-code strategy for blocking hooks, flags missing timeouts, and reviews interactive vs async patterns. Use when setting up hooks for the first time, debugging a hook that never fires or hangs the agent, or doing a periodic hooks hygiene pass.

Multi-AI requirements scoping using Codex and Gemini CLIs (Double Diamond Define phase)

One-click installer for gate-cli and gate-skills on Cursor, Claude Code, Codex, or OpenClaw/mcporter. Triggers on 'install gate-cli', 'Gate skills', 'Gate Verify', 'tx check-in', 'setup Gate Cursor', 'Gate Claude Code', 'Gate Codex', 'OpenClaw Gate', 'mcporter Gate'.

Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Comprehensive quick-reference for authoring Claude Code hooks. Use when creating new hooks for settings, plugins, or skill/agent frontmatter. Covers all 26 event types, four handler types (command/http/prompt/agent), JSON input/output formats, matcher semantics, decision control, exit codes, async hooks, environment variables, and troubleshooting patterns. Trigger when user says "create a hook", "add a hook", "hook reference", "what hooks are available", "how do hooks work", "hook schema", "hook events", or is authoring hooks.json for a plugin or settings file.

Laravel v12 - The PHP Framework For Web Artisans (project, gitignored)

Maintains feature plans in Linear during Claude Code plan mode. The orchestrator creates and updates Linear issues directly using MCP tools. Use when in plan mode, planning features, or creating implementation plans that should be tracked in Linear.

LLM prompt injection playbook. Use when testing AI/LLM applications for direct injection, indirect injection via RAG/browsing, tool abuse, data exfiltration, MCP security risks, and defense bypass techniques.

Karpathy's LLM Wiki: build/query interlinked markdown KB.

Unified writing system with intelligent model routing. Default: Claude. Options: GLM-4.7 (cheapest), GPT-4o/mini, Gemini, Grok. Includes browser automation for web interfaces. Cost-aware routing based on task complexity.

Attach judges to config variations for automatic LLM-as-a-judge evaluation. Create custom judges, configure sampling rates, and monitor quality scores.

Guide for creating effective fx/cc marketplace plugins. This skill should be used when users want to create a new Claude Code plugin (or update an existing plugin) for the fx/cc marketplace that extends Claude's capabilities with skills, commands, or hooks.

Initialize Claude Code project settings with standard hooks and language-specific permissions. Use when setting up a new project for Claude Code or adding standard configuration to an existing project.

File a feedback issue against the SDD plugin (joestump/claude-plugin-sdd) when an agent encounters significant friction with one of its skills — instructions that contradicted observed behavior, repeated tool failures, undocumented edge cases that burned tokens, or SKILL.md ambiguity that caused misinterpretation. Always prompts the user with the full proposed issue body before submitting. Use when an agent has just completed a workflow that involved real churn caused by the SDD plugin itself, not by the user's task.

Use when routing Claude Code through a local LiteLLM proxy to GitHub Copilot, reducing direct Anthropic spend, configuring ANTHROPIC_BASE_URL or ANTHROPIC_MODEL overrides, or troubleshooting Copilot proxy setup failures such as model-not-found, no localhost traffic, or GitHub 401/403 auth errors.

Optimizes AI skills for activation, clarity, and cross-model reliability. Use when creating or editing skill packs, diagnosing weak skill uptake, reducing regressions, tuning instruction salience, improving examples, shrinking context cost, or setting benchmark/release gates for skills. Trigger terms: skill optimization, activation gap, benchmark skill, with/without skill delta, regression, context budget, prompt salience.

Reviews and improves Claude Code skills against official best practices. Supports three modes - self-review (validate your own skills), external review (evaluate others' skills), and auto-PR (fork, improve, submit). Use when checking skill quality, reviewing skill repositories, or contributing improvements to open-source skills.

This skill should be used when the user asks to "review a PR against specs", "spec-driven code review", "review and fix PR", "review PR against openspec", "review and remediate", or when a PR implements features backed by OpenSpec living specs and needs both review and remediation in one session. Especially for security-critical components at trust boundaries. Combines parallel multi-agent review with confidence scoring and bounded remediation.

# MCP-Tasks Story and Task Management

Generate deterministic timestamps in YYYYMMDDHHMMSS format using bash. Use when you need timestamps for filenames, logging, or any situation requiring consistent timestamp formatting without LLM generation.

Triage GitHub issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Generate Uniswap v4 hook contracts via OpenZeppelin MCP. Use when building custom swap logic, async swaps, hook-owned liquidity, custom curves, dynamic fees, MEV protection, limit orders, or oracle hooks.

Single source of truth for the lenne.tech fullstack production-readiness checklist. Defines the eight pillars (configuration & secrets, observability & logging, health & lifecycle, security hardening, data durability, resilience under load, deployment hygiene, runbook & rollback) with concrete file/line evidence requirements per pillar, severity classification (Critical / Major / Minor), and a canonical machine-parseable report block. Activates whenever an agent or command needs to gate a release on production-readiness — currently used by /lt-dev:production-ready, lt-dev:production-readiness-orchestrator, and the devops-reviewer (read-only). NOT for OWASP-style code-level security review (use security-reviewer). NOT for npm dependency audits (use maintaining-npm-packages).

Use when the user wants to draft, scope, or formalize a feature — "write a PRD for X", "let's plan X", "scope this out", "what should X do", or when a tracker issue needs to be fleshed out before an agent plans it. Writes a PRD that a planning agent can consume in one shot without re-elicitation. Do NOT use for code edits, debugging, or PR reviews.

Guide for building dynamic agentic flows using ReAcTree hierarchical decomposition and Anthropic's workflow patterns. This skill should be used when users want to create complex multi-step agent workflows with deterministic gates, business rules, and comprehensive audit trails.

Manages cc-allow.toml configuration files for bash command, file tool, search tool, and WebFetch URL permission control. Use when the user wants to add, modify, or remove allow/deny rules, redirect rules, pipe rules, or URL rules for Claude Code tools.

Creates and improves Claude Code subagents interactively — scaffolds new agents from descriptions, refines existing agent definitions, tunes frontmatter, tools, model, and prompts. Triggers: create agent, new agent, claude code agent, make a subagent, improve agent, update agent, fix agent description, refactor agent, agent frontmatter, agent prompt, scaffold agent.

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, npm publishing (so `npx [email protected]` resolves), build verification, git tagging, GitHub releases, and changelog generation.

This skill should be used when the user asks to "create a command", "write a slash command", "build a plugin command", or wants to add custom commands to Claude Code.

Exports the project's Claude configuration (CLAUDE.md + ai-context/) to tool-specific instruction files for GitHub Copilot, Google Gemini, and Cursor. Trigger: /config-export, export config, copilot instructions, gemini config, cursor rules.

This skill should be used when the user asks to "validate agent contracts", "check contract compliance", "verify agent input/output", "pre-flight check", "debug agent failure", "why did the agent fail", or "check workflow state". Also triggered during OMT workflow when an agent starts or finishes execution. Validates input/output contracts for OMT agents using the Contract-First pattern.

Runs the research-team plugin's multi-agent research pipeline end-to-end from the main thread: decomposes a topic into 2-5 subtopics, spawns parallel research-team:research-specialist subagents for each, verifies their output on disk, then spawns a research-team:research-report-writer subagent to synthesize the final report. Activate ONLY when the user explicitly invokes this plugin — for example: "use research-team", "run the research-team coordinator", "research X with the research-team plugin", "research-team: research X", or when the user requests research that specifically needs Joplin-formatted output via this plugin's report-writer. Do NOT activate for generic research requests. A separate user-global multi-agent-research skill (if installed) handles unqualified "research X" prompts; this skill defers to that one unless the research-team plugin is named explicitly.

Provides GitHub Copilot CLI task delegation in non-interactive mode with multi-model support (Claude, GPT, Gemini), permission controls, output sharing, and session resume. Use when users ask to hand work to Copilot, compare models, or run Copilot programmatically from Claude Code.

Use when found gap or repetative issue, that produced by you or implemenataion agent. Esentially use it each time when you say "You absolutly right, I should have done it differently." -> need create rule for this issue so it not appears again.

Decomposes a plan file into beads with epics, dependencies, and self-documenting context. Use when you have a comprehensive feature specification or implementation plan that needs to be broken into actionable, trackable tasks for multi-agent execution.

Drive development using delegated agent workflows. Coordinates multi-agent task execution with proper supervision and result integration.

Execute Gemini CLI for AI-powered code analysis and generation. Use when you need to leverage Google's Gemini models for complex reasoning tasks.

Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.

Generates images using Google's Gemini model. Prioritizes standard resolution to save quota. Automatically opens images on macOS.

Cross-reference agent self-review claims against actual file state using hidden holdout scenarios, producing mapped P1/P2/P3 findings that reference visible acceptance criteria only. Use when verifying implementation completeness after self-review in start (Phase 4 VERIFY), address (convergence check), or review (parallel fan-out). Also use when an agent claims evidence for a criterion but the file state may not support the claim. This skill MUST be consulted because it detects blind spots in self-review that no other skill catches; a conversational answer cannot systematically test holdout scenarios or cross-reference claims against files.

Guide to Claude Code hooks — lifecycle events, handler types, decision control, and common patterns. Use when creating, debugging, or planning hooks for guardrails, context injection, quality gates, notifications, or automation.

Execute Hugging Face Hub operations using the `hf` CLI. Use when the user needs to download models/datasets/spaces, upload files to Hub repositories, create repos, manage local cache, or run comput...

Use an agent readiness report to identify and implement improvements that make a repository more agent-friendly. Proposes repo-appropriate fixes for each pillar, then implements them on request. Use after running a readiness report or when a user wants to improve their repo's AI-readiness.

Add Olakai monitoring to existing AI code — wrap your LLM client, configure custom KPIs, and validate the integration end-to-end

Decomposition playbook + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.

Indexes and queries project research graphs backed by hex-research MCP. Use for hypotheses, goals, benchmark runs, evidence depth, derived goal metrics, lineage, generated research maps, and graph audits.

Reference for Nathan's agent skills setup: the nweii/agent-stuff and nweii/agent-stuff-private repos, frontmatter conventions, changelog practices, privacy tiers, and migrating locally-developed skills into a repo. Use when creating, editing, migrating, or installing skills in Nathan's environment.

Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.

Author SYSTEM.md or APPEND_SYSTEM.md for pi coding agent. Use when extending the default system prompt with custom principles, guidelines, or project rules.

Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer for context survival, Compaction Recovery, and battle-tested security patterns. Part of the Hal Stack 🦞

Orchestre une équipe d'agents spécialisés pour les tâches complexes. Auto-détecte le type, compose l'équipe, coordonne les phases analyse → challenge → implémentation → QA.

Single source of truth for running the package.json `check` script across lt-dev review and rebase workflows. Defines discovery (multi-package monorepo aware), the iterate-until-green auto-fix loop, the mandatory audit-finding fix escalation ladder, residual classification (Accepted vs Critical), test-duplication avoidance, and report formatting. Activates whenever an agent or command needs to validate runnability via `check` — currently used by `/lt-dev:review`, `code-reviewer`, `branch-rebaser`, and `test-reviewer`. NOT for general npm package maintenance (use maintaining-npm-packages). NOT for the rebase orchestration itself (use rebasing-branches).

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

This skill should be used when setting up Claude Code rules in a project by symlinking from rbw-claude-code templates, such as adding Python coding standards, anti-slop rules, or other shared rules.

Apply when the right APPROACH is unknown and must be discovered before committing — a hard algorithm or big-O/rendering decision, a complex state machine, tricky native/platform integration, a gnarly gesture/animation problem, a performance optimization, anything where you would otherwise guess an approach and build it. Use this whenever the task is "figure out how to...", "what is the best way to...", "optimize X", "this is slow/complex", "spike on Y". The dominant failure mode is COMMITTING TO THE WRONG APPROACH and DECLARING FALSE VICTORY against a weak baseline (agent psychosis). The rule is: establish the FLOOR (theoretical limit / reference) FIRST and judge every result against it, enumerate solution CLASSES (consult the mental-models skill) rather than optimizing within one, benchmark, then collapse the spike into a feature or refactor. Delegates to feature-workflow's change-kind gate-runners with --kind spike. Do NOT use once the approach is known — collapse and run that kind's loop.

Parallel task orchestration CLI that dispatches work to AI workers (via Claude Code) in isolated git workspaces. Use when the user wants to draft, create, run, or manage tasks, delegate tasks to workers/subagents, or mentions subtask or Subtask.

Generate an audience-appropriate stakeholder update by pulling live GitLab sprint data and Drive artifacts. Produces human-facing communication from AI-native project artifacts — status reports, client updates, executive summaries, engineering updates. Works in Claude Cowork and Claude Code.

Redirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-unit, testing-e2e, testing-integration, testing-llm, or testing-perf.

Use this agent for processing inbox, filing notes, organizing the vault, updating living docs, maintaining backlinks and tags, and running audit passes. The organizer that turns raw captures into structured knowledge.

Transform text or documents into AI-generated infographic pages that explain concepts visually using Gemini Pro 3 for generation and Claude Vision for quality evaluation

Implementation session — execute milestones from a plan, write production code and tests, follow codebase patterns, surface deviations, maintain living docs. Launched via: claude --agent wf:builder

Adds one or more contact records to the Carta CRM via the Carta CRM MCP Server. Use this skill when the user says things like "add a contact", "create a contact record", "add contact to CRM", "save a contact", "upload contact to Carta CRM", or "/add-contact". Collects contact information conversationally, then creates it via the MCP server. Only name is required — all other fields are optional.

Creates one or more deal records in the Carta CRM via the Carta CRM MCP Server. Use this skill when the user says things like "add a deal", "create a deal", "log a deal", "add deal to CRM", "add deal to Carta CRM", or "/add-deal". Collects deal information conversationally, then creates it via the MCP server.

Adds one or more fundraising records to the Carta CRM via the Carta CRM MCP Server. Use this skill when the user says things like "add a fundraising", "create a fundraising", "log a fundraising round", "add fundraising to CRM", "create fundraising record", or "/add-fundraising". Collects fundraising information conversationally, then creates it via the MCP server.

Create new Claude Code skills with proper structure. Use when adding a skill or slash command.

Scaffold and operate an opt-in `Agent activity log` table that records what the agent did, decided, and got blocked on across a long-running or multi-session Airtable workflow. Use whenever a workflow skill (product-ops, sales-ops, marketing-ops, etc.) is being set up for an agent-driven motion (recurring triage, multi-step plan, automated monitoring, agentic workflow), or when the user explicitly asks for "agent activity tracking," "audit log of agent decisions," "agent memory," "track what the agent did," or similar. The pattern is opt-in (front-load the offer, frame as auditability for the user's benefit, not surveillance). Composes into workflow skills the same way `show-airtable-link` does — workflow skills point at this skill rather than re-implementing the schema inline.

Extract and display the final message from a Claude agent JSONL file. Use when the user wants to see an agent report, view agent output, extract agent results, check what an agent produced, or read the final response from a subagent. Triggers on requests like "show me agent report", "what did agent X produce", "extract agent output", "view agent results", or "get the report from agent ad42ecb".

Use when analyzing server logs to understand how AI crawlers (GPTBot, ClaudeBot, PerplexityBot) interact with your site. Use when optimizing content placement for LLM retrieval, diagnosing why AI search isn't citing your content, or auditing crawl patterns to find optimization gaps.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Use when user wants their Claude Code pet (/buddy) to sing a song. Triggers on any request that combines the concept of their Claude Code buddy, pet, or companion with singing or music. Supports multilingual triggers — match equivalent phrases in any language.

Configure AEM 6.5 LTS replication agents for content publishing, dispatcher cache flushing, and reverse replication

Use when creating a new Claude Code plugin package. Use when user says "create plugin", "new plugin", "scaffold plugin", "plugin template".

Internal helper agent. Invoked by orchestrator agents via Task tool. Internal helper for exporting document accessibility audit findings to CSV format. Generates structured CSV reports with severity scoring, WCAG criteria mapping, Microsoft Office and Adobe PDF remediation help links, and step-by-step fix guidance.

Evaluates FiftyOne plugins for quality, security, and agent-readiness. Use when reviewing a plugin before installation, auditing an existing plugin, validating a plugin you just built, or assessing community plugins for safety. Produces a structured report with scores and actionable recommendations.

Route `/gemini ...` requests to the Cursor headless CLI for one-shot autonomous execution. Use when the user explicitly invokes `/gemini` or asks to hand a task off to Cursor agent. Preserves the prompt verbatim, runs in headless print mode, and returns Cursor's output.

Use the gemini-cli-integration skill PROACTIVELY when analyzing large codebases, multiple files, or directories. Leverages Google Gemini's massive context window with @ syntax for file inclusion to handle comprehensive codebase analysis, implementation verification, and architectural understanding.

Git worktree management for parallel agent team development. Triggers: 'create worktree', 'worktree setup', or during /delegate dispatch. Do NOT use for branch creation without delegation context.