Start here

Your first request

You don't write specs or tickets to get work done. You write a chat message to the manager, the way you'd message a teammate.

Just tell the manager

Open the general tab, type @, pick the manager, and describe what you want in normal words:

• "@manager update the landing page, remove the waitlist section and link to the download page instead"
• "@manager our site is getting spammed with fake signups, can you look into it and stop it"
• "@manager add web analytics so we can see downloads"

You don't need to know which file to change or which engineer should do it. That's the manager's job. It reads your message, creates a ticket, assigns the right agent, and reports back in the same thread.

What a good request looks like

The single biggest lever on quality is saying what outcome you want, not how to build it. Compare:

• Vague: "improve the download page"
• Better: "on the download page, the Mac button is the main thing. If someone isn't on a Mac, show them a waitlist for Windows and Linux instead"

One request per message also helps. Three unrelated asks in one message tend to become one muddled ticket.

What happens next

1. The manager replies in a thread confirming what it understood.
2. A ticket appears in the tickets board and an engineer picks it up.
3. You can watch progress in activity, or just wait. The team posts updates in the thread.
4. When the work is built and reviewed, the ticket moves to Human Review and Guildly asks for your decision: approve, or request changes.

Checking in and course-correcting

You can ask "what's happening?" at any time and the manager gives you a status. You can also ask after the fact: "what changes did we make to handle the spam?" gets you a plain-English summary of everything that shipped.

If the result isn't what you wanted, say so bluntly. "This isn't what I asked for, the button is broken on mobile" is a perfectly good message. Agents don't have feelings to hurt, and a direct correction gets a faster fix than a polite hint.