Skip to main content

​
How it works

Project Builder is an Expert, a specialized agent. Give it a feature brief, mockup, existing ticket, or rough design. It researches the relevant code and drafts a design for your review. On request, it breaks the reviewed design into ordered tickets with dependencies. The diagram shows the ticketed path: Ticket creation is optional. When you request implementation, Project Builder delegates the work to PR Author workers and coordinates delivery.

​
Where you participate

  • Define the outcome. Provide the problem, success criteria, constraints, and what is out of scope.
  • Review the design. You decide scope and architecture; the Expert researches options and explains tradeoffs. Resolve open questions before handing work off.
  • Choose the next step. Ask for tickets, implementation, or both. A design request alone is not permission to change code.

​
Template Experts

  • Project Builder researches, drafts designs, and breaks work into tickets; it can also coordinate delivery when requested.
  • PR Author implements and tests work you hand off after planning.

​
Set it up

  1. Connect your tools. Connect your code host and, for ticket creation, your tracker. Provide access to the relevant repositories and product context.
  2. Ask Cosmos Advisor to configure Project Builder. Tell it which code host and ticket tracker you use.
  3. Start Project Builder with a feature brief. Review its design and open questions, then decide whether to request tickets or implementation.
Example Advisor prompt:
Set up Project Builder for [code host] and [ticket tracker] to turn feature requirements into designs and tickets.

​
Next step

Use Ticket → PR to turn approved work into a draft change for review. Already have a clear ticket? Start there directly.

​
Further reading