guildly

The workspace

Ideas

The ideas tab is a low-friction inbox for anything you want built or fixed, without starting a conversation about it.

When to use ideas instead of chat

Chat is for things you want to discuss or want moving now. Ideas is for the stream of thoughts you have during the day: a bug you noticed on your phone, a feature that would be nice someday, a wording change. Drop it in the inbox and move on. Nothing gets lost, and you didn't have to write a proper request.

Capturing an idea

The composer asks one question: "What should the team build or fix next?" Describe it, set the type (feature, fix, and so on), and attach a screenshot if you have one. A screenshot of a broken layout says more than a paragraph.

When you submit, you pick how it gets handled:

  • Auto-pick: agents grab it on their own and start working. No nudge needed. Use this for clear, self-contained items.
  • Backlog: it's parked until you ask the manager to pick it up. Use this for someday-maybe ideas you don't want the team burning time on yet.

The lifecycle

Ideas move through three states: open (waiting), picked up (the team turned it into real work, a PRD or tickets), and shipped. The tab has two views, Active and Shipped, so you can see what's in flight and scroll back through everything that made it out the door.

Tip:treat the ideas inbox like a notes app that happens to have an engineering team behind it. The cheaper it is to capture a thought, the more of them you'll actually capture.