manage-procurement

Manage Procurement

Use this skill for purchase order lookup, unified procurement request lookup, pending procurement approvals, and safe request approval or rejection.

Do not use it for bill approval/payment, card transaction cleanup, reimbursements, vendor document upload, accounting recoding, or contract edits.

Rules

• Use purchase_orders for PO lookup/detail. Use requests for unified request search, request detail, pending approval queue, approval, and rejection.
• Keep identifiers labeled. purchase_order_id, request_uuid / unified_request_id, and spend_request_id are distinct. Approval acts on the unified request UUID, not the PO UUID.
• Use --agent for responses you need to parse.
• Use --json for search filters. The CLI validates unknown JSON keys and enum values, so use --dry_run --json ... when checking payload shape.
• Use exact pagination cursors returned by the API. Do not trim or rewrite them.
• Procurement schemas do not return deep-link URLs. Present returned identifiers and statuses instead of inventing links.
• Do not approve or reject without first showing details and confirming the user's intent.
• For rejection, include the user-supplied or user-accepted reason in --thoughts.
• PO amount fields are numeric currency units with a currency code. Display them directly; do not apply cents conversion.

Workflow

1. Search POs first when the user gives a PO number, vendor, or procurement record:

   ramp purchase_orders search --json '{"rationale":"Searching purchase orders by vendor or PO number","filters":{"search":"Figma"},"limit":10}' --agent
   

   If a known PO number is not returned, the spend request may still be pending and the PO may not be issued yet. Search unified requests scoped to purchase orders:

   ramp requests search --json '{"rationale":"Searching purchase order requests before PO issuance","filters":{"search":"Figma","unified_spend_request_types":["PURCHASE_ORDER"]},"limit":10}' --agent