Results for “team-analysis”

Designs high-performing team structures using organizational psychology AND creates new skills on-the-fly when team needs unmet expertise. Expert in team composition, personality balancing, collaboration ritual design, and skill creation for missing capabilities. Use for team design, role definition, skill gap identification. Activates on 'team building', 'team composition', 'skills needed', 'what skills'. NOT for general project management or solo work planning.

Coaching Analyst

Provides a structured workflow for reverse engineering .NET and C# binaries, including deobfuscation with de4dot, static analysis via dnSpyEx IL view, dynamic debugging, and reliable IL patching for red-team tools and malware.

Conversation Analyst

Derives a comprehensive test plan and writes unit, integration, and end-to-end test cases from user stories and acceptance criteria, flagging issues in prior artifacts and declaring UAT readiness.

Use when team expertise is needed to unblock implementation decisions.

Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

Analyze closed deals and lost opportunities for patterns

Compose a provider-neutral AI team by tiering accessible models on cost-efficiency, capability, latency, and governance, then mapping the 8 processkit role archetypes onto catalog Roles + RoleSlots inside a chartering Scope. Use when bootstrapping a new project team, rotating after a provider change, or quarterly rebalancing. Triggers: "create my AI team", "compose a team", "rebalance the team", "review the team".

Weekly engineering retrospective. (gstack)

Design and evolve engineering team structures for fast flow of change using the Team Topologies framework, including Conway's law, four team types, three interaction modes, and cognitive load management.

Establish team norms for collaboration and communication. TRIGGERS - Use when user needs help with team-norms related tasks.

Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations. Use when doing strategic assessment, competitive analysis, or evaluating a product or business position.

Plan team outings with activities and logistics. TRIGGERS - Use when user needs help with team-outing related tasks.

Weekly engineering retrospective. (gstack)

Conduct gap analyses between current and desired states. TRIGGERS - Use when user needs help with gap-analysis related tasks.

Plan team outings with activities and logistics. TRIGGERS - Use when user needs help with team-outing related tasks.

Conduct gap analyses between current and desired states. TRIGGERS - Use when user needs help with gap-analysis related tasks.

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

Establish team norms for collaboration and communication. TRIGGERS - Use when user needs help with team-norms related tasks.

Guide teams through MITRE's Problem Framing Canvas to clarify problem statements before jumping to solutions.

Turn churned and downgraded accounts into an early-warning system. Reads the customers who left or shrank, extracts the themes behind why, builds a warning checklist from the real causes, then reads your active book and flags which accounts look like the ones that just churned. Built for B2B retention teams, customizable to your CRM and your customer data. Trigger on "why do customers churn", "what do churned accounts have in common", "build me a churn early-warning list", "which accounts are at risk of churning", "who looks like a recent churner", or any retention post-mortem.