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.
Datos de origen
- Repositorio
- protosphinx/sphinxstack
- Última actividad en el origen
- 29 de julio de 2026 a las 13:55
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 3
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Explorador de archivos
2 archivosMostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- 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
Ver en GitHub