rcode-nasser-eng-manager

Prepare 1:1 notes, hiring plans, and burnout checks for engineering managers.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-nasser-eng-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rcode-nasser-eng-manager
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/agents/nasser-eng-manager
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-nasser-eng-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineering managers handle the people side of software teams without losing structure, empathy, or follow-through. It is designed for 1:1s, hiring, onboarding, growth plans, performance conversations, burnout checks, and team composition decisions.

Core Features & Use Cases

  • 1:1 Preparation and Follow-up: Build Work, Growth, and Life discussion notes, then capture action items for future check-ins.
  • Hiring and Onboarding Support: Draft role expectations, interview loops, sourcing plans, and onboarding guidance for new engineers.
  • Performance and Team Health Management: Identify root causes behind missed deadlines, surface burnout signals early, and frame feedback around observable behavior.
  • Use Case: A manager can ask for help preparing a 1:1 with an engineer, designing a hiring plan for a new backend role, or diagnosing whether a velocity drop is caused by scope, burnout, or a real performance issue.

Quick Start

Ask Nasser to prepare a 1:1, hiring plan, growth plan, or burnout check for a specific engineer or team.

Frequently Asked Questions about rcode-nasser-eng-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a structured 1:1 meeting for a software engineer?

Prepare a 1:1 for a software engineer by structuring notes across Work, Growth, and Life categories, then capturing action items for future check-ins. This ensures clear follow-through on engineering team management discussions.

How do I create a hiring and onboarding plan for a new backend engineer?

Create a hiring plan for a new backend engineer by drafting role expectations, interview loops, and sourcing plans. Onboarding guidance is then generated to integrate the new engineer into the team with clear day-one structure and expectations.

What is the best way to diagnose a sudden drop in team velocity?

Diagnose a drop in team velocity by identifying root causes behind missed deadlines, checking whether the issue stems from scope creep, burnout signals, or a real performance issue requiring behavioral feedback and management intervention.

How do I conduct an early burnout check for my engineering team?

Conduct an early burnout check by surfacing behavioral signals and team health indicators to identify root causes of stress. This helps frame feedback around observable behavior before missed deadlines or velocity drops occur.

Can I use this for bilingual engineering organizations?

Yes, this applies to bilingual engineering organizations needing guidance on individual performance, team health, and staffing decisions across day-to-day management scenarios and squad design.

How do I frame feedback around observable behavior for performance reviews?

Frame feedback around observable behavior by using role-aware decision frameworks to structure performance conversations. This identifies root causes behind issues and ensures feedback remains structured, empathetic, and clear.