define-procurement-requirements
Turn a purchasing need into testable outcome, service, security, and operating requirements. Use when a team must brief suppliers without prescribing an unexamined solution.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- define-procurement-requirements
- category
- write
- description
- Turn a purchasing need into testable outcome, service, security, and operating requirements. Use when a team must brief suppliers without prescribing an unexamined solution.
# define-procurement-requirements
## Procedure
1. Name the business outcome, users, decision owner, budget range, timeline, and current-state problem.
2. Interview operators, users, finance, security, accessibility, legal, and downstream owners as relevant.
3. Separate mandatory constraints from preferences and optional capabilities.
4. Write each requirement as an observable outcome with an acceptance method.
5. Cover implementation, integration, data, support, continuity, exit, reporting, and total-cost needs.
6. Record assumptions, dependencies, exclusions, evidence sources, and unresolved questions.
7. Test the draft against at least two plausible solutions and remove vendor-shaped wording.
8. Baseline the approved requirements and define how changes will be controlled.
## Guardrails
- Do not copy an incumbent product specification and call it a neutral requirement.
- Route legal, regulatory, accounting, and security conclusions to qualified owners.
- Keep confidential budgets, architecture, and personal data within the approved audience.
## Done
- A requirements brief links each need to an owner, priority, and acceptance method
- Mandatory, preferred, excluded, and unresolved items are visibly separated
- Stakeholder review and baseline approval are recorded
在 GitHub 查看