@rubytech/create-maxy-code 0.1.23 → 0.1.24

package/payload/premium-plugins/real-agency/plugins/estate-business/skills/month-end-close/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: month-end-close
+description: "Run the monthly close, reconcile completions against fees received, compute the commission run, surface variances, and produce the pack for the accountant. Triggers when the operator says 'close out <month>', 'close <month>', 'month end', 'do my commission', 'commission run', 'reconcile <month>', 'ready for the accountant', 'what did I do last month'. Also fires automatically on the first working day of the month."
+---
+
+# Month-end close
+
+The master workflow owned by the compliance specialist. Compresses a half-day to a full day of month-end admin into a 20-minute review. Produces a clean pack ready for the accountant.
+
+This is the workflow that earns back the subscription. A solo agent who would otherwise spend half a Saturday on this should feel that Real Agent paid for itself in the time saved on month-end alone.
+
+## Inputs
+
+- The period to close (typically the previous calendar month).
+- The customisation profile.
+
+The workflow reads the rest from connectors.
+
+## Architecture principles encoded here
+
+- Read before write. The workflow opens by reading completions, fees received, the commission splits table, and the prior close pack. It writes nothing until the operator approves each individual stage.
+- Stage, don't send. Journal entries, payment batches, accountant emails are all staged. Approval is per item.
+- One screen of output. The pack is five sections, each summarised on one screen. Drill-down is available on request.
+- Cite the source. Every line in the reconciliation cites the completion record and the bank transaction it matched against. Every commission line cites the splits table and the deal.
+- Teach the profile. Categorisation conventions, variance tolerance, narrative tone all feed back through `profile-writer`.
+- Reversible. No transfers are initiated. Journal postings require explicit approval. The accountant pack is drafted and queued; nothing sends without the operator.
+
+## Output shape
+
+Five sections, in this order.
+
+1. **Completions.** Every property that exchanged or completed in the period: address, vendor, buyer, fee value, fee structure (sole, multi, withdrawal, sliding), completion date, expected receipt date. Anything that exchanged but is still awaiting completion is highlighted.
+2. **Reconciliation.** Fees expected versus fees received, matched on completion date and amount. Three flag categories: matched, pending (expected but not yet received with age), variance (received differs from expected: fee adjustment, referral deduction, fee dispute). Variances get a one-line cause and a draft email to the accountant or the solicitor if appropriate. Built by `period-reconciler`.
+3. **Commission run.** For office tiers with multiple agents: each agent's earned commission for the period, referral fees passed through, franchise levies deducted, pre-agreed adjustments. Built by `commission-calculator`. Presented as a payable schedule with totals.
+4. **Pipeline carry-forward.** Sale-agreed but not yet exchanged, with expected exchange or completion month, fee value, current fall-through risk pulled from `chase-progression`. One-line narrative of next month's expectation.
+5. **Variance narrative.** Two paragraphs comparing the period to the previous month and to the same period last year, in plain language. Built by `variance-narrator`. Suitable to paste into a board update, a tax-return cover note, or a conversation with a partner.
+
+## Approval gates
+
+- **Variance writeoffs.** Any fee variance the workflow proposes to write off (FX, small reconciliation differences) requires per-item approval.
+- **Commission payment batch.** Staged by `payment-batch-stager`. No transfer is initiated; the operator approves the batch for export to their bank, or makes payments manually using the schedule.
+- **Journal entries.** Any postings to the accounting system require approval. The default behaviour is to propose postings, show what they would do, and let the operator approve before they hit the books.
+- **Accountant pack send.** The drafted email to the accountant with the pack attached requires explicit approval before send.
+
+## Continuous learning hooks
+
+- Categorisation conventions. The accountant prefers a specific chart-of-accounts mapping. Corrected once, learned for every subsequent close.
+- Variance tolerance. Default writeoff threshold tightens or loosens based on overrides.
+- Narrative tone. Voice for the variance paragraphs learned from edit-before-approve diffs.
+- What to flag. "I always want to know about completions over GBP 5,000 fee value" leads the pack with those. "Don't bother flagging multi-agency fee splits separately" suppresses that detail.
+- Pipeline narrative confidence. Over time the workflow learns how accurate its "next month should look like X" predictions are and adjusts the confidence language.
+
+All writes go through `profile-writer`.
+
+## Connectors
+
+Read: accounting (Xero, FreeAgent, QuickBooks, Sage), bank feed via the accounting connector, CRM, prior month's close pack.
+Write: accounting (journal entries on approval), payment batch staging for the bank or for a payroll-style export, Drive (close pack storage), email (accountant pack).
+
+## Profile keys
+
+- `realagent.accounting.platform` ("xero" | "freeagent" | "quickbooks" | "sage")
+- `realagent.accounting.chart_of_accounts_map` (learned)
+- `realagent.close.writeoff_threshold_gbp` (default 5)
+- `realagent.close.flag_threshold_fee_gbp` (default 5000)
+- `realagent.close.narrative_voice_samples` (learned)
+- `realagent.close.pack_recipients` (accountant email addresses)
+- `realagent.commission.splits_table_path`
+- `realagent.commission.franchise_levy_pct`

package/payload/premium-plugins/real-agency/plugins/estate-business/skills/payment-batch-stager/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: payment-batch-stager
+description: "Build the commission payment batch ready for the operator's approval. Stages an export for the agent's bank or a payroll-style spreadsheet. Never initiates a transfer. Built for use inside month-end-close."
+---
+
+# Payment batch stager
+
+A building-block skill called by `month-end-close`. Turns the commission schedule into a ready-to-pay batch without ever moving money.
+
+## What it does
+
+Reads the commission schedule produced by `commission-calculator`. For each payee with a non-zero net, the skill produces a row in the batch:
+
+- Payee name
+- Payee bank account (sort code, account number) from the profile's payees table
+- Amount
+- Reference (the deal references, abbreviated to fit the bank's reference length limit)
+- Pay date (the operator's preferred pay date)
+
+Two outputs are produced:
+
+1. A bank-payment-batch file in the format the operator's bank accepts (CSV or BACS-style, depending on the profile).
+2. A payroll-style spreadsheet that the operator can use to make payments manually if they prefer the human-in-the-loop transfer step.
+
+The operator approves the batch. Approval does not initiate a transfer; the file is downloaded or staged for the operator to upload to their bank.
+
+## What it does not do
+
+- It does not initiate a transfer. Ever.
+- It does not store bank credentials.
+- It does not bypass the operator on any change to a payee's bank details. Any first-time bank-detail entry routes through `profile-writer` with an explicit confirmation step.
+
+## Connectors
+
+Read: profile (payees table, bank format), commission schedule from `commission-calculator`.
+Write: file artefact in the agent's Drive.
+
+## Profile keys
+
+- `realagent.payees` (per-agent bank details)
+- `realagent.bank.batch_format` ("csv" | "bacs" | "open_banking_pain001" | "manual")
+- `realagent.bank.preferred_pay_date_offset_days` (days after period end, default 7)

package/payload/premium-plugins/real-agency/plugins/estate-business/skills/period-reconciler/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: period-reconciler
+description: "Match completions to fees received for a closing period and surface variances. Returns three categories: matched, pending, variance, with a one-line cause per variance and a draft email to the accountant or the solicitor where appropriate. Built for use inside month-end-close."
+---
+
+# Period reconciler
+
+A building-block skill called by `month-end-close`. Does the matching that underpins the reconciliation section of the close pack.
+
+## What it does
+
+For the period being closed, the skill reads:
+
+- Every property with completion date in the period from the CRM
+- Every fee receipt in the accounting platform's bank feed for the period and the following 30 days
+
+It then matches receipts to completions on amount and date (with a small tolerance window). Three outcomes per completion:
+
+- **Matched.** Receipt amount matches expected fee within the tolerance. No action.
+- **Pending.** Completion logged but no receipt yet. The completion date age is shown so the operator knows whether to chase.
+- **Variance.** Receipt amount differs from expected fee by more than the tolerance. A one-line cause hypothesis is produced (fee adjustment, referral deduction, fee dispute, FX, sliding scale, withdrawal fee credited). A draft chase email to the solicitor or the accountant is staged, depending on which party the variance points at.
+
+## Variance writeoff
+
+Variances under the profile's writeoff threshold (default GBP 5) are proposed for writeoff. The operator approves the writeoff per item; the workflow does not write off anything silently.
+
+## What it does not do
+
+- It does not post journal entries. Postings are staged by `month-end-close` for the operator's approval.
+- It does not initiate a transfer.
+- It does not chase the solicitor or the accountant; it stages the draft email which the operator approves.
+
+## Connectors
+
+Read: CRM (completions, fee structure), accounting (bank feed, prior reconciliations).
+Write (staged only): email drafts to solicitor or accountant.
+
+## Profile keys
+
+- `realagent.close.writeoff_threshold_gbp` (default 5)
+- `realagent.close.match_tolerance_gbp` (default 1)
+- `realagent.close.match_tolerance_days` (default 30)

package/payload/premium-plugins/real-agency/plugins/estate-sales/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "real-agency-sales",
-  "description": "Estate agency sales cycle — prospect qualification, closing techniques, negotiation frameworks, and sales progression tracking.",
+  "description": "Sale-agreed to completion progression for UK residential sales agents. The headline workflow is chase-progression: daily ranked stalled-deal surfacing with tone-matched draft messages and per-message approval gates. Includes risk-scorer (fall-through risk scoring, used by chase-progression) plus the existing sales-discovery, sales-closer, sales-negotiation, and sales-progression skills.",
   "version": "0.1.0",
   "author": {
     "name": "Rubytech LLC"

package/payload/premium-plugins/real-agency/plugins/estate-sales/PLUGIN.md

@@ -1,34 +1,48 @@
 ---
 name: real-agency-sales
-description: "Estate agency sales cycle — prospect qualification, closing techniques, negotiation frameworks, and sales progression tracking."
+description: "Sale-agreed to completion progression for UK residential sales agents. The headline workflow is chase-progression: daily ranked stalled-deal surfacing with tone-matched draft messages and per-message approval gates. Includes risk-scorer (fall-through risk scoring, used by chase-progression) plus the existing sales-discovery, sales-closer, sales-negotiation, and sales-progression skills."
 tools: []
+skills:
+  - skills/chase-progression/SKILL.md
+  - skills/risk-scorer/SKILL.md
+  - skills/sales-discovery/SKILL.md
+  - skills/sales-closer/SKILL.md
+  - skills/sales-negotiation/SKILL.md
+  - skills/sales-progression/SKILL.md
+  - skills/negotiation/SKILL.md
 always: false
 metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
 ---
 
-# Real Agency — Sales
+# Real Agency, Chase Progression and Sales
 
-Four skills covering the full sales cycle from discovery through to completion tracking.
+Seven skills covering chain progression (the headline workflow) and the existing sales cycle.
 
 ## When to Activate
 
-The user is working on prospect qualification, closing deals, handling objections, protecting price, or tracking transactions from sale agreed to completion.
+The user is working on stalled deals, chain progression, fall-through risk, sale-agreed deals, or any of the existing sales-cycle skills.
 
 ## Skills
 
-| Skill | Purpose |
-|-------|---------|
-| `sales-discovery` | Qualify prospects through structured discovery — needs, authority, motivation, readiness |
-| `sales-closer` | Detect buying signals and close using Serhant emotional stages, Push/Pull/Persist |
-| `sales-negotiation` | Frame value, protect price, navigate objections — Voss, Panos, Phil Jones |
-| `sales-progression` | Track transactions from sale agreed through to completion |
+| Skill | Owner specialist | Purpose |
+|-------|------------------|---------|
+| `chase-progression` | negotiator | Master workflow: daily ranked stalled list with per-message approval |
+| `risk-scorer` | negotiator | Computes fall-through risk score (used inside chase-progression) |
+| `sales-discovery` | negotiator | Qualify prospects |
+| `sales-closer` | negotiator | Detect buying signals and close |
+| `sales-negotiation` | negotiator | Frame value, protect price |
+| `sales-progression` | negotiator | Track transactions from sale agreed through to completion |
+| `negotiation` | negotiator | Negotiation framework (existing) |
 
 ## Tools Used
 
 No MCP server. Skills operate via existing platform tools:
-- `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
+
+- `memory-search` for domain knowledge
+- `render-component` for structured choices
+- `profile-read` and `profile-update` for the customisation profile
+- `action-pending`, `action-approve`, `action-reject`, `action-edit` for the per-message approval gates in chase-progression
 
 ## References
 
-Domain knowledge files loaded on demand by each skill. See individual skill files for their specific reference listings.
+Domain knowledge files loaded on demand by each skill.

package/payload/premium-plugins/real-agency/plugins/estate-sales/skills/chase-progression/SKILL.md

@@ -0,0 +1,107 @@
+---
+name: chase-progression
+description: "The headline daily-and-on-demand workflow that protects pipeline fee income. Surfaces stalled sale-agreed deals ranked by fall-through risk and fee value, drafts tone-matched messages per stakeholder, and fires only the messages the operator approves. Triggers when the operator says 'chase the chain', 'chase progression', 'where is everyone on <address>', 'push <name>'s deal', 'push the chain on <address>', 'follow up on the <name> solicitors', 'what's stalled', 'stalled deals', 'any updates on <address>'. Also runs as a sub-flow of the morning round."
+---
+
+# Chase progression
+
+The master workflow owned by the negotiator. The headline of the product. Sales agents lose more fee income to stalled chains than to any single other cause; this workflow protects every pipeline fee the agent has earned.
+
+Done well, every weekday morning the operator opens chase-progression, reads 5 to 15 ranked stalled deals with drafted messages, approves the ones to send, edits one or two, skips the ones already handled, and is done in under 10 minutes. The alternative is a half-day a week on the same work, done badly.
+
+## Inputs
+
+- The customisation profile.
+- Every sale-agreed deal in the CRM with its full state, including last contact per party.
+- The mortgage offer expiry dates held in the CRM where available.
+- The calendar (for surveyor and viewing schedules).
+
+If invoked with a property name ("push 14 Garth Road"), the workflow narrows to the single-deal deep dive for that property and skips the across-pipeline view.
+
+## Architecture principles encoded here
+
+- Read before write. The workflow opens by reading the chain state for every deal. It does not draft a message until the deal state has been built.
+- Stage, don't send. Every message is a draft until the operator approves it. The workflow never fires a message that has been edited but not re-approved.
+- One screen of output. The ranked list collapses to one screen even when there are 15 deals. Each row is one line until the operator expands it.
+- Cite the source. Every cause sentence cites the connector reads that support it. Every draft message references the actual deal record.
+- Teach the profile. Edit-before-send diffs are the gold signal; see learning hooks.
+- Reversible. A sent message creates a CRM activity entry. The "spoke to them" override removes a recipient and logs the verbal contact.
+
+## Two views
+
+### Across-pipeline view
+
+Every sale-agreed deal stalled past the threshold for the relevant stakeholder type, ranked by fall-through risk multiplied by fee value. For each deal, one line shows:
+
+- Property
+- Days since the last positive movement
+- One-line cause from chain state
+- Drafted message ready to fire
+
+Built by composing `chain-progression-tracker` (state), `risk-scorer` (risk), `priority-ranker` (rank), and `tone-matched-drafter` (drafts).
+
+### Single-deal deep-dive view
+
+When the operator names a property, the workflow returns the full state: every party, every last-known status, every outstanding action, every risk flag, and draft messages for every stakeholder who needs chasing. Each draft is in the right tone for that recipient and channel.
+
+## Tone and channel per recipient type
+
+The profile holds a tone preference per type, calibrated from voice samples and from edit-before-send diffs. Defaults:
+
+| Recipient type | Default tone | Channel default |
+|---|---|---|
+| Vendor (familiar) | Conversational, first name | WhatsApp or mobile |
+| Vendor (formal) | Polite, surname | Email |
+| Buyer (familiar) | Conversational, first name | WhatsApp or mobile |
+| Buyer (formal) | Polite, surname | Email |
+| Vendor solicitor | Formal, surname, references file | Email |
+| Buyer solicitor | Formal, surname, references file | Email |
+| Mortgage broker | Polite, first name, references buyer | Email or phone |
+| Surveyor | Brief, polite, references property | Email |
+
+Defaults are starting points. Within a month of use each agent's tone profile is distinct.
+
+## Approval gates
+
+Per message. The workflow presents drafts in a batch (cap 15). The operator can:
+
+- **Approve all.** Fires every message as drafted.
+- **Approve, edit some.** Edits are captured for learning. Remaining approved messages fire as drafted.
+- **Approve some, skip some.** Fires only approved ones. Skipped recipients are excluded from chase for 24 hours.
+- **Pause.** Saves the batch and returns to it later.
+
+If the operator has more than 15 stalled deals, the workflow surfaces two batches of 15 with a pause between rather than one batch of 30. Approve-all-and-regret is the failure mode the cap prevents.
+
+## The "spoke to them" override
+
+The most frequent operator action with this workflow is "don't chase Mrs Patel, I spoke to her yesterday". The workflow recognises this phrasing, removes the recipient from the batch, writes a CRM activity entry with timestamp and the note "operator confirms verbal contact, no chase needed", and resets the stalled-threshold clock for that recipient.
+
+## Continuous learning hooks
+
+- Cadence per stakeholder type. "I chase solicitors at 5 days, brokers at 3, vendors weekly". Learned from explicit corrections and from edit-frequency patterns.
+- Tone profile. The deepest learning hook in the product. Every edit-before-send diff is gold. Within a quarter the workflow should be drafting messages the agent sends without editing 80% of the time.
+- Risk weights. Reweighted by which deals actually fall through (negative outcome) and which complete (positive outcome). Slow signal, high quality.
+- Skip patterns. Recipients the agent never chases (a friend, a regular client they handle in person) get excluded automatically once the pattern is recognised.
+- Channel preferences per recipient. If the operator always changes the drafted email to a WhatsApp, the channel preference updates.
+- Phrasing pet peeves. "I hope this finds you well" edited out every time stops appearing in drafts.
+
+All writes go through `profile-writer`.
+
+## Connectors
+
+Read: CRM, email, WhatsApp, calendar, mortgage offer expiry data if held in CRM.
+Write: Email, WhatsApp Business, SMS, each on explicit per-message approval.
+
+## WhatsApp Business templating
+
+WhatsApp Business is rate-limited and template-restricted for the first interaction with a recipient. The workflow knows when a recipient is on an open 24-hour conversation window and when a template message is required. The operator does not need to know which is which; the draft adapts.
+
+## Profile keys
+
+- `realagent.stalled_threshold_days.*` (per stakeholder type)
+- `realagent.tone_profile.*` (per recipient type)
+- `realagent.channel_preference.<recipient_id>` (learned per recipient)
+- `realagent.batch_cap` (default 15)
+- `realagent.skip_recipients` (list, learned)
+- `realagent.phrasing_pet_peeves` (list of phrases the agent edits out, learned)
+- `realagent.risk_weights.*` (learned from outcome correlation)

package/payload/premium-plugins/real-agency/plugins/estate-sales/skills/risk-scorer/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: risk-scorer
+description: "Compute a fall-through risk score per stalled deal from observable signals. The score drives the ranking and a one-line cause description; the number itself is never shown to the operator. Built for use inside chase-progression."
+---
+
+# Risk scorer
+
+A building-block skill called by `chase-progression`. Computes the risk score that `priority-ranker` uses to order the stalled list, and the cause sentence the operator reads.
+
+## Signals
+
+The score is a weighted combination of:
+
+- Days since any party's last contact
+- Days since the last positive progress event
+- Mortgage offer expiry date approaching (offers usually valid 3 to 6 months)
+- Searches outstanding past day 21
+- Survey booked but not done past day 14
+- Vendor or buyer disengagement signals (slow replies, terse messages)
+- Chain complexity (number of linked transactions)
+- Onward-purchase status if known
+
+The weights are profile-learned from outcome correlation. Deals that the workflow flagged as high risk and that actually fell through reinforce the weighting. Deals flagged high that completed without incident reduce the weighting on whatever signal triggered the flag.
+
+## Opacity rule
+
+The numeric score is never surfaced to the operator. Showing a number invites debate. Showing a one-line cause invites action. The skill returns the score for the ranker to use internally and returns the cause sentence for the operator to see.
+
+## What it does not do
+
+- It does not write to the CRM.
+- It does not produce a probability of fall-through as a percentage. The score is a relative ranking signal, not a forecast.
+- It does not draft messages.
+
+## Connectors
+
+Read: CRM, email, WhatsApp, calendar, mortgage offer data if held in CRM. No writes.
+
+## Profile keys
+
+- `realagent.risk_weights.*` (per signal, learned)
+- `realagent.risk_weights.fee_multiplier` (how heavily fee value modulates the rank, default 1.0)

package/payload/premium-plugins/real-agency/plugins/leads/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "real-agency-leads",
-  "description": "Lead generation and pipeline building — systematic nurturing, database reactivation, and proactive prospecting for UK estate agents.",
+  "description": "Daily morning round and lead-pipeline skills for UK residential sales agents. Composes diary, awaiting-reply, overnight-enquiry triage, and stalled-deal surfacing into one snapshot, plus the chain-progression-tracker shared with chase-progression.",
   "version": "0.1.0",
   "author": {
     "name": "Rubytech LLC"

package/payload/premium-plugins/real-agency/plugins/leads/PLUGIN.md

@@ -1,31 +1,45 @@
 ---
 name: real-agency-leads
-description: "Lead generation and pipeline building — systematic nurturing, database reactivation, and proactive prospecting for UK estate agents."
+description: "Daily morning round and lead-pipeline skills for UK residential sales agents. Composes diary, awaiting-reply, overnight-enquiry triage, and stalled-deal surfacing into one snapshot, plus the chain-progression-tracker shared with chase-progression."
 tools: []
+skills:
+  - skills/morning-round/SKILL.md
+  - skills/diary-builder/SKILL.md
+  - skills/enquiry-triage/SKILL.md
+  - skills/chain-progression-tracker/SKILL.md
+  - skills/lead-nurturing/SKILL.md
+  - skills/prospecting/SKILL.md
 always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency — Lead Generation
+# Real Agency, Lead Generation and Morning Round
 
-Two skills covering pipeline building and database reactivation.
+Six skills: four covering the daily morning round (master plus building blocks) and two covering longer-horizon lead nurturing and prospecting.
 
 ## When to Activate
 
-The user is working on lead nurturing, follow-up cadences, database reactivation campaigns, prospecting activities, or outreach strategies.
+The user is asking for the morning round, the daily brief, the day's diary, overnight enquiries, or anything stalled. Also activates when the user is working on lead nurturing, follow-up cadences, database reactivation campaigns, prospecting activities, or outreach strategies.
 
 ## Skills
 
-| Skill | Purpose |
-|-------|---------|
-| `lead-nurturing` | Systematic follow-up and pipeline warming — Serhant Three F's, HOT/WARM/COLD cadence |
-| `prospecting` | Database reactivation, lead generation, campaign chaining, proactive outreach |
+| Skill | Owner specialist | Purpose |
+|-------|------------------|---------|
+| `morning-round` | negotiator | The daily one-page snapshot: diary, awaiting replies, overnight enquiries, stalled deals, top three |
+| `diary-builder` | negotiator | Today's diary block for the morning round |
+| `enquiry-triage` | negotiator | Triages overnight portal and email enquiries |
+| `chain-progression-tracker` | negotiator | State-of-the-chain view; used by morning round and chase-progression |
+| `lead-nurturing` | negotiator | Systematic follow-up and pipeline warming |
+| `prospecting` | negotiator | Database reactivation, lead generation, campaign chaining |
 
 ## Tools Used
 
 No MCP server. Skills operate via existing platform tools:
-- `memory-search` — retrieve domain knowledge from the knowledge base
-- `render-component` — present structured choices during interactions
+
+- `memory-search` to retrieve domain knowledge from the knowledge base
+- `render-component` to present structured choices during interactions
+- `profile-read` and `profile-update` for the customisation profile
+- `task-create` to file an open task when a chase needs deferring
 
 ## References
 

package/payload/premium-plugins/real-agency/plugins/leads/skills/chain-progression-tracker/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: chain-progression-tracker
+description: "Build the state-of-the-chain view for a sale-agreed deal. Identifies stalled deals across the pipeline for the morning round, and produces a single-deal deep dive when the chase-progression workflow expands one. Read-only; never sends anything."
+---
+
+# Chain progression tracker
+
+A building-block skill used by two workflows. The morning round calls it for the across-pipeline stalled view. The chase-progression workflow calls it for the single-deal deep dive.
+
+## Two modes
+
+### Across-pipeline mode
+
+Used by `morning-round`. Returns every sale-agreed deal where nothing has moved past the stalled threshold for the relevant stakeholder type. For each, returns:
+
+- Property address
+- Days since the last positive movement
+- The most likely cause from chain state, expressed as one short sentence
+
+The stalled threshold is read from the profile, per stakeholder type. Default 7 days for everyone; learns per type.
+
+### Single-deal deep-dive mode
+
+Used by `chase-progression`. Given a property the operator named, returns:
+
+- Every party in the chain with their role
+- Last known status for each party
+- Every outstanding action with the responsible party
+- Every risk flag (offer expiry approaching, searches outstanding, survey booked but not done, vendor or buyer disengagement signals, chain complexity, onward-purchase status)
+- A timeline view of the last 30 days of contact
+
+## What "most likely cause" means
+
+The skill compares the deal state against the typical stalled patterns: solicitor not responding, mortgage offer expiring, survey scheduled but not completed, search results outstanding, vendor unresponsive, buyer unresponsive, chain party upstream unresponsive. The cause sentence is the pattern that best fits the observable signals, written by `variance-narrator`.
+
+The skill never invents a cause it cannot trace to data. If no pattern fits, the cause line says "no clear cause from connectors, manual check recommended".
+
+## What it does not do
+
+- It does not compute the fall-through risk score. That is `risk-scorer`, called separately by `chase-progression`.
+- It does not draft messages. Draft messages come from `tone-matched-drafter`.
+- It does not write to the CRM.
+
+## Connectors
+
+Read: CRM, email, WhatsApp, calendar, mortgage offer expiry data if held in CRM. No writes.
+
+## Profile keys
+
+- `realagent.stalled_threshold_days.*` (per stakeholder type)
+- `realagent.cause_phrases` (preferred cause phrasings, learned from edits)

package/payload/premium-plugins/real-agency/plugins/leads/skills/diary-builder/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: diary-builder
+description: "Produce the today's diary block for the morning round. Reads the calendar and the CRM to surface every viewing, valuation, market appraisal, vendor meeting, and completion call for today, with times, addresses, contact, and postcode."
+---
+
+# Diary builder
+
+A building-block skill the operator never names. Called by `morning-round` to build the diary block of the daily snapshot.
+
+## What it does
+
+Reads today's calendar entries from the connected calendar (M365 or Google). For each entry it correlates the CRM record so that the line shows the right contact and the property context, not just a calendar title. Items not tied to a CRM record still appear, marked as "calendar entry, no CRM match".
+
+## Output shape
+
+A list, one line per entry, sorted by start time. Each line shows:
+
+- Start time and duration
+- Activity type: viewing, valuation, market appraisal, vendor meeting, completion call, other
+- Address with postcode
+- Contact name and role (vendor, buyer, applicant)
+
+If the order of addresses by postcode is not geographically sensible, a one-line note flags it so the operator can resequence before they leave the office.
+
+## What it does not do
+
+- It does not produce the prep pack for any valuation in the diary. That is `valuation-prep`, which the operator invokes after reading the diary.
+- It does not chase anyone. The diary is read-only output.
+- It does not modify the calendar.
+
+## Connectors
+
+Read: calendar, CRM. No writes.
+
+## Profile keys
+
+- `realagent.diary.postcode_ordering` (boolean, default true)
+- `realagent.diary.show_internal_events` (boolean, default false)

package/payload/premium-plugins/real-agency/plugins/leads/skills/enquiry-triage/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: enquiry-triage
+description: "Classify overnight portal and email enquiries into hot, lukewarm, cold, duplicate, or spam. Built for use inside the morning round; the operator does not invoke it directly."
+---
+
+# Enquiry triage
+
+A building-block skill called by `morning-round`. Takes the new portal and email enquiries since the last round and assigns each one a triage tag.
+
+## What hot, lukewarm, cold, duplicate, and spam mean
+
+- **Hot.** The enquirer named a price range and a timeline, or asked to book a viewing, or referenced a specific property and confirmed they are a proceedable buyer. Hot enquiries appear verbatim in the round so the operator can act on them without re-reading the source.
+- **Lukewarm.** The enquirer asked about a property without naming budget, timeline, or position. The round shows a one-line summary.
+- **Cold.** Generic enquiry with no specifics. One-line summary in the round.
+- **Duplicate.** Matches a previous enquiry by phone, email, or named buyer in the last 30 days. One-line summary referencing the prior contact.
+- **Spam.** Off-topic, lead-broker, or otherwise non-buyer traffic. One-line summary so the operator can confirm the call.
+
+## Triage signals
+
+For each enquiry, the skill considers: source (Rightmove, Zoopla, OnTheMarket, agency website, direct email, WhatsApp), the literal text of the enquiry, the contact details supplied, the CRM history of the same contact, and the property the enquiry refers to.
+
+The decision is the LLM's, not a regex. Classification quality improves as the profile learns from skip patterns (see learning hooks in `morning-round`).
+
+## What it does not do
+
+- It does not reply to enquiries. Reply drafting is `tone-matched-drafter`, invoked from a chase or new-instruction workflow.
+- It does not write to the CRM. The enquiry record itself lives in the portal or the email connector; this skill only reads.
+
+## Connectors
+
+Read: portal feeds (Rightmove, Zoopla, OnTheMarket), email, WhatsApp, CRM. No writes.
+
+## Profile keys
+
+- `realagent.enquiry_triage.source_weights` (map of source to weight, learned)
+- `realagent.enquiry_triage.spam_phrases` (list of phrases the operator has flagged as spam, learned)