veto-mechanism
Skill2 starsChanged 6 months agoMITView on GitHub
封驳机制,门下审议草案时触发审查、中书收到封驳时触发修订的双向制衡流程
In this repository26 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analysis-frameworkSkill
- architecture-overviewSkill
- audit-boundariesSkill
- biannianSkill
- communication-protocolsSkill
- dispatch-rulesSkill
- fault-toleranceSkill
- governance-coreSkill
- hanlinSkill
- intent-classificationSkill
- kejuSkill
- morning-courtSkill
- parallel-executionSkill
- permission-matrixSkill
- qijuzhuSkill
- redline-referenceSkill
- report-formatSkill
- review-coverageSkill
- shengzhiSkill
- special-directivesSkill
- team-bootstrapSkill
- ticket-formatSkill
- token-optimizationSkill
- tuichaoSkill
- zouzheSkill
The file
Files
Skill: 封驳机制
适用 Agent:中书省、门下省 加载时机:门下省审议草案时;中书省收到封驳时
封驳是门下省的核心权力,源自唐制"封还诏书,驳正违失"。
封驳流程
- 首次封驳:门下省退回草案,附驳议理由与修改建议
- 中书修订:中书省必须针对驳议逐条回应,修订后重新提交
- 二次封驳:若修订仍不满足,门下省再次封驳并升级理由
- 三驳上奏:连续三次封驳同一方案,自动上报皇上裁决(附双方意见摘要)
- 皇上裁决:皇上可选择——采纳中书方案 / 采纳门下意见 / 给出新指示
封驳输出格式
{ "type": "veto", "plan_id": "...", "round": 1, "rejection_reason": "...", "suggestions": ["..."] }约束
- 门下省有绝对封驳权,中书不得绕过
- 中书不得强行通过被驳方案,必须修订后重新提交
- 三驳上奏时,双方意见摘要须客观呈现,不得偏颇
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

