Deal pipeline

Skill Fusion-Data-Company/bristol-os/plugins/bristol-os/skills/deal-pipeline

One-paste Claude setup that turns Claude into an institutional multifamily research & underwriting teammate for Bristol Development Group — zero-config, fully cited, self-evolving (V1→V2→V3).

Install

npx -y skills add Fusion-Data-Company/bristol-os --skill deal-pipeline

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Track deals across stages and produce status updates. Use when the user says "track this deal," "what's in my pipeline," "update the status on [deal]," "give me a pipeline summary," or wants an overview of what's moving.

SKILL.md

2.6 KB, as published. Nobody here has run it

Deal Pipeline

Keep a simple, living record of Bristol deals and produce clean status updates.

When to use

"Add this to my pipeline," "what's in the pipeline," "update [deal] to underwriting," "give me a pipeline summary for Monday."

Where it lives

A single file: bristol-os/pipeline.md in the workspace. Create it on first use.

Stages (Bristol deal lifecycle)

Sourced → Screening → Underwriting → IC/Approval → Capital Raise → Closing → Development → Lease-up → Stabilized → Disposition/Refi

For each deal track

Name / location / product & units
Stage + date entered stage
Owner (who at Bristol is driving it)
Next action + due date
Key open items / blockers
Link to the deal folder and latest memo

Operations

Add: append a new deal row/section.
Update: move stage, log the change with a date, update next action.
Summary: produce a grouped-by-stage overview, highlight what's stalled (no movement / overdue next action) and what needs a decision.
Whenever another play produces a deliverable for a deal, note it on that deal's pipeline entry.

Output

Updated pipeline.md, plus a readable summary when asked (e.g., a Monday update grouped by stage with a "needs your attention" section at top).

Live tracker artifact (build it for them — HARD LAW)

Bristol OS gives each person a live visual deal board they can reopen any time.

The first time pipeline is used (and during onboarding), build it for them: read bristol-os/templates/project-tracker.html and create a persistent artifact from it with the create_artifact tool (title it "Bristol Deal Tracker"). Don't tell them how — just make it and open it.
Tell them where it is and how to use it in one plain sentence: "I made you a live Deal Tracker — it's pinned in this conversation; click any card to update a deal, and it saves itself on your computer."
Keep it in sync: when a deal changes, update both pipeline.md and (when asked for the board) regenerate/refresh the artifact. The board saves deals in the browser, so it persists across sessions.
Never make the user build or find it themselves — you create it and point to it.

Guardrails

Keep it factual — reflect only what the user tells you or what's in the deal folders.
This is internal tracking; keep it in the workspace, never anywhere public.