create-an-approval-workflow
Design an approval path with proportionate authority, evidence, separation, and escalation. Use when a recurring decision is delayed, inconsistent, overcontrolled, or weakly governed.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- create-an-approval-workflow
- category
- start
- description
- Design an approval path with proportionate authority, evidence, separation, and escalation. Use when a recurring decision is delayed, inconsistent, overcontrolled, or weakly governed.
# create-an-approval-workflow
## Procedure
1. Define the decision, risk, frequency, value bands, policy source, and accountable owner.
2. Map requester, reviewer, approver, executor, recorder, and exception roles.
3. Specify required evidence, thresholds, delegated authority, and separation-of-duty rules.
4. Remove duplicate reviews that do not change the decision or reduce risk.
5. Design normal, urgent, rejected, returned, delegated, expired, and unavailable-approver paths.
6. Add timestamps, rationale, version, attachments, and immutable outcome history.
7. Test low-risk, high-risk, incomplete, conflict, and emergency cases.
8. Publish service expectations, escalation, review cadence, and control owner.
## Guardrails
- Do not allow requesters to approve their own consequential transactions.
- Never use automation to exceed delegated authority or suppress exceptions.
- Minimize sensitive evidence and restrict it to authorized reviewers.
## Done
- An approval plan and workflow map name roles, thresholds, evidence, states, and escalations
- Scenario tests verify authority, separation, exception, and audit behavior
- The approved workflow has an owner, service target, and review record
在 GitHub 查看