スキルを探す

Quantitative cost measurement for technical research — token injection costs, payload sizes, context window consumption, and file-level counts from actual repo files. Use when a technical-researcher orchestrator needs the cost dimension of adding or changing something: how many tokens will it inject, how big are the artifacts, what is the context window impact? This is NOT blast-radius analysis (which files break) — it covers size, tokens, and performance cost only.

日本語の概要は準備中です。原文の説明を表示しています。

Grooms a GitHub milestone for parallel execution — batch-grooms ungroomed items, assesses scope gaps, analyzes cross-item dependencies via Impact Radius overlap, builds conflict groups, assigns items to execution waves, and persists the dispatch plan via dispatch_create_plan MCP tool. Calls dispatch_wave_start per wave to register state. Use when preparing a milestone for /work-milestone execution. Pass the milestone number as the first argument. Requires milestone items assigned via /group-items-to-milestone.

日本語の概要は準備中です。原文の説明を表示しています。

Generates one worker task prompt conforming to the CLEAR + selective CoVe task design standard and swarm-task-planner structure. Use when creating or rewriting a single task entry or task block inside a plan — providing a title and brief description as input.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate why something happens — confirm the question and success criteria with you, then trace the root cause with an evidence chain.

日本語の概要は準備中です。原文の説明を表示しています。

Certifies that a feature achieves its original objectives via goal-backward verification (SAM Stage 7). Use when all tasks pass forensic review — starts from expected outcomes, works backwards to verify each was achieved, and returns CERTIFIED or NOT_CERTIFIED with specific gaps.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate parallel agent dispatch as a manager — not a micromanager. Use when coordinating 2+ independent workers, running SAM task waves, relaying discoveries between worker waves, handling blockers, or synthesizing results. Covers both SAM structured dispatch (the task does the work) and ad-hoc dispatch (reference agent-orchestration for prompt template).

日本語の概要は準備中です。原文の説明を表示しています。

Local codebase analysis research angle — derives behavioral contracts, coding conventions, SKILL.md flow insertion points, and agent data availability maps from actual source files. Use when the blocking question is answered by reading the repository: what does this function actually do, what pattern does the codebase use for X, where in this workflow does a new step go, or what data does this agent already have.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews skill, agent, and plugin artifacts against their intended consumer's schema and runtime contract. Loaded by dh:code-reviewer for SKILL.md, agent definitions, or plugin manifests; checks discovery, frontmatter, triggers, tools, context cost, bundled references, and caller handoffs.

日本語の概要は準備中です。原文の説明を表示しています。

Use for architecture review, dependency graphs, coupling analysis, or circular dependency detection. Establishes project module namespaces and traces imports plus Claude plugin hook, skill, script, PEP 723, and MCP boundaries. Emits partitioned Mermaid graphs with cycle, coupling, and ownership signals; verifies contract and consequence before assigning severity. Registers diagrams as codebase-analysis artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

Use when orchestration or planning agents are producing task plans, task prompts, or TASK.md instructions that must be unambiguous, verifiable, and resistant to hallucination. Applies CLEAR (Concise, Logical, Explicit, Adaptive, Reflective) to structure and write agent task prompts, then adds CoVe (Chain of Verification) checks where accuracy risk is meaningful. Activates on draft task prompts, swarm plans, migration tasks, and multi-step plans requiring independently executable steps.

日本語の概要は準備中です。原文の説明を表示しています。

Audit documentation claims against implementation and authoritative repository evidence. Use when checking whether README, architecture, configuration, API, usage, or feature documentation is stale, incomplete, contradicted by code, missing implemented behavior, or inconsistent with a normative contract.

日本語の概要は準備中です。原文の説明を表示しています。

Fetch and report current API syntax, changelog entries, and breaking changes for a specific library or protocol version. One research angle within a parallel technical-research set — runs independently and returns a structured cited report. Invoke when a specific library name and version are the target.

日本語の概要は準備中です。原文の説明を表示しています。

Dasel v3 patterns for querying Tomcat web.xml deployment descriptors — use when inspecting servlet enumeration, filter chain discovery, listener listing, context parameter extraction, or init-param inspection in web.xml files

日本語の概要は準備中です。原文の説明を表示しています。

Use when extracting specific data points from large agent output transcripts, kaizen analysis reports, or JSONL session files — tool timings, query counts, error summaries, or any structured facts — without loading raw data into orchestrator context. Activates when the orchestrator needs targeted facts from large files and context pollution must be avoided.

日本語の概要は準備中です。原文の説明を表示しています。

Transform transcript analysis findings into actionable improvements. Triggers on "generate hooks from findings", "improve agent", "fix anti-pattern", "kaizen improvement", "generate hook proposals", or "create improvement plan". Provides templates for hook generation, agent prompt refinement, skill patches, CLAUDE.md updates, and script automation from analysis data.

日本語の概要は準備中です。原文の説明を表示しています。

Agentskill kaizen plugin documentation index. Load when needing to read about cross-platform notes, improvement plans, or DuckDB integration.

日本語の概要は準備中です。原文の説明を表示しています。

Shapes for running many sub-agents at once — fan-out with a barrier, maker/checker, generate-and-filter, tournaments for ranking, hypothesis fan-out for root cause, and loops that stop on a condition with a cap. Use when a phase has several independent targets, when a task is too large or too repetitive for one window, when the same edit applies across many files, when ranking or judging a large set, when several hypotheses compete, or when work must repeat until a signal says stop. Does not apply when units depend on each other's results or the cause is still unknown — investigate first, then parallelize.

日本語の概要は準備中です。原文の説明を表示しています。

Decompose substantive work into phases, dispatch each phase to a sub-agent, and adjudicate what comes back. Use whenever a request asks for implementation, investigation, a fix, a review, or any change to files — including small ones — and whenever you are about to read source or run a diagnostic yourself instead of handing it off. Also use when a report from a sub-agent needs judging, when a phase needs re-dispatching, or when a user names one instance of a pattern. Does not apply when your own prompt begins "Your ROLE_TYPE is sub-agent." — then follow references/sub-agent-contract.md instead.

日本語の概要は準備中です。原文の説明を表示しています。

Creative reasoning framework for ill-defined problems where conventional solutions are suboptimal. Use when the problem has ambiguous goals, vast solution space, no single correct answer, or requires innovation. Implements three paradigms — combinational (novel combinations of familiar ideas), exploratory (expand solution space boundaries), transformative (alter fundamental constraints). Do not use for well-defined problems, mathematical puzzles, or tasks requiring convergent reasoning.

日本語の概要は準備中です。原文の説明を表示しています。

Transitions a GitHub milestone from planning to active execution. Use when the team is ready to begin a sprint or release cycle — bulk-transitions open issue labels from status:needs-grooming to status:in-progress, updates GitHub Projects V2 Status to In Progress, and confirms before applying changes. Requires milestone number as argument. Use after /group-items-to-milestone.

日本語の概要は準備中です。原文の説明を表示しています。

Activates Standard of Excellence enforcement for the current session. Load before starting any task to apply completion standards: finish the whole thing, fix the root cause, ship the complete working result. Blocks partial solutions, workarounds, deferred threads, and invented content limits when the permanent solve is within reach. Triggers: 'do the whole thing', 'boil the ocean', 'standard of excellence', 'finish it completely', before starting any implementation, refactoring, or multi-step task where partial output is a risk. Does NOT apply to: read-only queries, one-line typo fixes, pure knowledge questions, or single-output summarize requests.

日本語の概要は準備中です。原文の説明を表示しています。

Modern Git workflows, best practices, and commands. Use when the user asks about Git branch management (git switch vs checkout), file restoration (git restore), fixup commits, autosquash rebasing, git worktrees, rerere, force-with-lease, repository cleanup (git clean, stale branches, bloat analysis), history navigation (revision syntax, range notation, pickaxe search), recommended global git config, or GitButler and the but CLI.

日本語の概要は準備中です。原文の説明を表示しています。

Integrates patterns from external sources (URLs or local files) into local skills, agents, and plugins. Use when comparing external agent definitions against local equivalents, extracting best practices from frameworks like GSD or BMAD-METHOD, enhancing local skills with external workflow patterns, or adding interoperability with external tool ecosystems. Runs a 3-phase workflow — parallel candidate mapping, contextual enhancement, and validation — with source attribution and backlog tracking for deferred enhancements.

日本語の概要は準備中です。原文の説明を表示しています。

Walks a user from one rough content idea to a finished post, platform-adapted variants, and repurposed follow-on assets using a 7-step sequential prompting workflow. Use when the user wants to turn a half-formed idea, frustration, story, or client situation into publishable content quickly and consistently — covering idea extraction, hook generation, outline, draft, humanizer pass, platform adaptation (LinkedIn, Reddit, X/Twitter, newsletter, Telegram), and repurpose engine.

日本語の概要は準備中です。原文の説明を表示しています。