Get a status update on a feature
Prompt detail
Read the {{Slack channel}} and review all tickets related to {{Feature name}}.
Summarize the current status of the feature, including:
● Completed work: tasks or milestones that have been finished
● In-progress work: items currently being worked on
● Upcoming milestones: next planned steps or deadlines
Identify any blockers, risks, or issues affecting progress, and describe the actions being taken to resolve them.
Incorporate any relevant feedback, decisions, or insights shared by the team, and present the summary in a clear, structured format.
What the prompt does
Engineering teams constantly juggle Slack threads, ticket boards, and meeting notes to understand where a feature stands. Manually piecing together status updates from scattered sources wastes time and risks missing critical blockers or decisions.
With remio, you specify a Slack channel and feature name, and it reads through relevant messages and linked tickets to produce a structured progress report. The output covers completed milestones, in-progress tasks, upcoming deadlines, active blockers, and team decisions — all organized in a format ready for standups, stakeholder updates, or sprint reviews.
When to use
• Preparing a weekly engineering status update for leadership without manually scanning dozens of Slack threads and Jira tickets.
• Onboarding onto a feature mid-sprint and needing a fast snapshot of what's done, what's blocked, and what's next.
• Running a sprint retrospective and wanting an objective timeline of how a feature progressed, including decisions and pivots.
• Briefing a product manager or cross-functional partner who needs a clear summary before a planning meeting.
• Escalating a blocked feature by compiling evidence of delays and unresolved dependencies into one document.
Prompt examples
Input: Read the #payments-v2-eng channel and review all tickets related to Stripe Connect onboarding flow.
remio responds:
Completed work: The merchant identity verification UI was shipped on June 3rd, and the backend webhook handler for Stripe account.updated events was merged and deployed to staging. In-progress work: Sarah is finalizing the payout scheduling logic (PAYS-214), and Marcus is writing integration tests for the connected account creation endpoint. Upcoming milestones: QA regression testing is scheduled for June 12th, with a production rollout targeted for June 17th. Blockers: The team flagged a dependency on the compliance team's KYB review template, which is two days overdue — Jake escalated this in #compliance-requests on June 5th and is awaiting a response. A decision was made on June 4th to defer multi-currency support to v2.1 to keep the launch timeline intact.
Tip 1:
Specify the exact date range in your Slack channel reference (e.g., "#payments-v2-eng from the last 2 weeks") to avoid pulling in outdated discussions that dilute the summary.
Tip 2:
Include the ticket prefix or project key (e.g., "PAYS-*") alongside the feature name so remio can match tickets more precisely across your issue tracker.
Tip 3:
Ask remio to tag each blocker with severity and owner so the output is immediately actionable in your next standup or escalation thread.
More tips
remio meets all your needs about knowledge
Learn more features
Capture resources from websites, local folders & files.
Get instant, reliable answers from your entire knowledge base.
Your working assistant, on desktop, browser, and mobile.
Unlimited free recording and transcription, no-bot.