Menu

Individual skill

reflect-3-procureops-controls

0upvotes

Solve ProcureOps control, reconciliation, sourcing-readiness, AP-close, change-control, and AP-release JSON tasks using task inputs plus the remote ProcureOps API.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_006/reflect-3/reflect-3_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Reflect-3 ProcureOps Controls

Use this skill when a task asks for a JSON control file or reconciliation packet from ProcureOps records.

## Operating Rules

- Read the task prompt, answer template, and task-local payloads first. The answer template is the output contract: preserve required keys, enum values, ordering rules, nullability, rounding, and JSON-only output.
- Use the ProcureOps API as the system of record for operational entities: programs, suppliers, items, requisitions, approvals, contracts, purchase orders, receipts, invoices, payments, budgets, and vendor-risk events.
- Treat local payloads as authoritative for task scope, requested as-of/review dates, target IDs, local-only registers, alias notes, and business-control assumptions. Do not broaden the scope beyond memo-named anchors or target IDs unless the prompt explicitly asks for a wider search.
- If a task-level environment note conflicts with a prompt example URL, follow the environment note or runner-provided base URL.
- Return only the JSON object requested. Do not add prose, citations, diagnostics, or extra fields.

## Source Precedence
Back to top