Deal Lifecycle

Create, advance, and close deals in the Buildr CRM via MCP write actions.

1|Updated May 17, 2026
One-click install
npx skills add https://github.com/Envision-Construction/Envision-Skill-Repo --skill deal-lifecycle-envision-construction
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Deal Lifecycle
Source: https://github.com/Envision-Construction/Envision-Skill-Repo/tree/main/plugins/construction/buildr/skills/deal-lifecycle
Command: npx skills add https://github.com/Envision-Construction/Envision-Skill-Repo --skill deal-lifecycle-envision-construction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Business development teams need to act on deal records in Buildr — creating opportunities, moving stages, marking deals won or lost — without manually navigating the CRM or risking invalid writes like invented stage names or wrongly typed values. ## Core Features & Use Cases - Deal Creation: Resolves or creates the associated company first, then creates the deal with correctly typed value, stage, and company_id parameters. - Stage Transitions: Looks up the real pipeline stage list before calling deals.move_stage so only valid stage names are used. - Win/Loss Closeout: Marks deals won with optional won_value or lost with a captured reason, with mandatory user confirmation before these terminal writes. - Field Updates: Updates value, owner, or probability with schema-correct types (value as string, probability as integer 0-100). - Use Case: A user says "we won the Marina Vista deal at 158M" — the skill resolves the deal, confirms the final number, calls deals.win with won_value, and offers to spin up the project record. ## Quick Start Ask the assistant to create a new deal in Buildr for a named company with a value and stage, or to mark an existing deal won or lost.

Frequently Asked Questions about Deal Lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new deal in Buildr CRM?▼

Creating a deal in Buildr uses the deals.create write action with name, value, company_id, and stage parameters. The company is resolved or created first so pipeline analytics stay meaningful, and the value must be sent as a string.

How do I mark a deal won or lost in Buildr?▼

Marking a deal won or lost uses the dedicated deals.win and deals.lose actions, which are terminal and remove the deal from open-pipeline rollups. The skill confirms the deal name, value, and loss reason with you before executing.

Can I move a deal to any stage name in Buildr?▼

No, the stage parameter must match an existing pipeline stage exactly. The skill fetches the current stage list via the pipeline read action first so it never proposes an invented stage name.

Why does my Buildr deal update fail with a type error?▼

Deal updates fail when value is sent as a number instead of a string or probability is sent as a float or string. The write schema forbids extra fields and requires value as a string and probability as an integer from 0 to 100.

Can I set a deal to won using a generic update call?▼

No, won and lost are typed-only verbs with no equivalent in the generic deals.update action. You must use deals.win or deals.lose to transition a deal out of open status.