What problem does it solve? Architects and product managers often spec residential real-estate products as generic CRUD apps, missing MLS fragmentation, listing status lifecycles, long-cycle lead nurture, and transaction-coordination deadlines — then rebuild later. This Skill front-loads that domain structure so the spec is right the first time. ## Core Features & Use Cases - Domain Vocabulary & Rules: Codifies MLS/IDX/RESO realities, listing status lifecycles, syndication canonical-source modeling, and agent-vs-brokerage data boundaries. - Naive-Build Checklist: Lists the five most common spec mistakes (single MLS schema, flat listings, checklist-only TC, short-funnel CRM, ignored ownership boundaries) so reviewers catch them early. - Must-Model Entities & Wedge Guidance: Seeds Listing, Lead, Transaction, and Property/MaintenanceRequest entity shapes, and identifies transaction-coordination as the high-pain, low-switching-cost wedge product. - Use Case: When speccing a lead-CRM for a brokerage, apply this Skill to model a 6–18 month nurture drip with stage and last-contact tracking instead of a short sales pipeline. ## Quick Start Apply the vertical-real-estate skill to seed the domain model and naive-build checklist before decomposing tasks for this real-estate product spec.
