'subagent' 검색 결과

Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces, explicit wrapped errors, context propagation) plus Cobra/Viper conventions where applicable. Use when a user has a Go spec to review, asks "is this spec ready?", or is about to implement from a written design. Distilled from spf13/go-skills and adapted to this repo's conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Route user requests to the right skill, decompose complex work into parallel subagents, and manage project phase transitions. Load when the user asks "what should I do next", "which skill should I use", "orchestrate this", "run the full workflow", "split this into parallel tasks", or when a complex request spans multiple skills. Also triggers on "coordinate agents", "parallel execution", "task decomposition", "agent workflow", "what phase am I in", or when the user gives a broad instruction that requires multiple skills in sequence. This is the project's brain — it decides what runs, when, and whether to parallelise.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and scaffold new skills, subagents, and MCP surfaces. Use when choosing which primitive to create. NOT for invoking existing agents, generic coding help, or deployment work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to up to 15 specialists (8 always + 7 conditional), generates health score. Use when user says audit, full SEO check, analyze my site, or website health check.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Working playbook preloaded into the reviewer helper; the coach updates its Lessons after each round. Use only when acting as reviewer or coaching it. NOT for writing a verifier brief (use subagent-dispatch).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pre-commitment attack on a plan by an agent that did not write it. Use when presenting a feature-deep-dive plan, assigning vision-to-fleet briefs, moving a register to build mode, ratifying a scope list, or coding a new contract or table. NOT for built work or DONE reports (use subagent-dispatch).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The recipe for production-grade AI Matrx platform agents built through the AI Dream MCP. Use when asked to create, build, configure, improve, rename, or re-instruct a platform agent, or when a deliverable or kind needs an agent to emit it. NOT for Claude Code subagents or .claude/agents files.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

サブエージェントを活用した並列実行・調査委譲・コンテキスト管理の戦略。複雑な問題への対処、調査・探索タスク、複数の選択肢の比較検討、大規模なリファクタリングなどでこのスキルを参照する。「調べて」「比較して」「並列で」「複数のアプローチを試して」といったリクエストや、メインのコンテキストが肥大化しそうな場面で使う。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs a session's fan-out — splits a large request into tiered, recoverable units, dispatches and reconciles them against the repo. Trigger when work needs many agents or spans many repos or files (rebuild, re-architect, sweep, migrate, 'do all of this'); when subagents would launch with no model or effort set; for the plan table (units, models, tokens, meters) before launch; to resume a unit that died or hit a usage limit; when units would share a repo; or say dispatchwright (plan, dispatch, resume, audit, refresh). Tiers come from its own table (scoutwright flags it stale); pacing, pacewright's; hooks, rigwright's; schedules, agentwright's.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Paces a Claude subscription's usage — how fast to spend this week, what can still run at N% weekly, whether planned work fits before a reset. Reads the 5-hour, weekly, per-model and CI-minutes meters, sets a spend mode (normal, pace, turbo, overnight, work-day, owner-away, reset-eve) and re-cuts waves that don't fit. Also when something ate usage overnight, CI minutes run low, context runs high (compact or clear?), a new model needs a measured baseline, or which skill or subagent used tokens; or say pacewright (check, mode, fit, context, uba, baseline, spend, refresh). The plan table is dispatchwright's; the handoff, handoffwright's; one artifact's cost, skillwright's slim; the meter statusline, rigwright's; a scheduled check, agentwright's.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pattern for progressively refining context retrieval to solve the subagent context problem

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when executing implementation plans with independent tasks in the current session

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement a whole spec by orchestrating subagents over its ticket graph; auto-detects the most recent task folder when no argument is given.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds production-ready applications with the Claude Agent SDK for Python, covering orchestrators with subagents, programmatic agent configuration, hooks, and permissions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Parallel 3-agent cleanup of recent code changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Operating discipline distilled from Claude Fable 5 for sessions and subagents on weaker models (Opus 4.x, Sonnet 5/4.x, Haiku 4.5) doing agentic coding. Load it at the START of any non-trivial task when not running on Fable 5. Операционная дисциплина мышления Fable 5 для менее сильных моделей. Загружай в начале любой нетривиальной задачи (дебаг, рефакторинг, ≥2 файлов, незнакомый код), когда работаешь НЕ на Fable 5 — и указывай сабагенту на Opus/Sonnet/Haiku прочитать этот скилл вместе с нетривиальным заданием. Триггеры — «думай как Fable», «fable-mode», «включи дисциплину», «работай аккуратно», запуск сабагента на слабой модели, повторяющиеся ошибки/переделки в сессии. НЕ нужен для тривиальных правок (rename, опечатка, one-liner) и чисто разговорных ответов.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the full Forge pipeline unattended: each phase is reviewed by a fresh evaluator subagent, the findings feed back, and the run advances itself. Use when the user runs /forgemaster-auto or wants a feature built end to end without approval gates.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute a trivial task inline — no subagents, no planning overhead

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnose user-reported AILI/ROSE harness or workflow behavior problems without editing files; use when the user says a command, skill trigger, subagent packet, memory flow, installer, docs, or agent prompt behavior is wrong and wants to know where the issue lives and how to fix it. Do not use for normal product-code bugs; return any approved modification need to ROSE.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prefer a fresh matching specialist for a clear bounded non-trivial package when current capabilities and permissions permit it; use direct ROSE work only for accepted direct-work exceptions or a concrete block.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produce or apply an approved report-first proposal for workflow, ROSE, skill, command, subagent, memory, install, or harness-doc changes; use after harness-issue-triage localizes a harness problem or when the user explicitly requests harness maintenance, and do not edit core harness files without explicit human approval.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces, explicit wrapped errors, context propagation) plus Cobra/Viper conventions where applicable. Use when a user has a Go spec to review, asks "is this spec ready?", or is about to implement from a written design. Distilled from spf13/go-skills and adapted to this repo's conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build autonomous AI agents with Claude Agent SDK. Structured outputs guarantee JSON schema validation, with plugins system and hooks for event-driven workflows. Prevents 14 documented errors. Use when: building coding agents, SRE systems, security auditors, or troubleshooting CLI not found, structured output validation, session forking errors, MCP config issues, subagent cleanup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.