plugins/lobbi-mortgage-domain/skills/disclosure-generator/SKILL.md
Generate TRID Loan Estimate and Closing Disclosure timing and accuracy specifications. Use when designing the disclosure workflow for a mortgage lender or broker to ensure TRID compliance.
npx skillsauth add markus41/claude plugins/lobbi-mortgage-domain/skills/disclosure-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design the Loan Estimate and Closing Disclosure workflow to ensure full TRID (TILA-RESPA Integrated Disclosure) compliance. TRID violations are among the most commonly cited mortgage regulatory deficiencies — this specification covers timing, tolerance buckets, changed circumstance procedures, and recordkeeping requirements.
TRID (implemented under Reg Z § 1026.37-38 and Reg X § 1024.7) applies to:
Consists of two required disclosures:
The LE clock starts when the borrower provides these 6 pieces of information:
Important: The creditor cannot require additional information beyond these 6 before providing a Loan Estimate. Pre-qualification worksheets or additional documentation can be requested in parallel, but the 6-piece receipt date is the application date.
System requirement: Log the exact date and time each of the 6 fields is captured. When all 6 are present, set application_received_date. This is the date the LE clock starts.
LE deadline calculator:
application_received_date = first date all 6 triggers are present
le_due_date = application_received_date + 3 business days
(Count: skip Sundays and federal public holidays; include Saturdays if office open)
If mailing:
le_mail_by_date = application_received_date + 3 business days
le_constructive_receipt = le_mail_by_date + 3 more business days
TRID limits how much certain fees can change between the LE and the CD.
Zero tolerance (cannot increase):
10% tolerance (aggregate tolerance — total increase cannot exceed 10% of LE total):
No tolerance (can change without limit):
Tolerance cure process: If at CD, any zero-tolerance or 10%-bucket fee exceeds tolerance:
A valid changed circumstance allows re-disclosure of a revised LE and resets the tolerance comparison baseline.
Valid changed circumstance categories:
| Category | Examples | Documentation Required | |---------|---------|----------------------| | Extraordinary event | Natural disaster affecting property; market disruption | News documentation, loss adjuster report | | Information relied upon changes | Appraisal comes in different from estimate; title search reveals lien; income different from stated | Revised information + explanation of how it changed the fee | | New information on borrower or property | Borrower adds or removes co-borrower; property use differs from disclosed | Written explanation | | Interest rate locked | Fees tied to rate lock that changes when rate is locked | Lock confirmation | | Borrower-requested change | Program change, loan amount change, property address change | Written or documented borrower request | | Expiration of original LE | Borrower does not express intent to proceed within 10 business days | Log of LE delivery date and non-response |
Changed circumstance documentation requirement:
Revised LE timing after changed circumstance:
CD delivery compliance checklist:
CD receipt date matrix:
| Delivery Method | Assumed Receipt | 3-Business-Day Clock Starts | |----------------|----------------|--------------------------| | In person or electronic (with E-SIGN consent) | Day of delivery | Day after delivery | | U.S. mail | 3 business days after mailing | Day after assumed receipt (6 days total) |
Example:
Actual calculation: Count back from consummation date. Day 1 = business day before consummation, Day 2 = business day before Day 1, Day 3 = business day before Day 2. CD must be received on or before Day 3.
If the CD is reissued with certain changes after delivery, the 3-business-day waiting period resets.
| Change | New 3-Day Wait Required? | |--------|--------------------------| | APR increases by more than 1/8 of 1% (1/4% for irregulars) | Yes | | Loan product changes (e.g., fixed to ARM) | Yes | | Prepayment penalty added | Yes | | Decrease in APR | No (borrower benefit — no re-wait required) | | Non-triggering fee changes (e.g., increased cash to close not due to above) | No |
Practical implication for workflow:
At CD stage, compare each fee against the LE baseline:
| Step | Action | |------|--------| | 1 | Pull all fees from the final LE (or latest revised LE for each fee category) | | 2 | Compare each fee on the CD to the LE | | 3 | Apply tolerance bucket rules (zero / 10% / no tolerance) | | 4 | Calculate aggregate 10% bucket variance | | 5 | Identify any tolerance violations | | 6 | Calculate cure amount for each violation | | 7 | Document cure in CD (or confirm separate cure payment timing) |
Cure documentation:
In certain cases, a corrected CD must be provided after closing:
| Document | Retention Period | Required Content | |---------|-----------------|-----------------| | Initial Loan Estimate | 3 years from consummation | LE as delivered; evidence of delivery; application date | | All revised LEs | 3 years from consummation | Revised LE; changed circumstance documentation | | Intent to proceed | 3 years from consummation | Date, method, staff member (if verbal) | | Closing Disclosure | 5 years from consummation | CD as delivered; evidence of 3-day receipt | | All revised CDs | 5 years from consummation | Revised CD; reason for revision; delivery evidence | | Tolerance cure documentation | 3 years | Amount, date, method | | Changed circumstance file | 3 years | Date of event, description, fees affected |
Delivery confirmation requirements:
Deliver two artifacts:
TRID Disclosure Workflow Specification — Process flows for LE issuance, changed circumstance handling, CD issuance, and post-consummation corrections; with decision trees for tolerance analysis and re-disclosure triggers
Tolerance Matrix — Complete fee tolerance table with examples for each bucket; changed circumstance documentation template; CD vs. LE comparison checklist
tools
Build Teams-native agents with the Teams SDK (formerly Teams AI Library v2) — App class, activity routing, adaptive cards, streaming, AI-generated labels, feedback, message extensions, Teams-as-MCP-server, and the bring-your-own-AI pattern with Agent Framework.
tools
Run agents on Microsoft Foundry (formerly Azure AI Foundry) Agent Service — prompt agents vs hosted agents, threads/runs and the Responses API, built-in tools (Bing grounding, code interpreter, file search, MCP, OpenAPI, A2A), connected agents, Entra agent identity, SDKs, and observability/evaluations.
tools
Build and host custom engine agents with the Microsoft 365 Agents SDK — AgentApplication, the Activity protocol, channel reach via Azure Bot Service, hosting Agent Framework or Semantic Kernel engines, and the Agents Toolkit/Playground workflow. Successor to the Bot Framework SDK.
tools
Design, govern, and extend Microsoft Copilot Studio agents — topics, generative orchestration, knowledge, tools and MCP, agent flows, autonomous triggers, publishing channels, Copilot Credits pricing, and solution-based ALM on Power Platform.