New project from a brief
Write what you want made, and let Mastery HQ do the setup. One command creates the project folder, opens a window for each agent the brief names, gives them the rules they need, sends them the brief, and opens the Files window where the results appear.
The command
Section titled “The command”In the command bar, either of these:
new project from C:\Users\you\Desktop\brief.mdopens a brief you saved as a file.start a project: Lumen. Goal: a private cycle tracker. Deliverables: overview.md and app/index.html.takes the brief inline.
What a brief looks like
Section titled “What a brief looks like”# Purrfect Time launch
Agents: Writer, Builder (codex)
Goal: launch materials for a smartwatch for cats.
Deliverables:- Writer: positioning.md, a one-page positioning statement.- Writer: a hero image: [[image hero as hero.png: a sleek matte-black cat collar watch]]- Builder: app/index.html, a landing page that shows images/hero.png.- A launch reel: [[reel as launch-reel.mp4: a cat wearing the watch at dawn | Purrfect Time | voiceover: Know where your cat is, always.]]- The first heading (or first line) is the project’s name and its folder.
Agents:is optional. Without it, one window named after the project does all the work.Brand:is optional too:Brand: Purrfect Time; colours #0A0C10 #FF5C1A #FFB27A; tone playful, warmbecomes the project’s own Brand Kit (name, then background, primary and accent colours, then tone). Every image, clip and reel in the project is styled and titled with it instead of the global brand in Settings → Brand.- Everything else is the brief. Address a line to an agent by name when the work should be split; otherwise every agent reads the whole brief.
What HQ adds
Section titled “What HQ adds”You never write the rules; HQ appends them to every copy of the brief:
- save everything in the project folder, and never create a nested one,
- name generated media with
asso pages reference it correctly, - plain prose without em dashes,
- finish with a manifest, one line per file made.
An existing window with the same name as an agent in the brief is reused and re-scoped to the project, so a second brief for the same team lands in a new folder without opening duplicate windows.
Frequently asked questions
Do I have to name the agents?
No. Without an Agents line the project gets one window named after the project. Add `Agents: Alex, Bo (codex)` to split the work across named windows; a brand in brackets picks the CLI, and anything unrecognised uses Claude Code.
Where do the files go?
In the project's folder inside the workspace, `projects/<name>/`. The Files window opens with the project so you can find them without knowing the path, and each agent ends its reply with a list of the files it made.
Can the brief ask for images and videos?
Yes. Write the directive where you want the media, for example `[[image hero as hero.png: a calm dawn sky]]` or `[[reel as launch-reel.mp4: ... | voiceover: ...]]`. The agents are told to name files with `as` so their pages reference them correctly.