菜单
For any non-trivial task, start in Plan Mode, produce a clear step-by-step plan with risks and verification method, and wait for explicit approval before any edits. Use when the user says "plan this", "use plan mode", "don't edit yet", or describes a complex feature/refactor/migration.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Perform focused architecture and modularity reviews. Identify boundary violations, god objects, tangled dependencies, and propose the smallest reversible improvements. Use the repo-graph MCP when available. Trigger with "architecture review", "check the boundaries", "is this modular enough?".
Enforce conventional commits, clean branch strategy, small focused diffs, and PR-ready history. Use before any commit or when preparing work for review. Triggers: "commit this cleanly", "prepare for PR", "fix the git history", "use git-discipline".
Discover available MCP servers, evaluate their fit, install and configure them safely, and then use them effectively within sessions. Use when the user needs new capabilities (browser control, advanced git, observability, etc.) or when existing MCPs are under-utilized. Triggers: "set up MCPs", "install the right tools", "add an MCP for...", "what MCPs do we need?"
Perform focused security reviews on code, diffs, hooks, and MCP servers. Look for auth issues, injection, secret leakage, unsafe tool/MCP usage, and hook risks. Use for any change involving external input, credentials, or agent capabilities. Triggers: "security review", "audit this diff", "check for vulnerabilities".
Run parallel independent subagents on the same investigation or design question, collect structured outputs, then synthesize the best elements or score approaches. Use for complex research, architecture decisions, or when multiple valid strategies exist. Trigger with "run an arena", "parallel subagents", "compare approaches", "investigate from multiple angles".
Apply rigorous test-first development. Write failing tests (or characterization tests) that capture desired behavior before implementing. Maintain high test coverage on changed code. Use for new features, refactors, and bug fixes where regression protection matters. Triggers: "TDD this", "test first", "write the test then implement", "add characterization tests".
| name | plan-mode-orchestrator |
| description | For any non-trivial task, start in Plan Mode, produce a clear step-by-step plan with risks and verification method, and wait for explicit approval before any edits. Use when the user says "plan this", "use plan mode", "don't edit yet", or describes a complex feature/refactor/migration. |
| version | 1.0.0 |
| author | Cobus Greyling |
The single most important skill in this arsenal. Enforces disciplined agentic work.
Immediately enter or confirm Plan Mode mindset.
Investigate first (read-only where possible).
grok inspect if configuration or skills may be relevant.Produce a high-quality plan with these sections:
grok inspect, etc.)Present the plan and STOP.
After approval:
For large investigations, spawn 2–4 subagents with clear charters (e.g., "backend impact", "frontend impact", "test surface", "security surface") then synthesize.