太子向皇上呈报重要事项时的格式化模板——背景、分析、建议选项(附利弊)、请求裁决
Scanned 9/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill zouzhe --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Zouzhe?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-zouzhe)More formats (shields.io, HTML) on the badges page.
---
name: zouzhe
description: 太子向皇上呈报重要事项时的格式化模板——背景、分析、建议选项(附利弊)、请求裁决
---
# Skill: 奏折
> **适用 Agent**:太子(Lead)
> **加载时机**:太子需要向皇上呈报需裁决的重要事项时(三驳上奏、降级审批、重大技术决策等)
## 功能
将需要皇上裁决的事项格式化为结构清晰的奏折,确保皇上获得充分信息以做决策。
## 呈报格式选用指南
系统中有四种呈报格式,适用场景不同:
| 格式 | 使用场景 | 触发方 |
|------|---------|--------|
| 早朝奏报 | 会话开始时的系统状态全景汇报 | `/morning-court` |
| 退朝奏报 | 会话结束时的工作总结与交接 | `/tuichao` |
| 回奏报告 | 尚书省向太子汇报旨意执行结果 | 尚书省 report 模式 |
| **奏折** | **需皇上裁决的重大事项(含多选项与利弊分析)** | **太子或三省上奏时** |
一句话区分:早朝报"现在怎样",退朝报"做了什么",回奏报"执行结果",奏折报"请您定夺"。
## 奏折格式
```
📜 奏折
【事由】一句话概括
【紧急程度】P0/P1/P2
【来源】触发此奏折的原因(三驳上奏 / 降级审批 / 技术分歧 / ...)
一、背景
事项的来龙去脉,简明扼要
二、分析
关键发现与考量因素
三、选项
选项 A:{方案名}
· 描述:...
· 利:...
· 弊:...
· 支持方:{哪个 Agent 主张}
选项 B:{方案名}
· 描述:...
· 利:...
· 弊:...
· 支持方:{哪个 Agent 主张}
(可选)选项 C:...
四、太子建议
太子基于全局判断给出倾向性建议(可选,标注"仅供参考")
五、请求裁决
恳请皇上在以上选项中择一,或给出新指示
```
## 适用场景
| 场景 | 触发方 | 内容来源 |
|------|--------|---------|
| 三驳上奏 | 门下省第三次封驳 | 中书方案 + 门下驳议 |
| 降级审批 | 太子或尚书省 | 异常检测结果 + 降级方案 |
| 技术分歧 | 中书/门下争议 | 双方技术论点 |
| 资源冲突 | 尚书省 | 多旨意资源竞争情况 |
| 皇上主动询问 | 皇上 | 相关背景汇总 |
## 约束
1. 选项必须至少两个,给皇上真正的选择空间
2. 利弊分析须客观,不得偏袒任何一方
3. 太子建议为可选项,若给出须标注"仅供参考"
4. 奏折格式固定,各章节不得省略(无内容写"无")
5. 三驳上奏场景中,必须完整呈现中书与门下双方意见,不得删减
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.