スキルを探す

Decide and execute native Codex worker delegation for the main coordinating agent. Use it for a substantial investigation, implementation, fix, or verification responsibility that can be handed over whole, and for continuing or reworking the same worker; a temporary worker, an explicit solo request, casual explanation, or tiny or nearly finished work does not trigger another delegation.

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

Run or continue an operator-authorized external ACP worker through cwr-acp, using a configured default or an explicitly selected route. Use when the operator has selected ACP for this responsibility; native workers and merely discovering an ACP-capable CLI do not trigger it.

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

Turn a rough feature, product interaction, or architecture idea into a concrete design. Use when meaningful decisions remain open; avoid for already-clear local edits.

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

Review a diff, commit, branch, PR, or implementation for actionable correctness and risk issues without duplicate reviewer loops or invented findings.

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

Preserve an approved specification through a complete implementation plan and execution. Use for major refactors, migrations, or multi-session work when a confirmed spec is authoritative; keep scope and order changes explicit.

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

Verify code or product claims after changes using fresh, risk-matched evidence. Use before saying a bug is fixed, tests pass, requirements are met, or a branch is ready.

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

Choose, reuse, restore, park, or clean up Git workspaces while preserving work and host ownership. Create isolation only when it resolves a real conflict; inspection does not authorize creation or deletion.

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

Execute an existing implementation plan or settled multi-step request through connected slices with targeted checks and controlled plan drift.

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

Finish a development change safely by inspecting the final tree, verifying at the right scope, and performing only the requested Git or PR actions.

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

Investigate and fix bugs, failing tests, regressions, build failures, or unexpected behavior using boundary localization, evidence, and bounded hypotheses.

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

Use for hands-on repository work when a quiet, risk-scaled engineering method can improve design, implementation, debugging, review, delegation, workspace lifecycle, or verification. Keep clear local changes direct, preserve the complete requested outcome, and add method only where risk or uncertainty justifies it. Do not use for general technical explanations, simple file lookup, casual discussion, or non-engineering writing.

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

Apply risk-based test-driven development to bugs, domain logic, state transitions, parsers, contracts, migrations, and behavior where a failing test sharpens the design.

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

Choose responsibility for substantial work before deep execution: keep one responsibility's coupled parts in a single lane, and hand a bounded or independent lane to a worker when clean context, an unknown cause, independent review, or coordinator attention materially improves the outcome.

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

Create an implementation plan sized to settled work. Use when a multi-step change benefits from sequencing, file targets, and explicit verification.

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

Evaluate and act on code-review feedback with technical judgment. Use before applying external suggestions, especially when feedback is ambiguous, broad, or may conflict with repository constraints, and carry confirmed corrections to relevant consumers without widening scope.

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

Complete MCP engineering work on the live path: build or repair servers and Apps, debug stdio or Streamable HTTP, migrate protocol/SDK/transport versions, reconcile source with package and activated runtime, inspect capability/effect authorization, and verify named-host claims without promoting weaker evidence. Use for real Model Context Protocol implementation, review, migration, runtime, or host-integration tasks. Do not use for ordinary non-MCP APIs, generic frontend work, or incidental product copy.

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

Design, audit, harden, review, or upgrade MCP servers and MCP Apps with revision-aware protocol profiles, explicit HTTP/deployment boundaries, capability-centered validation, bilingual reporting, and reproducible evidence. Use for MCP server architecture, JSON-RPC or Streamable HTTP bugs, security hardening, protocol-version migration, MCP Apps widget boundaries, review reconciliation, test planning, and public engineering evidence.

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

Resolve repository documentation authority, repair reading paths and explanations, or shape a bounded public projection. Maintain docs after a bounded change when indirect reader promises, generated or paired sources, version/evidence boundaries, or unclear authority need attention. Ordinary known updates stay in normal development; not for isolated prose polishing, code review, or broad runtime audits.

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

Design, audit, harden, review, or upgrade MCP servers and MCP Apps with revision-aware protocol profiles, explicit HTTP/deployment boundaries, capability-centered validation, bilingual reporting, and reproducible evidence. Use for MCP server architecture, JSON-RPC or Streamable HTTP bugs, security hardening, protocol-version migration, MCP Apps widget boundaries, review reconciliation, test planning, and public engineering evidence.

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