feat(community): add PM SOP Library skill — Owner Leads, Move-Outs, Lease Renewals

[willierobert213-star]

Summary

Adds a new community skill providing standard operating procedures for property management companies.

• Owner Leads SOP — 7-step workflow from lead capture through signed PM agreement (CRM logging, qualification, CMA, proposal, follow-up cadence, objection handling, onboarding handoff)
• Move-Outs SOP — 6-step workflow from notice received through unit turnover (pre-move-out comms, inspection, vendor dispatch, security deposit disposition)
• Lease Renewals SOP — 5-step workflow from 90-day identification through lease execution

All SOPs are fully genericized — no company-specific names, board IDs, fees, or personnel. Designed as a starting-point template that any PM company can customize for their tools and local law.

Agent Usage

Agents can reference these SOPs when:

• Answering owner/tenant questions about process
• Drafting communications at each stage
• Routing decisions to the right team member
• Training new team members on standard workflows

Test plan

• Read SKILL.md — all three SOPs present and complete
• Verify no company-specific references (board IDs, personnel names, proprietary tool references)
• Confirm jurisdiction notes are generic (not state-specific mandates)
• Confirm pipeline stage reference tables are accurate

🤖 Generated with Claude Code

[noogalabs]

We opened both parts of this PR. The PM SOP library contains useful operational prose, including the owner-lead qualification/CMA sequence, the move-out inspection-to-deposit flow, and the 90/60/30-day renewal cadence.

We are not merging the branch because current main now contains a fuller 18-file turnover-coordinator with CLAUDE.md and an experiments structure, while this PR carries a stale 13-file version that differs across 12 overlapping content files and omits those surfaces. Current main also has machine-readable owner-lead, move-out, turnover, deposit-disposition, renewal-prefill, and holdover SOPs, so the PM SOP library duplicates an existing workflow surface.

The outcome is report-only: preserve and credit any useful prose deltas, but do not merge the stale agent or a second competing SOP library. Three days with no human response was already too long; a specific no with the evidence is what we owed you.

[noogalabs]

Thanks for putting this together - the SOP content itself is squarely on-mission. Two things need resolving before code review:

1. The diff is larger than the description. Alongside the pm-sop-library skill, this branch carries a full 13-file community/agents/turnover-coordinator/ template that the PR body doesn't mention - and main already has that directory, which is the source of the conflicts. Those files would need to be dropped from this PR (main's version wins) or proposed separately with their own description.
2. Placement decision on our side: main's sops/ hub now has 47 structured SOP templates covering much of this ground (owner-lead-nurture, move-out-deposit-disposition, move-out-inspection, lease-renewal-prefill, turnover-make-ready). We need to decide whether new SOP content lands there as structured templates or as skills - we'll make that call and follow up here so your content lands in the right shape rather than duplicating.

So: on hold for that decision, not declined. Thanks for contributing!