How it works 

Your prompts don’t build anything directly. Instead, they are folded into a specification which is a written description of your solution broken into user stories, each with the specific details that define how it should work. The specification is updated every time you prompt and defines what is built.  

Ed the Builder acts as Project Builder's foreman. He reads the specification, plans the work, and hands it to a team of specialist agents who build it. 

The data model is built first. Everything else is built on top of it, so describe your tables, fields, and relationships before anything else. After that, order matters much less. 

What matters most 

If you leave something out, Project Builder doesn't stop and ask. It picks a reasonable default, writes it into your specification, and keeps going. Most disappointing results aren't Project Builder getting something wrong, they're Project Builder filling in a blank you left. 

Structure 

  • Goal—What you want, in one sentence.
  • Context—The objects, fields, and relationships involved.
  • Details—Rules, roles, and anything else that matters.

Example prompt: Create a Purchase Requisition solution for Requisition (RequisitionNumber, Requester, CostCenter, Status, TotalAmount) and RequisitionLine (ItemDescription, Quantity, UnitPrice). Requesters create and submit; Approvers approve or reject. Requisitions can't be submitted with zero lines. 

Prompts for agents follow the same structure. The goal is the job the agent does, the context is the project data it works with, and the details are the requests it should handle and how it should respond. If you want the agent to work with your project's data, build the project first.

Example agent prompt: I want an agent for this project that can answer these types of questions about Requisitions and RequisitionLines. It should handle requests like these. How many open Requisitions does Engineering have, and what's their total amount? Which Requisitions are waiting on a Finance Approver, and how long has each been waiting? Create a new Requisition for ten laptops from Example Vendor Inc for Engineering. Change the quantity on the laptop line of REQ-1042 to 12. When it gives a number, it should list the Requisitions behind it.

Tips 

  1. Be specific about what elements you want to change. "That screen" and "the status thing" force a guess; "the Requisition Detail page" and “the Status field on Requisition” don't.
  1. Say what you want, not what you don't want. "Don't make it cluttered" leaves the choice to Ed the Builder. "Show five columns: RequisitionNumber, Requester, Status, TotalAmount, SubmittedDate" doesn't.
  2. Limit the number of changes in each prompt. Eight requests in one prompt fail in ways you can't diagnose. Smaller prompts, reviewed in between, get you there faster and let you roll back exactly the one that went wrong. The same goes for agents, so tune one behavior at a time.
  3. Not sure what to include? Ask it to ask you. End with: "Ask me any questions you need in order to fully understand what I want before you build anything." Cheapest, most effective technique here.
  4. Building an agent? Describe the requests it should handle and list real examples with real names. "REQ-1042" and "Engineering" teach it more than "a Requisition" and "a department." Include questions and actions if you want the agent to do both.
  5. Say how an agent should respond. For example, "When it gives a number, it should list the Requisitions behind it."

Checkpoints 

A checkpoint is a full snapshot you can roll back to at any time. Project Builder creates one automatically each time a prompt finishes, so if a prompt doesn't go the way you wanted, select Undo in the chat input to jump back to the checkpoint from right before it. Project Builder keeps the 50 most recent automatic checkpoints, so mark any checkpoint you want to keep permanently as Keep this Version. 

More Example Prompts 

  • Debugging a button: "On the Requisition Detail page, the Submit button doesn't do anything when I click it. Save works fine on the same page and does persist my changes. Submit should also change Status to Submitted."
  • Adding fields: "Add a Notes field to Requisition. Show it on the Requisition Detail page and add it as a column on the Requisition List page."
  • Generating sample data: "Generate 10 sample Requisition records with RequisitionLines. Make sure at least half have a Status of Submitted, since that's what the default view filters to."
  • Brainstorming with Ed: "How would you approach adding multi-level approval to Requisition? Requisitions over $5,000 need a second approval from a Finance Approver. Don't build anything yet. Walk me through what you'd change."
  • Building an agent: "I want an agent for this project that can answer these types of questions. It should handle requests like these."
    • How many open Requisitions does Engineering have, and what's their total amount?
    • Which Requisitions are waiting on a Finance Approver, and how long has each been waiting?
    • Create a new Requisition for ten laptops from Example Vendor Inc for Engineering.
    • Change the quantity on the laptop line of REQ-1042 to 12.
    • Add a Customer Success cost center owned by Dana Whitfield.
    "When it gives a number, it should list the Requisitions behind it."
  • Building a standalone agent: "Create an agent that helps me draft a polite follow-up email when I paste in notes from a customer call."
  • Using an agent in chat: "Put the Requisition agent under Ed so I can use it in chat."
  • Running an agent from a button: "Create a logic block that calls the Requisition agent. Send it a message asking it to review the Requisition the logic block runs on for likely duplicates. Add a button to the Requisition Detail page that runs it."
  • Teaching an agent: "Teach the Requisition agent to handle requests like these. Which Requisitions have no RequisitionLines? Change the CostCenter on REQ-1042 to Marketing."
  • Fixing an agent: "When I ask the Requisition agent which Requisitions are waiting on a Finance Approver, it also returns Requisitions that are already Approved. It should only return Submitted Requisitions over $5,000."