property-dealsheetlisted
Install: claude install-skill Vinedine/para-os
# Property dealsheet
Turns one property's dossier into the designed deal sheet a decision-maker reads, as `## Deal sheets` in the vault's `CLAUDE.md` defines it. The dossier is the underwriting model; the sheet is the derived memo.
## Arguments
| Arg | Behavior |
|---|---|
| *(none)* | Ask which property |
| `<property-name>` | Match against `projects/`, `resources/ideas/`, then `areas/properties/` |
| `<name> <name> ...` | Step 1 for every property, one go-ahead for all, then Steps 2 and 3 per sheet |
| `--test` | Test run, see [para-shared/test-run.md](../para-shared/test-run.md). |
## What it reads
- **The vault's `CLAUDE.md`**: its `**Delivery:**` line, the `## Deal sheets` rules, the language rule.
- **The template**, `resources/prompts/dealsheet-template.html`. Its header comment is the design system, the section skeleton and the stage variants.
- **The source register**, `resources/property-evaluation/property-data-sources.md`, for two things only: which facts no free source settles, and the plan renderer if it names one.
- **The dossier**, the only fact source.
Template or dossier missing: stop and ask.
## Procedure
Track the phases in the harness's task list where it offers one, else in a short progress message at each phase boundary. On `**Delivery:** readonly-ipad`, run [its edit cycle](../para-shared/operating-discipline.md#the-read-only-ipad-delivery) around the build.
1. **Locate and check readiness.** Resolve the vault root once and hold it (`operating