Skip to content
Back to skills

Reconcile Subcontractor Delivery To Obligations

ASecurity

Compare subcontractor deliverables with versioned obligations and acceptance evidence. Use when a status report says complete but contractual proof is incomplete.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 26, 2026
ai-agents

Security analysis

A100/100

Scanned September 26, 2026

npx -y skills add alisonjieli-png/loop-engine --skill reconcile-subcontractor-delivery-to-obligations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Reconcile Subcontractor Delivery To Obligations?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Reconcile Subcontractor Delivery To Obligations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/alisonjieli-png-reconcile-subcontractor-delivery-to-obligations/badge)](https://www.skillsdirectory.com/skills/alisonjieli-png-reconcile-subcontractor-delivery-to-obligations)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: reconcile-subcontractor-delivery-to-obligations
description: Compare subcontractor deliverables with versioned obligations and acceptance evidence. Use when a status report says complete but contractual proof is incomplete.
---

# Reconcile subcontractor delivery to obligations

## When to use

Use for one subcontractor, agreement version and reporting cutoff. Evaluate evidence for obligations; do not accept work or change commercial terms.

## Inputs

- Executed agreement and approved changes, named deliverables, due dates, acceptance criteria and party responsibilities.
- Submitted artifacts, inspection or test results, acceptance decisions, issue records and the cutoff time.
- Supplied waiver and cure rules, including who may approve them.

## Procedure

1. Build an obligation register from the effective agreement. Separate deliverables, process duties, dates and optional promises; preserve each clause reference.
2. Map each submitted artifact to an obligation and verify identity, revision, recipient and evidence date. A vendor status statement is a claim, not an acceptance decision.
3. Apply each explicit acceptance criterion to the artifact or test evidence. Distinguish submitted, inspected, accepted, rejected and undecided.
4. Show overdue or disputed obligations against the agreed timing rule. Keep an unapproved change request outside the active obligations.
5. Prepare a gap packet naming evidence needed, responsible party and authorized decision maker, without asserting breach or payment consequences beyond the supplied agreement.

## Completion check

Return obligation-to-evidence links, effective agreement version, accepted and open states, unresolved changes, timing basis and next decision owner. Every complete state needs its matching acceptance evidence.

## Known-wrong case and stop

A subcontractor uploads a test report but the agreement requires a signed inspection result; marking the deliverable accepted from the upload alone is wrong. Hold legal or payment conclusions when the agreement, amendment status or acceptance authority is unclear. Do not approve, reject, pay or notify the subcontractor.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.