loan-pipeline
Design loan origination pipeline tracking and status workflow specifications for mortgage brokers and lenders. Use when automating loan status tracking, milestone notifications, or pipeline reporting for a mortgage operation.
What this skill does
# Loan Pipeline Tracking Workflow Design Design the complete loan origination pipeline tracking system, from application intake through funding, with automated status updates, borrower and agent notifications, pipeline reporting, and exception queue management. ## Scope Confirmation Confirm which pipeline components are in scope: - [ ] Application intake and channel capture - [ ] Milestone status tracking - [ ] Automated notifications (borrower, agent, real estate agent, settlement agent) - [ ] Pipeline dashboard and reporting - [ ] Exception queue (stuck loans, missing conditions) - [ ] LOS integration for status sync --- ## Component 1: Application Intake and Channel Capture **Origination channels to track:** | Channel | Source System | Data Capture Method | Initial Status | |---------|--------------|---------------------|---------------| | Point-of-Sale (POS) system | [Blend, SimpleNexus, BeSmartee, etc.] | API integration | Application submitted | | LOS — manual entry | [Encompass, BytePro, Calyx, etc.] | LOS webhook or polling | Application in progress | | Referred (paper/email) | Manual upload | Staff entry in LOS | Application pending | | Wholesale broker submission | Broker portal | API or file import | Broker submitted | **Required data at intake (minimum for 6-piece TRID application definition):** | Field | TRID Required? | Source | |-------|---------------|--------| | Borrower legal name | Yes | Borrower entry | | Borrower SSN | Yes | Borrower entry | | Property address | Yes | Borrower entry | | Estimated property value | Yes | Borrower entry | | Loan amount | Yes | Borrower entry | | Income (used for qualification) | Yes | Borrower entry | | Borrower DOB | No | Borrower entry | | Email and phone | No | Borrower entry | | Co-borrower information | No | If applicable | | Loan purpose (purchase/refi) | No | Borrower selection | | Property type | No | Borrower selection | | Loan program | No | LO selection | **Application date rule (TRID):** Application is "received" for TRID purposes when all 6 required pieces are collected. The LE 3-business-day clock starts at application receipt. System must: - Flag the exact date/time all 6 fields are populated - Store this as the official `application_received_date` - Calculate `le_due_date` = application_received_date + 3 business days (business day = Monday–Friday excluding federal holidays) - Alert if LE has not been issued by day 2 --- ## Component 2: Milestone Status Tracking **Standard pipeline milestones:** | # | Milestone | Description | Preceding Milestone | Common SLA | |---|-----------|-------------|--------------------|-| | 1 | Application received | All 6 TRID pieces collected; application date set | — | Day 0 | | 2 | Pre-approval issued | Tri-merge credit pulled; DU/LP run; pre-approval letter generated | Application received | 1–2 business days | | 3 | Under contract | Purchase agreement received (purchase only) | Pre-approval | Borrower-dependent | | 4 | Disclosures sent | LE and intent to proceed received | Application received | Day 3 (LE due) | | 5 | Intent to proceed received | Borrower signed intent to proceed | Disclosures sent | Varies | | 6 | Processing — active | Loan package submitted to processor; conditions collection underway | Intent to proceed | Day 5–7 | | 7 | Appraisal ordered | Appraisal ordered through AMC | Processing active | Day 5–7 | | 8 | Appraisal received | Appraisal report received and reviewed | Appraisal ordered | 5–14 days from order | | 9 | Title ordered | Title search ordered | Processing active | Day 5–7 | | 10 | Title received | Title commitment received and reviewed | Title ordered | 5–10 days from order | | 11 | Submitted to underwriting | Complete loan package submitted to UW | Processing active | Day 10–15 | | 12 | Conditional approval | UW issues conditional approval with conditions list | Submitted to UW | 1–5 business days | | 13 | Conditions received | All UW conditions collected and submitted | Conditional approval | Varies | | 14 | Clear to close (CTC) | UW clears all conditions; loan approved | Conditions received | 1–2 business days | | 15 | CD issued | Closing Disclosure issued to borrower | CTC | 3 business days before closing | | 16 | Closing scheduled | Closing date/time/location confirmed | CD issued | — | | 17 | Closing | Loan documents signed | Closing scheduled | — | | 18 | Funding | Loan funded by lender; disbursement complete | Closing | 1–3 business days | | 19 | Post-closing complete | Post-close package reviewed; shipped to investor | Funding | 1–5 business days | **Status change triggers:** Each milestone status change is triggered by one of: - **LOS event** (automated): LOS webhook fires when LOS status changes - **Processor/UW action** (semi-automated): Staff changes status in pipeline system after completing an action - **System detection** (automated): Document received, time elapsed, condition cleared - **Manual** (staff entry): Phone call confirmed, verbal acknowledgment received Audit all status changes: record actor (staff member or system), timestamp, previous status, new status. --- ## Component 3: Automated Milestone Notifications **Notification recipients:** | Recipient | Relationship | Channel | Content Level | |-----------|-------------|---------|--------------| | Borrower | Primary | Email + SMS | Consumer-friendly, no jargon | | Co-borrower | Primary | Email + SMS | Same as borrower | | Loan officer | Internal | Email + in-app | Detailed milestone + next action | | Processor | Internal | In-app task | Action items | | Real estate agent (purchase) | External | Email | Brief status; no financial details | | Listing agent (purchase) | External | Email | Brief status; no financial details | | Settlement agent / title company | External | Email | Closing-relevant milestones only | **Borrower notification triggers and content:** | Milestone | Notification Sent | Subject Line | Key Content | |-----------|------------------|-------------|-------------| | Application received | Immediate | "Your application is received — here's what happens next" | Checklist of what they'll need to provide; timeline overview | | Disclosures sent | Immediate | "Your Loan Estimate is ready — please review" | LE summary; link to e-sign intent to proceed; LE explanation | | Appraisal ordered | Same day | "Your appraisal has been ordered" | Expected timeline; what appraiser access they need to provide | | Appraisal received | Same day | "Your appraisal is complete" | Result (value confirms/exceeds/below purchase price); next steps | | Conditional approval | Same day | "You're approved — we need a few more items" | Plain-English list of outstanding conditions; how to submit; priority | | CTC | Immediate | "You're clear to close!" | Congratulations; what to expect at closing; wire fraud warning | | CD issued | Immediate | "Your Closing Disclosure is ready — please review" | CD summary; 3-business-day window explained; final cash to close | | Closing confirmed | Confirmation | "Closing confirmed for [date/time/location]" | Location, what to bring (ID, cashier's check if applicable), wire instructions warning | | Funded | Same day | "Your loan is funded — congratulations!" | Next steps: first payment date, servicer information | --- ## Component 4: Pipeline Dashboard and Reporting **Pipeline dashboard views:** **Loan officer view:** - My pipeline: all active loans assigned to me - Columns: borrower name, loan amount, program, loan purpose, current milestone, days in current milestone, CD due date, closing date, red flags - Filters: milestone, loan type, closing date range **Manager/branch view:** - Full pipeline: all active loans by LO - Pull-through metrics: application → CTC → funded rates - Days-to-close by LO, loan type, lead source - Loans at risk (closing within 7 days + not CTC) - Fallout analysis: what stage are withdrawn/denied loans falling out? **Pipeline reports:** | Report | Frequency | Recipients |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.