菜单
Plan a .NET feature before coding. Spawns planning-orchestrator which researches, decomposes tasks, and writes `.claude/plans/{slug}/plan.md`. Use for any non-trivial change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Full-project health audit — spawns 5 specialists (dotnet-reviewer, security-analyzer, testing-reviewer, performance-profiler, deployment-validator) in parallel. Use for onboarding or pre-release.
Analyze project/namespace boundaries, detect circular refs and layering violations via dotnet-depends and solution graph. Use before major refactors or to validate Clean Architecture.
Senior-engineer challenge mode — aggressively question the current approach, hunt for N+1 queries, captive deps, missing auth, sync-over-async, leaks. Use before finalizing significant changes.
Capture a solved problem as institutional knowledge. Writes `.claude/solutions/{category}/{slug}.md` with symptoms, root cause, fix, category, tags. Use after notable fixes.
Generate or update documentation — XML doc comments, README, architecture docs, OpenAPI descriptions. Uses code as source of truth; no hallucinated features.
Extract durable lessons from a just-finished fix — propose CLAUDE.md rule, Iron Law addition, or Solution doc. Use after resolving a surprising/repeatable bug.
| name | plan |
| description | Plan a .NET feature before coding. Spawns planning-orchestrator which researches, decomposes tasks, and writes `.claude/plans/{slug}/plan.md`. Use for any non-trivial change. |
| effort | high |
| argument-hint | <feature description> | --existing <plan.md> |
Produces a reviewable plan file at .claude/plans/{slug}/plan.md before
any code is written.
| Signal | Use /dotnet:plan? |
|---|---|
| Feature touches >3 files | Yes |
| New entity / API / UI surface | Yes |
| Refactor crossing module boundaries | Yes |
| Unclear scope | Yes (scope classification is the first output) |
| Single-line fix | No — use /dotnet:quick |
| Bug debugging | No — use /dotnet:investigate |
| Pure question ("how does X work") | No — answer directly |
file:line — vague plans fail at executionplanning-orchestrator (opus)
context-supervisor to compress researchplan.md/dotnet:plan --existing .claude/plans/{slug}/plan.md
Research gaps, add missing tasks, flag risks. Doesn't rewrite — annotates.
/dotnet:triage turns a review verdict into ready-to-work plans. Call
plan to expand/refine a single triaged item.
After plan written:
/dotnet:brief .claude/plans/{slug}/plan.md — walk through the plan
interactively (optional)/dotnet:work .claude/plans/{slug}/plan.md — start execution/dotnet:full — full lifecycle (plan + work + review + compound)${CLAUDE_SKILL_DIR}/references/planning-workflow.md — end-to-end flow${CLAUDE_SKILL_DIR}/references/plan-template.md — the plan.md
structure${CLAUDE_SKILL_DIR}/references/complexity-detail.md — Tiny/Small/
Medium/Large heuristics${CLAUDE_SKILL_DIR}/references/agent-selection.md — which research
agents to spawn for which signals${CLAUDE_SKILL_DIR}/references/breadboarding.md — rough-sketch
architecture before detail