Results for “feedback-management”

Design 360-degree feedback programs with surveys. TRIGGERS - Use when user needs help with 360-feedback related tasks.

Design 360-degree feedback programs with surveys. TRIGGERS - Use when user needs help with 360-feedback related tasks.

Designs and reviews feedback loops for AI agents to ensure goals are machine-decidable, loops are damped, and human judgment is preserved.

Collecting user feedback via NPS surveys, review analysis, sentiment analysis, feedback classification, and insight extraction reports. Use when establishing feedback loops.

Design pulse surveys for rapid employee feedback. TRIGGERS - Use when user needs help with pulse-survey related tasks.

当在线业务的一个环节（如产品、内容）运行后，需要系统性地收集反馈并驱动整体优化时

当遭遇挫折、失败或结果不如预期时，用于将负面经验转化为成长燃料

Design pulse surveys for rapid employee feedback. TRIGGERS - Use when user needs help with pulse-survey related tasks.

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

Send Structured Feedback to the Framework Maintainers

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.

Provides a structured protocol for receiving and evaluating code review feedback, emphasizing technical verification over performative agreement.

Reviews and tailors Product Manager resumes against 10 best practices including the XYZ+S formula, keyword optimization, and job-specific customization.

Code Review Reception

Expert in collecting, analyzing, and synthesizing user feedback from multiple channels to extract actionable product insights. Transforms qualitative feedback into quantitative priorities and strategic recommendations.

Guides technical evaluation of code review feedback, emphasizing verification before implementation and reasoned pushback over performative agreement.

Resolve GitHub PR feedback end-to-end for the branch you are on. Use when you need to fetch all comments on the branch PR, evaluate whether each comment still applies, decide whether it should be addressed, implement fixes, run compile/tests with retry-on-failure, then commit and push the result.

Update or correct an existing skill file based on judge feedback or improved understanding.

Package a customer escalation for engineering, product, or leadership as a decision-ready handoff — impact, timeline, facts vs. hypotheses, and a specific ask with an owner.

Design interaction flows, states, and microinteractions for usability and feedback clarity. Use when: (1) defining flows, (2) state/error handling, (3) reducing cognitive load. NOT for: final code implementation.

Guides technical verification of code review feedback before implementation, emphasizing reasoned pushback over performative agreement.

Provides patterns for robust error handling across TypeScript, Python, and Go, covering typed errors, error boundaries, retries, circuit breakers, and user-facing messages.

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

Use when reviewer comments arrive and each one needs a tracked decision, when a revise and resubmit letter must map every comment to a manuscript change, or when contradictory reviewer demands need evidence-based, editor-facing framing.

Analyze complex systems through stocks, flows, and feedback loops to find high-leverage interventions. For organizational, environmental, social, and technical systems exhibiting circular causality. NOT for linear problems or simple cause-effect chains.

Synthesize retrospectives into themes, root causes, decisions, and team improvements.

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.