Loading...
Loading...
Found 3 Skills
Find out which objections your outbound gets, how well your team handled them, and what to say next time. Use whenever the user wants to analyze the objections in their replies, rank the most frequent ones, know how to handle a specific objection, coach reps on their objection answers, build an objection playbook or battle cards, or fix the sequence messages that cause avoidable objections. Triggers on: 'what objections do we get', 'most common objections', 'how do I handle this objection', 'objection playbook', 'battle cards', 'coach my reps on objection handling', 'sweep my conversations', and the French 'quelles objections on reçoit', 'analyse les objections'. Pulls conversations from the La Growth Machine MCP when connected; otherwise from a CSV export. Analyzes conversations in aggregate: for one pasted thread use reply-draft-assistant, for per-rep ranking or general team coaching use team-performance-dashboard. For SDR, RevOps, Growth, Head of Sales and founders. Maintained by La Growth Machine.
Helps engineering managers diagnose team skill gaps and make better hiring and assignment decisions — produces the Dungeon Party archetype model (Warrior, Tank, Healer, Wizard, Rogue), the Barrels and Ammunition framework for understanding throughput limits, the Commandos/Infantry/Police phase model, and a minimum team size guideline. Use when the user says "team balance," "what roles do I need," "who should I hire next," "team is missing something," "skill gaps," "team is slow despite headcount," "this person thrived before but struggles now," or "what type of engineer should I hire."
Summarizes an RHDH sprint that has finished or is finishing, from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: committed versus completed story points, scope added mid-sprint, per-member breakdown, epic progress, the demo checklist with RHDH file and slide naming, and the velocity trend. Use for "sprint report", "what did we complete this sprint", "sprint review prep", "how did the sprint go", or "which demos do we owe". Looks back at work already done; preparing the sprint that has not started yet is a different job, and a single issue such as RHIDP-1234 is not a sprint.