Deal to Project

Convert a won Buildr deal into an operational Buildr project record.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a deal closes, teams often fumble the BD-to-ops handoff: project records get created late, duplicated, or with inconsistent naming, and downstream systems like accounting and scheduling inherit the mess. This Skill standardizes the conversion of a won Buildr deal into a Buildr project record so nothing falls through. ## Core Features & Use Cases - Won-deal verification: Resolves the named deal via the Buildr MCP gateway, confirms it is closed-won, and asks before promoting an open deal. - Duplicate prevention: Checks for existing projects on the same company before creating a new record. - Field mapping and write: Maps deal name, company_id, and value into the narrow projects.create schema (name, description, company_id), confirms with the user, then writes. - Backward linking: Adds a note on the originating deal pointing at the new project id for auditability. - Use Case: After hearing "we won the Marina Vista job," the Skill finds the won deal, confirms no project exists for that company, creates the project record, and logs the handoff note on the deal. ## Quick Start Ask the assistant to convert the won Marina Vista deal in Buildr into a project and kick off the operational handoff.

Frequently Asked Questions about Deal to Project

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

FAQPage Schema
How do I convert a won deal into a project in Buildr?▼

Resolve the deal with buildr_read, verify its status is won, check for existing projects on the same company, then call buildr_write with resource projects and action create. Confirm the project name with the user before writing, since it propagates to accounting and scheduling.

What fields can I set when creating a Buildr project?▼

The projects.create write schema accepts only name, description, and company_id, with extra fields forbidden. For additional fields like project_type, dates, or value, create the record first and follow with a projects.update call if the gateway schema supports it.

Does the skill create a project if the deal is still open?▼

No. If the deal status is not won, the skill asks the user before promoting it, since some teams create projects at signature and others at contract notice. It also lists existing projects for the company to avoid duplicates.

Should the deal value become the project budget in Buildr?▼

Not automatically. Won deal value may differ from the project budget, so the skill asks whether to carry deal.value into the project description or establish a fresh budget instead of assuming they match.

What happens after the Buildr project is created?▼

The skill surfaces the new project_id and adds a note on the originating deal linking to it. It then suggests next operational steps such as Procore project creation, Sage job setup, or seeding kickoff tasks via activity logging.