Design Briefs
The brief a client gives you is almost never a brief. It is a paragraph that says “modern but timeless” and a deadline. The real information exists — it is scattered across a discovery call, an old deck, a competitor they mentioned once — but assembling it into something you can design against is an hour of unbilled work you do at 11pm. So you skip it, start designing on assumptions, and find out in round two which ones were wrong.
Skynet does the assembly. Give it the transcript and the thread, and it drafts a structured brief from what is actually there — then marks the gaps explicitly instead of papering over them. The judgment about what makes a good direction stays with you. The transcription work does not.
How it works
Dump in the raw material
Call recordings, email threads, the client’s existing site, a Pinterest board, that half-finished doc. Skynet reads all of it and holds it as one project memory rather than a folder you have to re-read.
Draft against your brief template
Every studio has a brief shape that works. Teach Skynet yours once — audience, objective, tone, deliverables, constraints, success criteria — and it fills each section from the source material, citing where each line came from.
Name the gaps out loud
The most useful part of the draft is the list of what is missing. Budget unstated, no decision-maker named, deliverable count vague. Skynet writes the open questions as questions you can paste straight into a reply.
Approve, then reuse
You edit the draft into something you would actually sign, and it becomes the reference point for the project. Every later task — scope, feedback, handoff — reads from the same brief instead of a fresh guess.
Build it from a prompt
One instruction sets up the whole kickoff step.
You walk into the project with direction instead of vibes, and the client gets asked the hard questions on day one rather than in round three. The brief takes ten minutes instead of an evening, and it is written from what was actually said.