Procurement Docs — Procurement Document Set Generation Pipeline

Workflow

Phase 1: Preparation (performed directly by the orchestrator)

1. Extract from user input:
   • Procurement target: Goods, software, services, construction, etc.
   • Procurement context: New introduction, replacement, expansion, etc.
   • Budget: Budget range or limit
   • Timeline: Desired delivery date, project schedule
   • Vendor candidates (optional): Vendors already under consideration
   • Existing documents (optional): Existing specifications, contract drafts
2. Create the _workspace/ directory in the project root
3. Organize the input and save to _workspace/00_input.md
4. Determine the execution mode based on the request scope

Phase 2: Team Assembly and Execution

Tasks 3a (evaluation) and 3b (contract) run in parallel.

Inter-team communication flow:

• definer completes → sends requirements/budget to comparator, priorities/criteria to evaluator, delivery/support terms to contract, must-have requirements/criteria to acceptance
• comparator completes → sends vendor info/comparison items to evaluator, license/clause highlights to contract
• contract completes → sends acceptance conditions/warranty to acceptance
• Orchestrator performs final cross-document consistency validation

Phase 3: Integration and Final Deliverables

1. Verify all files in _workspace/
2. Cross-validation:
   • All must-have requirements are reflected in acceptance criteria
   • Evaluation criteria weight totals equal 100%
   • Contract terms align with requirements/acceptance criteria
   • Vendor comparison items map to requirements
3. Generate procurement summary report at _workspace/06_procurement_summary.md
4. Report the final summary to the user

Execution Modes by Scope

Data Transfer Protocol

Error Handling

Test Scenarios

Normal Flow

Prompt: "Create a procurement document set for cloud server hosting services. Budget is $500K/year and I want to compare AWS, Azure, and GCP." Expected Results:

• Spec: Compute/storage/network requirements, SLA requirements
• Comparison: 3-provider feature/price/support comparison, TCO analysis, SWOT
• Evaluation: Technical 40% / Price 30% / Support 20% / Reliability 10% scoring
• Contract: SLA clauses, data sovereignty, termination terms, negotiation points
• Acceptance: Infrastructure deployment acceptance, performance testing, SLA compliance verification

Existing File Flow

Prompt: "I already have a spec. Just create vendor comparison and evaluation criteria." + spec file Expected Results:

• Existing spec copied to _workspace/01_requirements_spec.md
• Comparison + evaluation mode: comparator + evaluator deployed
• Vendor comparison and evaluation criteria generated from spec

Error Flow

Prompt: "I need to buy something but don't know what, maybe work laptops?" Expected Results:

• definer presents clarifying questions (use case, number of users, performance needs, etc.)
• Requirements derived from user responses
• Market price range presented if budget is undetermined
• Report notes "Requirements confirmation needed"

Agent Extension Skills