703건 · 관련도순
Handle small development tasks directly in the current session, such as typo fixes, configuration changes, and minor refactoring. It skips subagents and PLAN.md files for work that can be described briefly and finished quickly.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a recurring workflow into a new agent skill through guided discussion. Define use cases, activation conditions, file structure, and instructions, then create and validate SKILL.md and supporting files, including workflows using external tools through MCP.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit custom subagents, the specialized assistants used by Claude Code and Codex. Check whether definitions load, identify overlapping roles, review model choices and tool access, and receive scores with prioritized fixes and optional confirmed edits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Delegate focused coding, research, review, or verification work to a bounded DevSpace subagent. Use when a task benefits from separate context, a specialist perspective, or a follow-up with the same worker.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Troubleshoot Kode permission prompts/denials (tool allowlists, commandAllowedTools, dontAsk fail-closed, subagent inheritance). Use when tools are unexpectedly blocked, permission prompts repeat, or behavior differs between main agent and subagents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use parallel subagents for large-scale paper screening and deep dive analysis
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch OpenAI Codex CLI as a subagent (ChatGPT subscription auth, no API key). Use when delegating a self-contained coding task to Codex from another agent — parallel implementation work, a second opinion, or an independent verification pass.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Checks which private files (.env, keys, secrets) Claude Code and its subagents reached in this project, whether a value came into an agent's context, and which key to change, by running the open source agentwhy CLI over the session records Claude Code already keeps on disk. Use when the user asks whether the agent or a subagent read their .env or other secrets, which private files a session touched, whether a key leaked into the conversation, or which key to rotate. Runs locally and never prints a secret value.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or revise Agent Skills, host plugins and subagents, MCP servers and client configurations, hooks, and marketplace catalogs against their actual specifications. Use when building reusable agent capabilities or consolidating creator tooling without inventing a universal host format. Trigger with "create an agent skill", "build a plugin", "create an MCP server", "add a subagent", or "scaffold an agent integration".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
当用户要求数学建模、建模竞赛、建模分析、代码求解、结果可视化或生成数学建模论文时使用。支持完整三阶段流程、单独执行任一角色，以及在关键节点使用独立 Subagent 进行阶段内质检；默认只启用质检 Subagent，用户可明确选择额外协作。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent per task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt engineering using subagents for isolated testing
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or dependencies - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Patterns for parallel subagent execution using the Agent tool (formerly Task). Use when coordinating multiple independent tasks, spawning dynamic subagents, or implementing features that can be parallelized.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
INVOKE THIS SKILL when using subagents, task planning, or human approval in Deep Agents. Covers SubAgentMiddleware, TodoList for planning, and HITL interrupts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit hook delivery health from Agent Monitor data — balance PreToolUse vs PostToolUse (a gap means tools that started but never reported back), detect missing Stop/SubagentStop terminators (sessions/subagents that never closed), and check for stale ingestion (no recent events). Use when hooks look unreliable or events seem to be dropping.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug a specific session by inspecting its full event chain (PreToolUse, PostToolUse, Stop, SubagentStop, Compaction, APIError, TurnDuration, Notification events), agent hierarchy (recursive parent/child tree with subagent_type and depth), token usage with compaction baselines, workflow intelligence data (orchestration DAG, error propagation by depth), and session metadata (thinking_blocks, turn_count, total_turn_duration_ms).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parallelize independent sub-jobs across fresh-context subagents instead of one bloated context. Use when a goal branches into many independent pieces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute multi-task implementation plans by dispatching a fresh implementer subagent per task with independent review gates. Use when implementing plans, executing multi-task PRs, or transitioning from planning to implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements GitHub or GitLab issues via parallel subagents with review gates between task batches. Use when resolving multi-step issues end-to-end.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.