Summarize backlog prioritization outcomes into a clear ranked list and key tradeoffs. Use it when you need a record of what moved up, what moved down, and why.

Write a concise engineering update for a team or project over a time window. Use it when you need a consistent format for leadership or cross-functional stakeholders.

Draft a concise feature brief from a rough idea or notes. Use it when you need a lightweight artifact that aligns product, design, and engineering. 167 ---

Summarize an incident report or incident ticket into a clear post-incident brief. Use it when you need to share what happened, impact, and next steps quickly.

Generate a PR review checklist and questions based on a ClickUp task’s goal and requirements. Use it when you want consistent review quality tied to acceptance criteria.

Generate “Went well / Didn’t / Try next” retro inputs using recent activity signals. Use it to start a retro with data, not opinions.

Summarize a roadmap into a concise, stakeholder-friendly overview. Use it when you need to communicate priorities, sequencing, and open questions quickly.

Summarize sprint planning inputs and outputs into a clear recap. Use it when you want a record of what was committed, what was deferred, and what risks were raised.

Summarize what changed and what shipped during a sprint for a specific list/folder/space. Use it when preparing sprint review notes or an executive readout.

Generate a daily standup update for one or more engineers based on ClickUp activity in a defined time window. Use it when you want a consistent standup format without manually collecting updates.

Create a well-formed technical spike task (research/experiment) with clear scope, deliverables, and timebox. Use it when engineers need aligned exploration work. instructions 28 --- • • Pu...