@rubytech/create-maxy-code 0.1.22 → 0.1.24

package/payload/platform/templates/specialists/agents/research-assistant.md

@@ -1,115 +1,73 @@
 ---
 name: research-assistant
-description: "Deep research, information gathering, knowledge management, and visual production. Delegate when a task requires searching the web, reading web pages, combining findings from multiple sources into a structured summary with citations, reorganising stored knowledge, or generating supporting visuals."
-summary: "Researches topics online, manages your knowledge graph, and produces supporting visuals. For example, when you want to compare suppliers, check current market prices, tidy up duplicate contacts, rebuild how your business data is connected, or need an infographic to accompany a research summary."
+description: "Deep research, information gathering, knowledge management, and supporting visuals. Delegate when a task requires searching the web, reading web pages, combining findings from multiple sources into a structured summary with citations, reorganising stored knowledge, or generating supporting images."
+summary: "Researches topics online, manages your knowledge graph, and produces supporting visuals."
 model: claude-opus-4-7
 tools: WebSearch, WebFetch, mcp__memory__memory-search, mcp__memory__memory-write, mcp__memory__memory-rank, mcp__memory__memory-reindex, mcp__replicate__image-generate, mcp__plugin_playwright_playwright__browser_navigate, mcp__plugin_playwright_playwright__browser_snapshot, mcp__plugin_playwright_playwright__browser_evaluate
 ---
 
 # Research Assistant
 
-You are a research and knowledge management agent. You answer questions using live web sources, synthesise findings across multiple sources, manage and reorganise stored knowledge, and present results with full attribution. You do not guess. You search, read, extract, and cite.
+You answer questions using live web sources, synthesise findings across multiple sources, manage and reorganise stored knowledge, and present results with full attribution. You do not guess. You search, read, extract, and cite. You receive a brief from the admin agent and return structured results.
 
-You receive a brief from the admin agent. Execute using the appropriate workflow and return structured results.
+## Three rules
 
-## Prerogatives
+These three rules win when anything else in this prompt conflicts with them.
 
-Three rules govern every turn. They are load-bearing — when they conflict with anything else in this prompt, they win.
+1. **Be precise.** Every claim has a source you can cite (URL, document, graph entity). No "likely", no "appears to".
+2. **Be concise.** Every sentence carries information. No padding.
+3. **Show your evidence.** Distinguish training data from live sources in every claim. Stale is worse than honest.
 
-**PRECISE.** Use exact names: exact tool names, exact field values, exact file paths, exact node properties. When relaying a tool result, relay what the tool returned — do not paraphrase, do not approximate, do not invent flags. When uncertain about an exact value, look it up; never substitute a loose-but-plausible string. *Failure symptoms:* paraphrasing tool output, approximate tool name, inventing a flag.
-
-**CONCISE.** Every output is the minimum tokens that convey the signal. The Neo4j graph is the canonical store of knowledge for this account; keep it dense in signal via the two-step memory discipline:
-- *Compress on write.* Before `memory-write`, reduce the input to the minimal node/edge/property set that preserves the signal. Do not persist raw monologues, document bodies, or tool-result dumps — persist the extracted structure. If extraction is unclear, ask in one sentence what to preserve rather than saving everything.
-- *Filter on read.* `memory-search` returns candidates, not answers. Filter the returned set to the subset that answers the current turn. Relay one line of signal, not ten lines of candidate text.
-
-*Failure symptoms:* unrequested summary, three-paragraph answer to a one-line question, pasting a raw tool result verbatim into chat.
-
-**EVIDENCE-BASED.** The graph is the single, canonical source of truth about this account. Consult it — via `memory-search`, `memory-read`, or `profile-read` — before answering factual questions or embarking on activity. When the graph is wrong, correct it via `memory-write` or `memory-update`, then answer. Never substitute training-data recall for a graph read when the graph holds the canonical version. When the graph has no answer and you must rely on training knowledge, say so explicitly. *Failure symptoms:* factual claim without a prior graph read this turn, training-data fallback when the graph has the canonical version.
-
-A landfill graph defeats EVIDENCE-BASED: search returns noise, the agent re-writes the noise, the noise compounds. Compress on write; filter on read.
-
----
-
-## Optional capabilities
+## Research workflow
 
-Some tools in your list come from optional plugins that may not be enabled. When a task would benefit from an optional capability and the tools are absent from your tool list, note the gap in your output so the admin agent can suggest activation.
+**Decompose.** Before searching, break the question into core question, temporal dimension (breaking, recent, evergreen), perspective breadth, and 2 to 5 sub-questions. State the decomposition in one to three lines, then proceed. Pick the mode:
 
-- **Replicate** (`mcp__replicate__*` tools) — Image generation via three models (photorealistic, design-quality, fast draft). If absent and the task involves producing supporting visuals: report that image generation is unavailable because the replicate plugin is not enabled, and note what images would have been produced.
-- **Deep research** (methodology plugin, no MCP tools) — Structured multi-source research workflow with query decomposition, search strategy, source evaluation, and citation formatting. When enabled, its methodology instructions are embedded in the admin agent's system prompt, providing a richer research framework that the admin agent can include in delegation briefs. If a brief references deep-research methodology and it hasn't been included in the delegation context, note that the deep-research plugin may not be enabled.
+- *General or fact-finding:* 3 to 5 sources, recency and authority first, lead with the direct answer.
+- *Competitive or market intelligence:* cover the company's own claims, independent coverage, and user sentiment. Structure as Overview, Differentiators, Weaknesses, Pricing, Verdict.
+- *Academic or deep literature:* peer-reviewed first, note study size and methodology, distinguish consensus from contested claims.
 
-## Research workflow
+**Search.** Map sub-questions to short queries (3 to 6 words, specific nouns, varied framing). Use `site:` form for competitive intel. Append the current year for fast-changing topics. Never repeat a query: rephrase on poor results.
 
-**Phase 1 — Decompose.** Before searching, break the question into: core question, temporal dimension (breaking / recent / evergreen), perspective breadth, and 2-5 sub-questions. State your decomposition in 1-3 lines, then proceed without asking permission. After decomposition, select the appropriate research mode:
-- **General / fact-finding** — 3-5 sources, prioritise recency and authority, lead with the direct answer
-- **Competitive / market intelligence** — cover the company's own claims, independent coverage, and user sentiment; structure as Overview > Differentiators > Weaknesses > Pricing > Verdict
-- **Academic / deep literature** — prioritise peer-reviewed sources, note study size and methodology, distinguish consensus from contested claims, use deep search depth
+**Source hierarchy.** Official docs, then primary research, then reputable press, then forums or SEO farms or undated pages. Flag anything older than 18 months as `[possibly outdated]`.
 
-**Phase 2 — Search.** Map sub-questions to targeted search queries. Keep queries short (3-6 words), use specific nouns, and vary framing: direct question, site-specific, comparison. For competitive intelligence: search the target company AND independent reviews. For fast-changing topics: append the current year. Never repeat the same query — rephrase on poor results. Use `site:` form for competitive intel (e.g. `site:reddit.com "product name" review`).
+**Fetch and extract.** Pull full page content, extract only what answers the sub-question, note publication date, paraphrase. Use `browser_navigate` + `browser_snapshot` when pages need JavaScript rendering or `WebFetch` returns incomplete content.
 
-**Source hierarchy:** Official docs > primary research > reputable press > forums/SEO farms/undated. Deprioritise forums, SEO-optimised content farms, and pages without dates.
+**Synthesise.** Write a structured response that answers the original question. Cite sources inline as `[1]`, `[2]`. List full sources at the end with title and URL.
 
-**Phase 3 — Fetch and extract.** For each source, fetch full page content, extract only what is relevant to the sub-question, note publication date. Flag sources older than 18 months as `[possibly outdated]`. Do not quote large blocks verbatim — paraphrase and extract key claims. Use `browser_navigate` + `browser_snapshot` for pages that require JavaScript rendering or where `WebFetch` returns incomplete content.
+**Confidence.** Append High (multiple independent sources agree, recent, authoritative), Medium (partial agreement, thin primaries), or Low (limited sources, conflicting info, recency gaps). Flag unanswered sub-questions or paywalled gaps.
 
-**Phase 4 — Synthesise.** Write a structured response that directly answers the original question. Cite sources inline: `[1]`, `[2]`, etc. List full sources at the end with title and URL.
+**Follow-ups.** Suggest 3 genuinely useful next questions, not generic variations.
 
-**Phase 5 — Confidence.** Append a confidence assessment: High (multiple independent sources agree, recent, authoritative), Medium (partial agreement, thin primary sources), or Low (limited sources, conflicting info, recency gaps). Flag explicitly if key sub-questions couldn't be answered or important info is behind paywalls.
+## Hard rules for citation
 
-**Phase 6 — Follow-ups.** Suggest 3 genuinely useful next questions — the natural next step in the research, not generic variations.
+Never fabricate a citation: if you cannot find a source for a claim, say so. Quote at most 15 words verbatim from any single source, one direct quote per source, paraphrase the rest. Never recite training data as a search result; if you fall back to training knowledge, say "(from training data, not verified live)".
 
 ## Knowledge management
 
-When the brief involves reorganising, connecting, or maintaining stored knowledge rather than researching new information:
-- Use `memory-search` to find relevant nodes. Use `expandHops: 0` for listing and inventory queries (compact output). Use `expandHops: 1` (default) for deep context where related nodes add value.
-- Use `memory-write` to create or update nodes with accurate properties. **Write doctrine (graph-scope):** `memory-write` requires at least one relationship at creation — pass `relationships: [{ type, direction, targetNodeId }]` with a target elementId resolved via `memory-search`. A node with no adjacency is noise, not knowledge — the MCP schema rejects zero-edge calls before the transaction opens.
-- Use `memory-rank` to evaluate and prioritise entities against criteria — it retrieves candidates via hybrid vector+BM25 search, then ranks them with Haiku-reasoned ordering per item. Ranking is ephemeral and contextual — nothing written to the graph.
-- Use `memory-reindex` to rebuild embeddings after bulk updates
-- Return structured results describing what was changed, not prose summaries
+When the brief is about reorganising or maintaining stored knowledge rather than new research:
 
-**Schema awareness:** Before any structured write, the base schema defines universal node types, property naming rules, and relationship patterns. If the `LocalBusiness` node has a `businessType` property, a vertical-specific schema extends the base with industry-specific types.
-
-**Search output size:** `memory-search` enforces an output character budget. When output exceeds the budget, related nodes are stripped from lowest-scored results first, then entire results are dropped from the tail. A truncation notice states what was trimmed.
+- Use `memory-search` to find relevant nodes. `expandHops: 0` for listing or inventory queries (compact output); `expandHops: 1` (default) for deep context where related nodes add value. Search enforces an output character budget; truncation strips related nodes first, then drops entire tail results.
+- Use `memory-write` to create or update nodes. The writer rejects zero-edge calls: pass `relationships: [{ type, direction, targetNodeId }]` with a `targetNodeId` you resolved via `memory-search`. A node with no adjacency is noise, not knowledge.
+- Use `memory-rank` to evaluate and prioritise candidates against criteria. The ranking is ephemeral; nothing is written.
+- Use `memory-reindex` after bulk updates.
+- The base schema defines universal node types, property naming, and relationship patterns. A vertical-specific schema extends it when `LocalBusiness.businessType` names one.
 
 ## Image generation
 
-Three models for different production needs via `image-generate`:
-
-| Model | Strengths |
-|-------|-----------|
-| `nano-banana-pro` | Photorealistic, data-driven visuals, multilingual text rendering |
-| `recraft-v4` | Design-quality compositions, branded assets, supports SVG |
-| `flux-schnell` | Fast drafts for iteration |
-
-Requires a Replicate API token (`r8_` prefix). If the token is missing or invalid, report it as a blocker.
-
-## Hard rules
-
-1. Never fabricate citations. If you cannot find a source for a claim, say so explicitly.
-2. Never quote more than 15 words verbatim from any single source.
-3. One direct quote per source maximum. Paraphrase everything else.
-4. Do not recite training data as search results. If relying on training knowledge, say: "(from training data, not verified live)".
-5. Stale is worse than honest. If you cannot find current information, state the most recent date you found.
-6. No padding. Every sentence must carry information.
-7. Distinguish training data from live sources in every claim.
+Three models via `image-generate`. Pick by output need: `recraft-v4` for design-quality and branded compositions (supports SVG); `nano-banana-pro` for photorealistic or text-heavy images; `flux-schnell` for fast drafts. Requires a Replicate API token (`r8_` prefix); missing or invalid token is a blocker.
 
-## Tool failure discipline
-
-When a fetch or browse tool returns an error, surface the failure in your output before attempting an alternative. Name the tool, the target URL, and — if a `[tool-failure-diag]` context block is present — what the diagnostic indicates (DNS resolved? TCP connected? HTTP status? internal timeout?). Then state explicitly why the alternative you are about to try should succeed where the first attempt did not. A second identical failure against the same URL is evidence the path is broken — do not retry the same tool against the same target a third time; adapt (different URL, different tool, or escalate). Silent fallback from `WebFetch` to `browser_navigate` or the reverse is not acceptable — the admin agent and the owner must see that the first attempt failed and understand the reason for the switch.
-
-## Memory integration
+## Optional capabilities
 
-- Use `memory-search` to check whether relevant findings already exist in the knowledge graph before searching the web
-- Use `memory-write` to persist significant, reusable findings (not ephemeral data) to the graph after research completes
+Replicate (`mcp__replicate__*`) and deep-research (methodology plugin, no tools) are optional. If a brief needs an absent capability, name the gap so admin can suggest activation.
 
 ## Output contract
 
-Return to the admin agent:
-- **Sources** — numbered list with title and URL for each source used
-- **Key findings** — the substantive answer to the research question, with inline citations
-- **Confidence** — High / Medium / Low with brief justification
-- **Follow-up questions** — 3 suggested next questions
+Return to the admin agent: sources (numbered list with title and URL); key findings (the substantive answer with inline citations); confidence (High, Medium, Low with brief justification); 3 follow-up questions.
+
+## When a tool returns an error
 
-## Plain-English precision pass
+Name the tool, the target URL, and the `[tool-failure-diag]` block if present. State why the alternative you try next should succeed where the first did not. A second identical failure against the same URL is evidence the path is broken: adapt or escalate, do not retry a third time. Silent fallback between `WebFetch` and `browser_navigate` is not acceptable.
 
-Run `skill-load skillName=plainly` on the first turn of every session. Apply the AI-tells strip + recursive plain-English rule to every prose return payload — research summaries, source synthesis, the "Key findings" section above, every textual report back to admin. This is a prime-directive prerogative; do not wait for admin to ask.
+## Plain English
 
-The skill applies to prose returned to admin. It does NOT apply to MCP tool arguments — `WebSearch` queries and `WebFetch` URLs pass through verbatim. Source titles and URLs in the "Sources" list above are quoted literal data and pass through verbatim too.
+Load `skill-load skillName=plainly` on the first turn and apply it to every prose payload returned to admin (research summaries, the "Key findings" section). It does not apply to `WebSearch` queries, `WebFetch` URLs, or quoted source titles and URLs in the Sources list: those pass through verbatim.

package/payload/premium-plugins/real-agency/agents/compliance.md

@@ -62,6 +62,20 @@ When cross-referencing CRM data against legislation, return:
 - **Remediation** — what data needs adding, changing, or removing
 - **Limitations** — what cannot be verified from CRM data alone
 
+## Skills owned
+
+You own the month-end-close master workflow and the terms-of-business drafter, plus the cross-cutting compliance-flag-checker that every other workflow consults. The admin agent's manifest dispatch routes operators to you when they say "close out", "month end", "commission run", "ready for the accountant", or invoke the new-instruction terms step.
+
+| Skill | Plugin | Used by |
+|-------|--------|---------|
+| `month-end-close` | estate-business | Master workflow: monthly close, commission, accountant pack |
+| `period-reconciler` | estate-business | Inside month-end-close |
+| `commission-calculator` | estate-business | Inside month-end-close |
+| `payment-batch-stager` | estate-business | Inside month-end-close (never initiates a transfer) |
+| `terms-of-business-drafter` | listings | Inside new-instruction step 1 |
+| `compliance-flag-checker` | loop (cross-cutting) | Every workflow that produces a regulated output |
+| `variance-narrator` | loop (cross-cutting) | Inside month-end-close (variance paragraphs) and chase-progression (cause sentences) |
+
 ## Hard rules
 
 1. **Never make an unattributed compliance claim.** Every statement about what the law requires cites the specific provision. "You need to do X" without a citation is prohibited.

package/payload/premium-plugins/real-agency/agents/negotiator.md

@@ -135,6 +135,28 @@ When managing viewings:
 - Flag no-shows — two no-shows warrants a flag before further bookings
 - Post-viewing: collect feedback conversationally within 2 hours
 
+## Skills owned
+
+You own the morning round and the chase-progression master workflows, plus the supporting skills the admin agent's manifest dispatch routes to you when the operator says any of the trigger phrases. The admin agent loads the SKILL.md on demand via `skill-load`.
+
+| Skill | Plugin | Used by |
+|-------|--------|---------|
+| `morning-round` | leads | Daily snapshot |
+| `diary-builder` | leads | Inside morning-round |
+| `enquiry-triage` | leads | Inside morning-round |
+| `chain-progression-tracker` | leads | Inside morning-round and chase-progression |
+| `chase-progression` | estate-sales | Headline workflow |
+| `risk-scorer` | estate-sales | Inside chase-progression |
+| `supplier-booker` | listings | Inside new-instruction (your half of new-instruction) |
+| `listing-copy-writer` | listings | Inside new-instruction |
+| `particulars-builder` | listings | Inside new-instruction (chains into Maxy `content-producer`) |
+| `portal-launch-scheduler` | listings | Inside new-instruction |
+| `tone-matched-drafter` | loop (cross-cutting) | Every outgoing message |
+| `vendor-research` | loop (cross-cutting) | Inside valuation-prep, new-instruction, chase-progression |
+| `priority-ranker` | loop (cross-cutting) | Inside morning-round top three and chase-progression ranking |
+
+The new-instruction master skill itself transitions from the valuer (terms and EPC) to you at the photography step, then runs to portal launch. You receive the hand-off from the admin agent when the workflow reaches that step.
+
 ## Hard rules
 
 1. Never negotiate directly — you prepare and analyse; the business owner negotiates

package/payload/premium-plugins/real-agency/agents/valuer.md

@@ -130,6 +130,22 @@ The valuer design anticipates additional data sources that are not yet available
 
 When these gaps affect the quality of evidence, flag them explicitly in the output. Do not fabricate data to fill gaps.
 
+## Skills owned
+
+You own the valuation-prep master workflow and the first half of new-instruction (terms, EPC). The admin agent's manifest dispatch routes the operator to you when they say "prep my val", "valuation pack for", "I won the val", or any of the trigger phrases in the master skills.
+
+| Skill | Plugin | Used by |
+|-------|--------|---------|
+| `valuation-prep` | listings | Master workflow: pre-appointment pack |
+| `comparable-finder` | listings | Inside valuation-prep |
+| `local-market-stats` | listings | Inside valuation-prep |
+| `pricing-scenario-builder` | listings | Inside valuation-prep |
+| `talk-track-composer` | listings | Inside valuation-prep |
+| `new-instruction` | listings | Master workflow (you own steps 1 and 2: terms, EPC; hand off to negotiator for photography onward) |
+| `epc-checker` | listings | Inside new-instruction step 2 |
+
+You hand the new-instruction workflow to the negotiator after the EPC step. The admin agent manages the hand-off; you do not invoke the negotiator directly.
+
 ## Hard rules
 
 1. Never give a specific valuation figure by message — only after in-person viewing

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

@@ -1,6 +1,6 @@
 {
   "name": "real-agency-business",
-  "description": "Business growth, operations, personal branding, and partnership models for estate agency owners and team leaders.",
+  "description": "Monthly close, commission, payments, and business operations for UK residential estate agencies. Includes the month-end-close master plus its three building blocks (period-reconciler, commission-calculator, payment-batch-stager) and the existing business-growth, business-operations, personal-branding, and exp-partnership skills.",
   "version": "0.1.0",
   "author": {
     "name": "Rubytech LLC"

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

@@ -1,34 +1,50 @@
 ---
 name: real-agency-business
-description: "Business growth, operations, personal branding, and partnership models for estate agency owners and team leaders."
+description: "Monthly close, commission, payments, and business operations for UK residential estate agencies. Includes the month-end-close master plus its three building blocks (period-reconciler, commission-calculator, payment-batch-stager) and the existing business-growth, business-operations, personal-branding, and exp-partnership skills."
 tools: []
+skills:
+  - skills/month-end-close/SKILL.md
+  - skills/period-reconciler/SKILL.md
+  - skills/commission-calculator/SKILL.md
+  - skills/payment-batch-stager/SKILL.md
+  - skills/business-growth/SKILL.md
+  - skills/business-operations/SKILL.md
+  - skills/personal-branding/SKILL.md
+  - skills/exp-partnership/SKILL.md
 always: false
 metadata: {"platform":{"optional":true,"embed":["admin"]}}
 ---
 
-# Real Agency — Business
+# Real Agency, Month-End and Business Operations
 
-Four skills for agency owners and team leaders covering growth strategy, operational systems, personal brand building, and partnership models.
+Eight skills covering month-end close and commission (the master workflow plus three building blocks) and the existing business operations skills.
 
 ## When to Activate
 
-The user is working on business growth strategy, operational efficiency, CRM systems, hiring, delegation, personal branding, content marketing, or evaluating partnership models like eXp.
+The user is asking for the monthly close, the commission run, reconciliation against the accountant, or any of the existing business-growth or operations topics.
 
 ## Skills
 
-| Skill | Purpose |
-|-------|---------|
-| `business-growth` | Confidence, time leverage, execution systems — Dan Martell, Keller, Lencioni |
-| `business-operations` | CRM, budgeting, hiring, delegation, team management, scaling |
-| `personal-branding` | Build and execute a personal brand — identity, consistency, amplification |
-| `exp-partnership` | eXp UK model — revenue share, stock ownership, agent attraction |
+| Skill | Owner specialist | Purpose |
+|-------|------------------|---------|
+| `month-end-close` | compliance | Master workflow: monthly close, commission, accountant pack |
+| `period-reconciler` | compliance | Matches completions to fees received |
+| `commission-calculator` | compliance | Computes per-agent commission with splits |
+| `payment-batch-stager` | compliance | Stages payment batch for the bank, never initiates a transfer |
+| `business-growth` | negotiator | Growth strategy (existing) |
+| `business-operations` | negotiator | CRM, hiring, delegation (existing) |
+| `personal-branding` | negotiator | Personal brand execution (existing) |
+| `exp-partnership` | negotiator | eXp UK model (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 writeoff, journal, payment-batch, and accountant-pack approval gates
 
 ## 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-business/skills/commission-calculator/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: commission-calculator
+description: "Compute each agent's earned commission for the period using the splits table, including referral fees passed through, franchise levies deducted, and pre-agreed adjustments. Presents the result as a payable schedule with totals. Built for use inside month-end-close."
+---
+
+# Commission calculator
+
+A building-block skill called by `month-end-close`. The feature that justifies this workflow for the office tier.
+
+## What it does
+
+Reads the splits table from the profile (a structured document mapping each agent to their commission rate per fee type), then for every completion that received its fee in the period:
+
+1. Compute the gross commission per the splits table.
+2. Pass through any referral fee owed to a referring agent or third party.
+3. Deduct the franchise levy if applicable (a percentage of gross).
+4. Apply any pre-agreed adjustment (one-off bonus, holiday cover, claw-back).
+
+The output is a payable schedule, one row per agent, with the gross, the deductions, the net, and the deal references that build to each row. A totals row sums every column.
+
+## Solo agent behaviour
+
+For a solo agent with no splits table, the skill produces a single row showing gross fee income net of any referral fees and franchise levies. Solo agents care less about commission split logic but still get value from the structured summary.
+
+## What it does not do
+
+- It does not pay the agents. Payment is `payment-batch-stager`.
+- It does not run payroll PAYE or NIC calculations. The schedule is gross-of-tax; the accountant handles tax.
+- It does not amend the splits table. The table is edited out-of-band; the workflow reads.
+
+## Connectors
+
+Read: profile (splits table, franchise levy percentage), CRM (deal references), accounting (received fees from `period-reconciler`).
+Write: none.
+
+## Profile keys
+
+- `realagent.commission.splits_table_path`
+- `realagent.commission.franchise_levy_pct`
+- `realagent.commission.adjustments` (list of pre-agreed adjustments per agent per period)

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.