Dev Request Brief
[ DEV REQUESTS ]
Dev Request
Dev Request
Brief
Every dev task starts here. Fill in the seven lines below and send it our way.
A complete brief gets queued same-day. A vague one costs a round of back-and-forth.
Copy this, paste it into your channel, fill in each line.
[ DEV REQUEST ]
What needs to happen: the outcome, not the how
Where: page / template, and desktop / mobile / both
Editor link: Shopify editor or page URL, if applicable
Product link: Shopify product URL or specific variant URL, if applicable
Deadline + priority: DATE, and low / med / high
References: Figma, Loom, screenshots, example URLs
Edge cases / must-haves: anything that should or shouldn't happen, e.g. "hide on out-of-stock variants"
on your message means we've seen it and queued it.
[ HOW TO USE IT ]
Three quick rules
One request per message. Each task gets its own brief, in its own thread. Keeps scope clear and nothing gets buried.
Tell us the outcome, not the build. Describe what should happen for the shopper. The "how" is our job.
Links beat descriptions. A Loom, a Figma frame, or a screenshot with an arrow saves more time than three paragraphs.