Use when this project needs Docs initialization, Docs structure maintenance, or Obsidian-friendly documentation without leaving the project's Docs system.
Use when an M or L level task in this project needs design clarification, option comparison, or user-approved solution shaping before planning or execution.
Use when a bug, test failure, compile failure, or unexpected behavior in this project needs root-cause analysis before any fix is attempted.
Use when a task in this project needs a clearer proposal or implementation plan while keeping all documents inside the project's Docs system.
Use when this project needs code review handling or structured feedback processing without turning every small task into a heavy mandatory gate.
Use when working inside this project and a stronger workflow layer is needed for planning, debugging, verification, or task decomposition without leaving the project's Docs system.
Use when about to say work is complete, fixed, or ready in this project and fresh verification evidence is required first.
L 级任务前期或需跨多份文档/模块时，并行 spawn 只读子智能体分别分析切片后由主智能体统一汇总。适合多文档分析、跨模块摸底、风险盘点。