The agent team

Every Orchpad project is handled by a team of specialized agents:

• Director — breaks down your brief into a plan, assigns work to Builders, and coordinates the build
• Builder agents — execute the actual work in parallel: writing code, building pages, wiring logic
• RO (Release Officer) — reviews the finished build before deployment and runs checks

You interact primarily with the Director. The Builders and RO work in the background.

How to give good instructions

The agents work best when instructions are:

• Specific — describe the exact outcome, not the general idea
• Scoped — one clear thing per instruction, not five things at once
• Outcome-focused — say what you want to exist, not how to build it

You don't need technical language. "Add a contact form that emails me when someone submits it" is a complete, good instruction.

When to redirect vs. iterate

If the agents built something close but not quite right — iterate. Submit a correction as a new instruction.

If the agents built something fundamentally different from what you meant — redirect. Go back to the Director with a clearer description of the original intent.

What agents can't do

• They can't read your mind — vague instructions produce vague results
• They can't access external systems without credentials you provide (e.g. API keys for third-party services)
• They won't deploy without your explicit approval