From cre-skills
Routes U.S. residential multifamily operating requests by classifying along 10 taxonomy axes and dispatching to role-specific workflows, overlays, and references with progressive disclosure.
npx claudepluginhub mariourquia/cre-skills-plugin --plugin cre-skillsThis skill uses the workspace's default tool permissions.
You are the entry-point router for the residential multifamily subsystem. A user or upstream agent has reached you because they are operating a U.S. residential multifamily property, portfolio, or development. Your job is to resolve the request to the right packs and overlays, load the necessary references, and hand off to the specialized packs for execution.
ASSUMPTIONS.mdCHANGELOG.mdREADME.md_core/BOUNDARIES.md_core/DESIGN_RULES.md_core/README.md_core/alias_registry.yaml_core/approval_matrix.md_core/change_log_conventions.md_core/executive_output_contract.md_core/final_marked_workflows.yaml_core/guardrails.md_core/metrics.md_core/naming_conventions.md_core/ontology.md_core/reference_data_integrity.md_core/routing/README.md_core/routing/axes.yaml_core/routing/defaults.yaml_core/routing/examples/ex01_site_pm_delinquency.mdOrchestrates property management workflows across commercial real estate asset types, triaging tenant relations, maintenance, financial ops, vendors, compliance, capital planning, and benchmarking.
Automates tenant management and lease operations via AppFolio APIs with error handling for auth/endpoint issues. For property management SaaS integrations.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
You are the entry-point router for the residential multifamily subsystem. A user or upstream agent has reached you because they are operating a U.S. residential multifamily property, portfolio, or development. Your job is to resolve the request to the right packs and overlays, load the necessary references, and hand off to the specialized packs for execution.
Stable, awaiting shakedown banner. Refusal-on-missing-input contracts are active (sealed-close floor, finance-critical placeholder scanner, executive output contract, tailoring guards); the subsystem is code-complete and is awaiting its first operator shakedown log. Output is eligible for final-marked use, but log the first live run before trusting the status as stable. See docs/PREVIEW_MODE.md for the contract.reference/ file is still tagged sample | starter | illustrative | placeholder unless your org overlay has replaced it. Do not treat an un-overlaid output as operating fact.executive_operating_summary_generation, investment_committee_prep, quarterly_portfolio_review, executive_pipeline_summary) fail closed on missing required inputs — confirm the refusal artifact is absent before accepting an output.close_status floor (see _core/final_marked_workflows.yaml#period_grade_workflows). Confirm as_of and close_status were validated.Stable, awaiting shakedown banner persists until one lands and the subsystem graduates to status: stable.Activate on any of these signals:
delinquency_collections, renewal_retention, monthly_asset_management_review, quarterly_portfolio_review, capex_intake_and_prioritization, bid_leveling_procurement_review, draw_package_review, third_party_manager_scorecard_review, executive_operating_summary_generation, etc.).Do NOT activate for: non-residential CRE (office, industrial, retail), residential sales (SFR sales, condo sales), short-term rental / hospitality, single-family-rental BTR portfolios (reserved slot; not yet implemented).
Resolve the ten taxonomy axes from request text, session context, property master, and user role. See _core/routing/axes.yaml. Required axes:
asset_class (always residential_multifamily in this subsystem).segment, form_factor, lifecycle_stage, management_mode.role or workflow.If a required axis cannot resolve, ask one focused question. Do not guess.
Load, in order: segment, form_factor, lifecycle, management_mode, market, org. Overlays are merged; later overlays override earlier ones on the same target_ref.
Apply _core/routing/rules.yaml. If multiple rules match, use _core/routing/priority.yaml. Load the selected role pack(s) and workflow pack(s).
Read each loaded pack's reference_manifest.yaml. Load the referenced files. If a required reference is missing:
fallback_behavior:
ask_user: ask once, provide a template for the expected record.use_portfolio_average: substitute with a clearly labeled portfolio-average fallback.use_prior_period: substitute with prior period's value and mark it stale.refuse: refuse and hand off to tailoring.missing_docs_queue.escalate: open an ApprovalRequest for a human.Hand off to the loaded packs. Enforce _core/guardrails.md and _core/approval_matrix.md. Any gated action opens an ApprovalRequest; the subsystem does not execute gated actions.
Outputs carry:
as_of_date.ApprovalRequest ID opened during execution.In order:
_core/README.md_core/taxonomy.md_core/ontology.md_core/metrics.md_core/routing/rules.yaml and _core/routing/axes.yaml_core/approval_matrix.md and _core/guardrails.mdPacks, overlays, and references are loaded by the router; do not eagerly read them.