菜单
Use when orchestrating broad or multi-issue subagent work where agents, lanes, reviews, or PRs may become too small; use for CuraOS waves, owner-path bundles, local issue queues, many-agent execution, or requests to run more lanes without wasting work in micro PRs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when asked to plan, decide, or execute subagent orchestration: subagents, delegated agents, parallel workers, review agents, multi-source research, broad audits, PR/MR review, worktree-aware execution, model/effort selection, or agent-driven execution.
Use when viewing or printing source/config files to the terminal with syntax highlighting and line numbers - a cat replacement that colorizes code, configs, and diffs. Use bat instead of cat when humans need highlighted file display.
Use when the user wants to format or lint JavaScript, TypeScript, JSX, TSX, JSON, JSONC, CSS, GraphQL, HTML, Vue, Svelte, or Astro - biome is the unified Rust-based replacement for prettier + eslint, doing both with one binary and one config file.
Use when the user formats or lints Dart or Flutter source code from the command line - dart format is the formatter (Black-style, mutates by default) and dart analyze is the static analyzer (errors, warnings, lints). Both ship with the Dart SDK; no separate install.
Use when the user wants a structural, syntax-aware diff between two source files or git revisions - a diff that parses each side as code (Rust, TS, Python, Go, …) and ignores reformatting, brace movement, or whitespace noise. Binary is difft; use for syntax-aware diffs, not plain file viewing.
Use when the user wants to load environment variables when entering a directory, auto-set env per project, scope env vars without polluting the global shell, set PATH per project, or load a .envrc on cd.
| name | macro-subagent-orchestration |
| description | Use when orchestrating broad or multi-issue subagent work where agents, lanes, reviews, or PRs may become too small; use for CuraOS waves, owner-path bundles, local issue queues, many-agent execution, or requests to run more lanes without wasting work in micro PRs. |
Use this standalone skill for broad orchestration. It covers the macro versions of subagent selection, lane planning, worker dispatch, review loops, verification, and integration. Do not also load subagent-orchestration or subagent-driven-development for the same broad wave unless you are deliberately switching a single lane into a narrow micro task.
See references/when-to-use.md. Load this skill for broad orchestration, owner-path bundles, local issue queues, many-agent execution, or any request to increase lanes without repeating micro PR waste.
See references/invocation.md. Before spawning agents, write a lane plan with:
See references/patterns.md. Core rule: lane size before lane count.
Local issue rows, checklist rows, and verification rows may stay small. Worker lanes and PRs should not. A macro lane bundles compatible work that one agent can own, test, review, and PR as a coherent deliverable.
See references/anti-patterns.md. Increasing agent count before packing compatible work repeats the Wave 0 failure mode.
If a lane has only one tiny file, one review nit, or one local child row, repack it unless it has a recorded split reason.
This skill covers the macro-level cases from subagent-orchestration and subagent-driven-development. Do not load those micro skills for the same broad wave. Use them only after deliberately narrowing one lane into a small standalone task.
