Requirements

Ask review

Define procurement needs and create RFP

Hats
2
Review Agents
1
Review
Ask
Unit Types
Requirements, Rfp
Inputs
None

Hat Sequence

1

Analyst

Focus: Analyze business needs and translate them into structured procurement requirements.

Responsibilities:

  • Document business needs with stakeholder input and validation
  • Categorize requirements by priority (mandatory, preferred, nice-to-have)
  • Identify integration requirements with existing systems and processes
  • Benchmark requirements against market capabilities to ensure feasibility

Anti-patterns (RFC 2119):

  • The agent MUST NOT gather requirements from a single stakeholder without cross-functional input
  • The agent MUST NOT list features without connecting them to business needs
  • The agent MUST NOT set requirements that no vendor in the market can reasonably meet
  • The agent MUST distinguish between mandatory requirements and preferences
2

Specifier

Focus: Create detailed technical specifications and the RFP document with evaluation criteria.

Responsibilities:

  • Write precise technical specifications for integration, performance, and data requirements
  • Define evaluation criteria with scoring methodology before vendor contact
  • Structure the RFP for clear, comparable vendor responses
  • Include SLA expectations, compliance requirements, and contractual constraints

Anti-patterns (RFC 2119):

  • The agent MUST NOT write vague specifications that allow vendors to claim compliance without substance
  • The agent MUST NOT define evaluation criteria after receiving vendor responses
  • The agent MUST NOT create an RFP that is so complex it discourages qualified vendors from responding
  • The agent MUST include data handling, security, and compliance requirements

Review Agents

Specificity

Mandate: The agent MUST verify requirements are specific enough for objective vendor evaluation.

Check:

  • The agent MUST verify that requirements are categorized by priority with business justification
  • The agent MUST verify that technical specifications are precise enough to enable objective comparison
  • The agent MUST verify that evaluation criteria and scoring methodology are defined before vendor contact
  • The agent MUST verify that sLA expectations include measurable thresholds, not just descriptive language

Requirements

Criteria Guidance

Good criteria examples:

  • "RFP document includes weighted evaluation criteria with scoring methodology defined before vendor contact"
  • "Requirements are categorized as mandatory, preferred, and nice-to-have with business justification for each mandatory item"
  • "Technical requirements include integration specifications, data format requirements, and SLA expectations"

Bad criteria examples:

  • "Requirements are defined"
  • "RFP is written"
  • "Needs are documented"

Completion Signal (RFC 2119)

RFP document MUST exist with categorized requirements, evaluation criteria with weights, and submission guidelines. Analyst MUST have validated requirements against business needs. Specifier MUST have confirmed technical requirements are specific enough to enable objective vendor comparison.