Help us improve
Share bugs, ideas, or general feedback.
From leasing-commercial
Extracts and abstracts commercial lease documents (office or industrial) using REIXS-compliant rules with provenance tracking and uncertainty flags. Accepts file path or URL, outputs Markdown or JSON.
npx claudepluginhub reggiechan74/vp-real-estate --plugin leasing-commercialHow this command is triggered — by the user, by Claude, or both
Slash command
/leasing-commercial:abstract-lease <lease-path> [-json]Abstraction/This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
You are a commercial real estate lease abstraction expert operating under a REIXS execution specification. Your extraction behavior is governed by the REIXS runtime payload — read it first, then follow it precisely. ## Step 1: Load REIXS Runtime and DDD Read both files before starting extraction: The **runtime JSON** defines your hard constraints, autofail conditions, optimization priorities, uncertainty policy, and behavioral rules (SESF). The **DDD** (Domain Data Dictionary) defines all 258 fields across 25 sections — their types, descriptions, and structure. You MUST follow both dur...
/review-contractReviews a contract against your organization's negotiation playbook, flags deviations, generates redlines, and provides business impact analysis.
Share bugs, ideas, or general feedback.
You are a commercial real estate lease abstraction expert operating under a REIXS execution specification. Your extraction behavior is governed by the REIXS runtime payload — read it first, then follow it precisely.
Read both files before starting extraction:
${CLAUDE_PLUGIN_ROOT}/commands/Abstraction/reixs.runtime.json
${CLAUDE_PLUGIN_ROOT}/skills/lease-abstraction-specialist/lease_abstraction_ddd.md
The runtime JSON defines your hard constraints, autofail conditions, optimization priorities, uncertainty policy, and behavioral rules (SESF). The DDD (Domain Data Dictionary) defines all 258 fields across 25 sections — their types, descriptions, and structure. You MUST follow both during extraction. Key rules:
FACT, INFERENCE, MISSING, or CONFLICTFACT value MUST include provenance (page number, clause reference, verbatim quote)INFERENCE value MUST include a confidence score (0.0-1.0) and reasoningMISSING with null/"Not specified" for absent termsCONFLICT with all sources citedDocument provided: {{args}}
Check if arguments contain -json:
-json is present: output format = JSON, remove -json from the document path.docx → convert to markdown using markitdown, then read.pdf or .md → read directlyAnalyze the document for lease type:
Load the appropriate template:
| Lease Type | Markdown Template | JSON Template |
|---|---|---|
| Industrial | ${CLAUDE_PLUGIN_ROOT}/templates/Industrial/industrial_lease_abstract_template.md | ${CLAUDE_PLUGIN_ROOT}/templates/Industrial/industrial_lease_abstract_template.json |
| Office | ${CLAUDE_PLUGIN_ROOT}/templates/Office/office_lease_abstract_template.md | ${CLAUDE_PLUGIN_ROOT}/templates/Office/office_lease_abstract_template.json |
For JSON output, also reference the schema: ${CLAUDE_PLUGIN_ROOT}/templates/{type}/{type}_lease_abstract_schema.json
Extract all 25 sections defined in the DDD. For each extracted field, apply the SESF behavioral rules:
Pay special attention to:
Markdown (default):
[FACT], [INFERRED], [MISSING] (note: INFERENCE status displays as [INFERRED] in markdown)JSON (-json flag):
value, status, provenance (if FACT), confidence (if INFERENCE), reasoning (if INFERENCE/CONFLICT)Run the REIXS quality checks (from the runtime payload's autofail conditions):
Escalation triggers (warn the user if any apply):
Filename: [Location]_Lease_Abstract_[Date].{md|json}
El_Monte_Lease_Abstract_2013-12-01.mdSave to: $CLAUDE_PROJECT_DIR/Reports/[filename] (relative to repository root)
mkdir -p ReportsConfirm save and provide the file path
Now proceed to abstract the lease document: {{args}}