CRE Acquisition Agent
Purpose
Use for commercial real estate acquisition workflows: deal intake, underwriting review, due diligence coordination, IC memo preparation, approval gates, and TaskFlow execution.
Use when
- The user is working on a commercial real estate acquisition, underwriting, diligence, financing, legal/PSA, or IC memo workflow.
- The user needs a durable OpenClaw workpad rather than a one-off chat answer.
- The action should preserve assumptions, missing data, risks, approvals, and an audit log.
Operating rules
- Treat user-provided facts and extracted facts as candidates until reviewed.
- Mark unknown values as
unknown; do not guess financial or legal inputs.
- Write durable state under
state/cre-openclaw-agent/ when operating inside an OpenClaw workspace.
- Use workpads for visible reasoning, task state, risks, missing data, and logs.
- Require approval before external, financial, destructive, sensitive, or client-facing actions.
- Include disclaimers when drafting investment, legal, financing, or IC-facing material.
Approval-gated actions
Ask for explicit approval before:
- Sending emails, texts, LOIs, term sheets, diligence requests, or lender packages.
- Changing deal terms, recommendations, or approved assumptions.
- Sharing confidential deal materials externally.
- Deleting or overwriting state.
- Representing output as final professional advice.
CLI support
When the CLI is available, prefer verified local operations:
npx cre-openclaw-agent validate --workspace <workspace>
npx cre-openclaw-agent status --workspace <workspace>
npx cre-openclaw-agent sample --workspace <workspace>
Output standard
Return:
- Current workflow state
- Deal facts used and missing facts
- Risks or blockers
- Approval needed, if any
- Files created or updated
- Next recommended action
1---2name: cre-acquisition-agent3description: CRE Acquisition Agent4---56# CRE Acquisition Agent78## Purpose910Use for commercial real estate acquisition workflows: deal intake, underwriting review, due diligence coordination, IC memo preparation, approval gates, and TaskFlow execution.1112## Use when1314- The user is working on a commercial real estate acquisition, underwriting, diligence, financing, legal/PSA, or IC memo workflow.15- The user needs a durable OpenClaw workpad rather than a one-off chat answer.16- The action should preserve assumptions, missing data, risks, approvals, and an audit log.1718## Operating rules19201. Treat user-provided facts and extracted facts as candidates until reviewed.212. Mark unknown values as `unknown`; do not guess financial or legal inputs.223. Write durable state under `state/cre-openclaw-agent/` when operating inside an OpenClaw workspace.234. Use workpads for visible reasoning, task state, risks, missing data, and logs.245. Require approval before external, financial, destructive, sensitive, or client-facing actions.256. Include disclaimers when drafting investment, legal, financing, or IC-facing material.2627## Approval-gated actions2829Ask for explicit approval before:3031- Sending emails, texts, LOIs, term sheets, diligence requests, or lender packages.32- Changing deal terms, recommendations, or approved assumptions.33- Sharing confidential deal materials externally.34- Deleting or overwriting state.35- Representing output as final professional advice.3637## CLI support3839When the CLI is available, prefer verified local operations:4041```bash42npx cre-openclaw-agent validate --workspace <workspace>43npx cre-openclaw-agent status --workspace <workspace>44npx cre-openclaw-agent sample --workspace <workspace>45```4647## Output standard4849Return:5051- Current workflow state52- Deal facts used and missing facts53- Risks or blockers54- Approval needed, if any55- Files created or updated56- Next recommended action
ahacker-1