Activate when: a real estate agent is running a listing/transaction and must not skip disclosure, agency, and fair-housing steps; 'what do I need to disclose...
Coding
Real Estate — Pricing & Price-Reduction Decision
Try itActivate when: a listing isn't selling and the agent must decide list price or a price reduction; 'should we drop the price', 'how much and when', days-on-ma...
What it does
Activate when: a listing isn't selling and the agent must decide list price or a price reduction; 'should we drop the price', 'how much and when', days-on-market rising, showings without offers. Do NOT activate when: the property is priced right and getting offers (no decision). More: deciqai.com/c/realtor-price-reduction-decision
The skill document
Real Estate — Pricing & Price-Reduction Decision
Industry front door for decision-tree. Adds domain triggers, example, packs. Parent Process unchanged. Not appraisal advice.
Activate when: setting a list price; a listing stalls (DOM up, showings without offers); deciding reduction timing/size; managing seller expectations. Do NOT activate when: priced correctly with active offers.
Why this variant
The parent decision-tree maps sequential choices under uncertainty. Pricing and reductions are a decision tree: hold vs reduce, by how much, when — against showing/offer feedback, carrying cost, and market trend, rolling back to expected net proceeds and time-to-sell.
Domain inputs → the tree
- Read the signals: showings-to-offer ratio, DOM vs market median, feedback themes, comparable adjustments.
- Branch: hold (if fresh/undersampled), small reduction (nudge into a search bracket), meaningful reduction (reset if far off).
- Value the branches by expected net proceeds × probability × carrying cost of extra DOM. Gate: reductions below a portal price bracket (e.g. $505k→$499k) capture a new buyer pool — size to brackets, not round guesses.
Worked example
30 showings, no offers, DOM 2× median, feedback "overpriced vs the one down the street." → Tree: this is a pricing (not marketing/condition) problem; a token cut won't fix a bracket miss. Reduce into the correct search bracket in one decisive move; slow drip prolongs DOM and signals weakness.
Packs
- Solo agent: showings-to-offer + DOM decision card; bracket-aware reduction sizing.
- Team: weekly stale-listing review triggering the decision.
Red flags
- Blaming marketing when the data says price.
- Tiny drip reductions that prolong DOM.
- Reductions not aligned to portal search brackets.
Verification
- Showing/offer + DOM signals reviewed vs comps
- Problem diagnosed (price vs condition vs marketing)
- Reduction sized to search brackets, not round numbers
- Expected net proceeds vs carrying cost weighed
Part of deciqAI Knowledge Skills — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/c/realtor-price-reduction-decision · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.
Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/realtor-price-reduction-decision.json
Related skills
Activate when: user says 'the market is telling us X', 'valuation has dropped/risen so we should act', 'everyone is selling/buying so I should too', or is ma...
Property search, screening, comparison, map enrichment, profile memory, watched listings, and listing publishing orchestration. Use when the user asks to ren...
Design and evaluate A/B tests for different price points, discount levels, and bundle combinations to find the highest-converting offer structure.
Return exact real estate listing script matches from the configured knowledge base.
Track product prices across time and stores, alert on price drops, and predict the best time to buy.