When you hand over a whole design instead of one change, droost adds a step before any building: the intake. It turns "build me a site from this" into a plan you have read and approved.

Start it

Put the design in the project (a zip, a folder, or a URL where it is served) and tell the agent:

text
/droost:workflow:intake build me a site from design/our-site.zip

No run can open while an intake is open, so nothing gets built yet.

What happens

  1. droost reads the design. A tool called droost-source opens it in a browser and lists what is there: the pages, the menus, the repeated blocks (cards, lists), the forms, the images, the data. This reading is recorded where the agent cannot change it.
  2. The agent writes a model. For every part of the design it decides what it becomes in Drupal (a content type, a block, a menu, a setting), and it writes down what it will not build.
  3. It asks you questions. Only the things the design cannot tell it: who edits what, where form submissions go, what is real content and what is a placeholder, what is out of scope. Each question comes with a recommendation you can just accept.
  4. It writes a roadmap. The site broken into small steps, called rungs, each with its own ticket. Each rung builds on the one before.
  5. You approve it. The agent asks "Approve this roadmap?". Answer "Not yet" with what is missing, and it revises the plan. Only your yes approves it.

droost checks the paperwork before you are asked (droost workflow:intake check): every page and form in the design is either planned or set aside, every question has your answer on record, and the rungs are in order.

Then build it, one rung at a time

Each rung is a normal run:

text
/droost:workflow:start build rung 1: droost/intake/tickets/R01.md

Finish one, review and commit it, then start the next.

Holding the site to the design

If you want droost to check the site still looks like the design, capture the design's pages once, before the first rung. This is the parity gate. See Parity.

What you get in the repository

text
droost/intake/model.md       what each part of the design becomes
droost/intake/questions.md   your questions and answers
droost/intake/roadmap.md     the rungs, in order
droost/intake/tickets/       one ticket per rung

These stay in git, so anyone can see why the site was built the way it was.