Workflows that start with a question.
Pick your role, pick a prompt. Floatable pulls the context from the codebase and pushes the result to Linear, Slack, Notion, Jira or wherever your team works.
Product managers
"We're seeing drop-off here. What changed recently? If something broke, create a ticket in Linear and let #product know on Slack."
"Summarize what shipped this sprint in plain language and post it in Slack. Include who changed what and anything that affects users."
"Did this feature grow or shrink compared to the original spec? Document what changed in Notion."
"Is this feature done? Look for missing states, empty views, and unhandled errors — create a ticket in Linear for anything that's missing."
Designers
"This doesn't look right. What changed visually since the last deploy? Open the component in Cursor so I can check the styling."
"Is this using the right design tokens such as spacing, colors and typography? Flag anything hardcoded and open it in Cursor."
"Were any UI changes made here without designer input? Post what changed in #design on Slack."
"How does this component behave on mobile and tablet? Flag any breakpoint issues and create a ticket in Linear."
QA
"What edge cases aren't handled here? List them by severity and create Jira tickets for anything high or critical."
"Write test cases for this function and cover both the happy path and failure scenarios. Open the test file in Cursor so I can review."
"This was AI-generated. What's most likely to break? Document the risk areas in Confluence."
"What code paths in this change aren't tested? Create a test plan in Notion with the minimum set of tests to cover them."
Support
"A customer reported this isn't working. What's going on in the code? If it's a real bug, create a ticket in Linear and notify #support on Slack."
"Is this a known issue? Check if there's already a ticket for it. If not, create one in Jira ."
"We need a temporary workaround for this issue. Look at how it works and write up a workaround in Notion that support team can share with customers."
"This customer issue needs engineering attention. Summarize the problem with the relevant code context and post it in #engineering on Slack."
Developers
"Review this PR for maintainability — naming, patterns, structure. Post the review as a comment on GitHub."
"I didn't write this. Walk me through what it does and why it was built this way. Write a guide and add it to Notion"
"Will this work in production? Check for hardcoded values, missing env variables, and anything that only works locally. Create a ticket in Linear for anything blocking."
"What's causing this to break? Explain the issue and open the file in Cursor so I can fix it."