Turn a loose Slack ask into a shippable Brajko brief.
Use this page when you know what you want but not how to phrase it. It keeps the request public-safe, concrete, and easy for Brajko to turn into code instead of clarification loops.
Five things every Brajko request should include
Outcome
State the result you want, not just the thing you think needs changing.
Target
Name the exact page, template, or feature so Brajko knows where to work.
Constraints
Call out what must stay the same: style, tone, links, or legal guardrails.
Acceptance
Say how you’ll know it is done so nobody has to guess after the build lands.
Safety
Leave private details out. Brajko only needs the public-safe version to move fast.
A clean brief you can paste into Slack
Keep the wording short. The template does the heavy lifting.
Slack brief skeleton
Update /brajko.html with one clear change. Goal: [what should improve] Target: [page or feature name] Keep: [style, links, tone, legal guardrails] Add: [new section, CTA, or helper] Done when: [simple acceptance check] Please keep it public-safe and production-ready.
Ready to copy.
“Add a Request Builder link to the Brajko page so people can turn vague asks into a clear brief.”
“Rewrite the CTA area to point people at the case study, the playbook, and the request builder.”
“Do not include client names, private details, or internal-only information in the copy.”
"If the request is clear enough to verify, it is clear enough to ship."
Brajko Request Rule
Need the agent page too?
The Request Builder helps you ask better. The Brajko page shows the agent. The case study shows the proof.