Hire an AI project debt reserve and payment reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A reserve roll-forward with opening balance, draws, required balance, top-up needed and what is still unfunded
• A payment waterfall that allocates the cash to senior payments, the reserve and junior payments in order
• A tie between the waterfall's reserve deposit and the roll-forward, with any difference explained
• A covenant headroom line for each test period, only when a distribution review needs it
• What changed since the last review, a record for the next one, MISSING lines and any checks that could not run

How it does the job well

• Start from the user problem and the evidence for it, then the solution.
• Write decisions down with the reason and the options you rejected.
• Keep scope small enough to ship and learn. Name what is out of scope.
• Define how success will be measured before building.

Mistakes it avoids

• Treating opinions or one loud request as proven demand.
• Specs that skip edge cases, error states or dependencies.
• Roadmaps with dates but no owners or confidence levels.

What a good result looks like

An example, not your task: The next loan payment changes, so the reserve you must hold changes with it.

• Changed since last review. Each requirement, draw, payment or priority term that moved, with old and new value and source date.
• outputs/step-1-debt-reserve-rollforward-builder.md. Opening reserve, approved draw, required balance, top-up needed and any unfunded amount, with the ending balance tied to its parts.
• outputs/step-2-project-payment-waterfall-builder.md. The cash allocated to senior payments, the reserve and junior payments in order, what is left over, and every unpaid amount.
• Reserve tie. The waterfall's reserve deposit set against the roll-forward deposit, with any difference explained, not plugged.
• Covenant headroom line. Signed cash headroom for each test period on the contract's own definition. Only when a distribution review needs it.
• Record and MISSING lines. The record for the next review, every gap with the line it stops, and CHECKS MISSED.

How the work is checked

• The reserve top-up appears once, in the roll-forward and in the waterfall, not twice.
• Ending reserve equals opening reserve plus deposits less draws and releases.
• Cash is allocated in the contract's order. Each level is capped at the cash left and the amount due. Existing reserve cash is not treated as new cash.
• The waterfall's reserve deposit ties to the roll-forward deposit, or the difference is explained and recorded.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Compares with the last review. Reads the saved record if it belongs to this project and reserve account, or sets a first baseline. It compares the requirement window, authorized draws, deposits, payment priorities and open test gates. If nothing changed and no review is due, it says so and stops.
• Builds the reserve roll-forward. Runs the Debt reserve rollforward builder step. It applies only the authorized draw, capped at the opening reserve, works out the required balance from the next payments, and funds a shortfall only from cash that is really available. The ending reserve ties to opening plus deposits less draws and releases.
• Runs the payment waterfall. Runs the Project payment waterfall builder step. It allocates the same cash to senior payments, the reserve and junior payments in the order the contract sets, capping each at the cash left and the amount due. It ties the reserve deposit to the roll-forward and records any difference.
• Tests a distribution gate only if needed. If owners request a distribution and a signed debt-service test applies, it runs the Loan covenant cash coverage checker on the contract's own definition and periods. It shows signed cash headroom for each period and keeps any weak period visible.
• Checks and saves. Tests the result against the acceptance rules, retries the affected calculation at most twice, then writes the dated files, which steps ran or were skipped, and the new record. It keeps the old record.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id project-reserve-evidence-reviewer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/project-reserve-evidence-reviewer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The project cash left after operating obligations for the period (from your cash records)
• The senior and junior loan payments due, with dates (from the loan agreements)
• The reserve rule, meaning how many months of payments it must cover and what may fill it (from the loan agreement)
• The reserve balance and the draws that were approved (from the reserve account statement and approvals)
• The payment priority clause (from the contract)
• A signed debt-service test, with cash and payments for three periods (optional, only if a distribution is requested)
• The last review's record and the earlier source versions (optional, needed to show what changed). The record is one small JSON file the agent writes each run; in plain chat it prints the record for you to paste next time

Helpful context (optional)

• The debt schedule with senior and junior payment dates.
• Lender approvals for any draw or release.
• A named person who owns the loan reporting and will check the order and the amounts.

Tools and access

• A spreadsheet engine and file-capable AI: Builds linked schedules for the reserve and the waterfall, and saves the record file for next time. In plain chat it returns the same tables as text.
• Your loan agreements and reserve account statements: The reserve rule, the payment order and the balances are contract and bank facts. Quote them, never guess them.
• A spreadsheet engine and file-capable AI: Builds a workbook with inputs, formulas and checks you can click into. In plain chat it returns the same tables as text and says no workbook was made.
• Claude, ChatGPT or Gemini: Any of them can build the headroom table in a chat.
• An AI that can make spreadsheet files: It can build the workbook, recalculate it and check that it reopens.
• Node.js 20 or later (optional): Runs the small script that comes with the skill, for a second check of the numbers.

Functions and deliverables

• Project debt reserve and payment reviewer: Check debt reserves and payment order. See required top-ups, unpaid items and rules still to verify before releasing cash.
  • A reserve roll-forward with opening balance, draws, required balance, top-up needed and what is still unfunded
  • A payment waterfall that allocates the cash to senior payments, the reserve and junior payments in order
  • A tie between the waterfall's reserve deposit and the roll-forward, with any difference explained
  • A covenant headroom line for each test period, only when a distribution review needs it
  • What changed since the last review, a record for the next one, MISSING lines and any checks that could not run
• Project debt reserve payment checker: Share project cash, debt schedules and payment rules. Get a reserve balance check, ordered payment split and unfunded obligations.
  • A reserve rollforward: requirement, approved draws, top-up need and closing balance
  • A payment waterfall: cash paid to senior debt, the reserve and junior debt, in your loan's order
  • A tie between the reserve deposit in the waterfall and the rollforward, with any difference recorded
  • A list of every service or reserve amount that stays unpaid
  • Every MISSING input and any check that could not run
• Loan covenant cash coverage checker: Share contract terms and cash by period. Check coverage ratios and the cushion above each required payment.
  • A schedule for each period: qualifying cash, debt service, cash required and headroom
  • The smallest headroom and the period it falls in
  • The cash gap, if any period is short
  • A ratio for each period that ties back to the same table
  • A list of missing facts and checks it could not run
  • A small workbook with the same schedule, if your AI can make files
• Debt payment reserve checker: Share reserve balances and loan terms. Check required funding, permitted draws and any reserve shortfall.
  • The reserve balance the loan requires
  • The draw applied, capped at what the account holds
  • The top-up deposit, limited to the cash you can put in
  • Any excess that could be released, shown as a scenario only
  • The ending reserve balance and any gap left unfunded
  • A list of missing facts and checks that could not run
  • A small workbook with the same sums, if your AI can make files
• Product context file writer: Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.
  • A product marketing context file
  • A summary of what the file already holds
  • A change log of updates
  • Gaps you still need to fill
  Source: Corey Haines.

Tasks you can use it for

• The next loan payment changes, so the reserve you must hold changes with it.
• A lender approves a draw on the reserve.
• Owners ask for a distribution and you need to show the cash goes through the waterfall first.
• A contract change alters who is paid first.

Limits to check before starting

• You only need to test a signed covenant, such as cash cover each period. Use the Loan covenant cash cover reviewer. This agent runs that test only when a distribution is requested.
• You need to build the loan schedule and the cover ratios first. Use the Project cash and debt coverage reviewer.
• Your reserve is a plain cash balance with no payment priority. A simple balance check is enough, and the Cash settlement forecast reviewer covers daily cash.
• You want to know if a payout is legally allowed. It reads the order and gates you supply. It gives no legal opinion.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add this agent to Claude, ChatGPT or Gemini, with the two pieces it uses. They are the Project debt reserve payment checker workflow and the Loan covenant cash coverage checker skill. An AI that reads files works best. In plain chat it still works, but it cannot save files.
• Say if this is the first run. If not, paste last time's record. Then attach the debt schedule, the reserve statement, the payment priority clause and the cash records for the period.
• Name the payment order once, in your own words. Check that the waterfall follows it and that existing reserve cash is not counted as new cash.
• Check that the reserve top-up appears once, and that the waterfall's reserve deposit matches the roll-forward. Any unpaid senior, reserve or junior amount should show on its own line.
• Fix every MISSING line and run it again when a requirement, a draw, a payment date or the order changes. Adding it sets up no schedule.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/project-reserve-evidence-reviewer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.