{"id":"d45f8b03-fbb2-4d9b-ae3f-2be90ac132a5","entityType":"agent","slug":"clawhub-skills-1kalin-afrexai-engineering-manager","name":"Engineering Manager OS","canonicalUrl":"https://www.xpersona.co/agent/clawhub-skills-1kalin-afrexai-engineering-manager","canonicalPath":"/agent/clawhub-skills-1kalin-afrexai-engineering-manager","generatedAt":"2026-10-09T20:55:44.706Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":null},"description":"Complete engineering management system — team building, 1:1s, performance, hiring, architecture decisions, incident management, and scaling. From IC-to-manager transition through director-level operations. --- name: Engineering Manager OS description: Complete engineering management system — team building, 1:1s, performance, hiring, architecture decisions, incident management, and scaling. From IC-to-manager transition through director-level operations. metadata: {\"clawdbot\":{\"emoji\":\"⚙️\",\"os\":[\"linux\",\"darwin\",\"win32\"]}} --- Engineering Manager Operating System Your complete playbook for engineering leadership. Not ge","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. Last updated 4/15/2026.","installCommand":"clawhub skill install skills:1kalin:afrexai-engineering-manager","sourceUrl":"https://github.com/openclaw/skills/tree/main/skills/1kalin/afrexai-engineering-manager","homepage":null,"primaryLinks":[{"label":"View on ClawHub","url":"https://github.com/openclaw/skills/tree/main/skills/1kalin/afrexai-engineering-manager","kind":"source"}],"safetyScore":84,"overallRank":62,"popularityScore":50,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Complete engineering management system — team building, 1:1s, performance, hiring, architecture decisions, incident management, and scaling. From IC-to-manager "},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[{"label":"the","status":"self-declared"},{"label":"i","status":"self-declared"},{"label":"be","status":"self-declared"},{"label":"estimate","status":"self-declared"},{"label":"slack","status":"self-declared"},{"label":"you","status":"self-declared"}],"verifiedCount":0,"selfDeclaredCount":7,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"},{"key":"the","type":"capability","support":"supported","confidenceSource":"profile","notes":"Declared in agent profile metadata"},{"key":"i","type":"capability","support":"supported","confidenceSource":"profile","notes":"Declared in agent profile metadata"},{"key":"be","type":"capability","support":"supported","confidenceSource":"profile","notes":"Declared in agent profile metadata"},{"key":"estimate","type":"capability","support":"supported","confidenceSource":"profile","notes":"Declared in agent profile metadata"},{"key":"slack","type":"capability","support":"supported","confidenceSource":"profile","notes":"Declared in agent profile metadata"},{"key":"you","type":"capability","support":"supported","confidenceSource":"profile","notes":"Declared in agent profile metadata"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile capability:the|supported|profile capability:i|supported|profile capability:be|supported|profile capability:estimate|supported|profile capability:slack|supported|profile capability:you|supported|profile"}},"adoption":{"evidence":{"source":"no-adoption-signals","verified":false,"confidence":"low","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":"No source adoption metrics were available."},"stars":null,"forks":null,"downloads":null,"packageName":null,"latestVersion":null,"tractionLabel":null},"release":{"evidence":{"source":"agent-index","verified":false,"confidence":"medium","updatedAt":"2026-02-25T06:17:23.661Z","emptyReason":null},"lastUpdatedAt":"2026-04-15T00:45:39.800Z","lastCrawledAt":"2026-02-25T06:17:23.661Z","lastIndexedAt":null,"nextCrawlAt":"2026-02-26T06:17:23.661Z","lastVerifiedAt":null,"highlights":[]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install skills:1kalin:afrexai-engineering-manager","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T20:55:44.705Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-skills-1kalin-afrexai-engineering-manager/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":null},"readme":"---\nname: Engineering Manager OS\ndescription: Complete engineering management system — team building, 1:1s, performance, hiring, architecture decisions, incident management, and scaling. From IC-to-manager transition through director-level operations.\nmetadata: {\"clawdbot\":{\"emoji\":\"⚙️\",\"os\":[\"linux\",\"darwin\",\"win32\"]}}\n---\n\n# Engineering Manager Operating System\n\nYour complete playbook for engineering leadership. Not generic management advice — this is the specific system that high-performing engineering managers run daily.\n\n---\n\n## Phase 1: Team Architecture\n\n### Team Topology Assessment\n\nBefore managing people, understand the system they work in.\n\n```yaml\nteam_topology:\n  name: \"[Team Name]\"\n  type: stream-aligned | platform | enabling | complicated-subsystem\n  mission: \"[One sentence — what does this team exist to do?]\"\n  boundaries:\n    owns: [\"service-x\", \"domain-y\", \"pipeline-z\"]\n    consumes: [\"auth-service\", \"data-platform\"]\n    provides: [\"checkout-api\", \"payment-events\"]\n  cognitive_load: low | medium | high | overloaded\n  interaction_modes:\n    - team: \"[Other Team]\"\n      mode: collaboration | x-as-a-service | facilitating\n      friction: low | medium | high\n      notes: \"[What's working/not working]\"\n  current_headcount: N\n  ideal_headcount: N\n  skill_gaps: [\"observability\", \"mobile\", \"ML\"]\n```\n\n### Team Health Radar (Monthly)\n\nScore 1-5 for each dimension. Track trends over time.\n\n| Dimension | Score | Signal |\n|-----------|-------|--------|\n| **Delivery pace** | _ /5 | Are we shipping what we committed? |\n| **Quality** | _ /5 | Bug rate, incident frequency, tech debt trajectory |\n| **Collaboration** | _ /5 | Cross-functional work, PR review speed, knowledge sharing |\n| **Morale** | _ /5 | Energy in meetings, voluntary contributions, retention signals |\n| **Learning** | _ /5 | New skills adopted, conference talks, internal tech talks |\n| **Autonomy** | _ /5 | Can the team make decisions without waiting for me? |\n| **Psychological safety** | _ /5 | Do people raise concerns, admit mistakes, challenge ideas? |\n| **On-call health** | _ /5 | Page frequency, off-hours burden, burnout signals |\n\n**Action rules:**\n- Any dimension ≤2 → Address THIS WEEK (it's a fire)\n- Any dimension at 3 → Create improvement plan within 2 weeks\n- Overall average <3.5 → Team is struggling, block new commitments until fixed\n- Track quarter-over-quarter — sustained decline in any dimension = systemic issue\n\n### Team Composition Model\n\nThe ideal team has these roles covered (not necessarily 1:1 with people):\n\n| Role | Description | Gap Impact |\n|------|-------------|------------|\n| **Tech lead** | Architecture decisions, code quality bar | Decisions bottleneck through you |\n| **Senior IC** (2-3) | Carry complex work, mentor juniors | Velocity drops, quality suffers |\n| **Mid-level** (2-3) | Reliable delivery, growing scope | No bench for senior pipeline |\n| **Junior** (0-2) | Learning, fresh perspective | No talent pipeline |\n| **Domain expert** | Deep knowledge of the problem space | Constantly solving wrong problems |\n\n**Rule of thumb:** Never have >60% of team at same level. Mix creates natural mentorship.\n\n---\n\n## Phase 2: 1:1 System\n\n### 1:1 Cadence\n\n| Report Level | Frequency | Duration | Focus |\n|-------------|-----------|----------|-------|\n| Direct reports | Weekly | 30 min | Career + blockers + feedback |\n| Skip-levels | Monthly | 30 min | Team health + career + honesty check |\n| Your manager | Weekly | 30 min | Priorities + asks + air cover |\n| Cross-functional peers | Bi-weekly | 25 min | Dependencies + alignment |\n\n### 1:1 Template (Direct Reports)\n\n```yaml\none_on_one:\n  date: \"YYYY-MM-DD\"\n  person: \"[Name]\"\n  role: \"[Title]\"\n  tenure: \"[X months on team]\"\n  \n  # Their agenda first — ALWAYS\n  their_topics: []\n  \n  # Check-in (2 min)\n  energy_level: 1-10  # \"How are you feeling about work this week?\"\n  energy_trend: up | stable | down\n  \n  # Delivery (5 min)\n  current_work: \"[What they're working on]\"\n  blockers: []\n  help_needed: \"[What can I unblock?]\"\n  \n  # Growth (10 min — skip if urgent topics dominate, but never 3 weeks in a row)\n  career_conversation: \"[Topic discussed]\"\n  feedback_given: \"[Specific behavior → impact → request]\"\n  feedback_received: \"[What they told me]\"\n  stretch_opportunity: \"[Current or upcoming]\"\n  \n  # Action items\n  my_actions: []  # What I committed to do\n  their_actions: []  # What they committed to do\n  \n  # Signals (private — don't share these)\n  flight_risk: low | medium | high\n  performance_trajectory: improving | stable | declining\n  notes: \"[Anything notable]\"\n```\n\n### 1:1 Question Bank\n\n**Opening (rotate these — never use the same opener 3 weeks in a row):**\n- \"What's on your mind?\"\n- \"What was the best/worst part of your week?\"\n- \"If you could change one thing about how we work, what would it be?\"\n- \"What's something you're proud of from this week that I might not know about?\"\n- \"On a scale of 1-10, how's your energy? What would move it up one point?\"\n\n**Career development (monthly deep-dive):**\n- \"Where do you want to be in 2 years? What's the gap between here and there?\"\n- \"What skills are you not using that you'd like to use more?\"\n- \"Who in the org (or industry) has a role you'd want? What specifically about it?\"\n- \"What's the hardest technical problem you've solved recently? What did you learn?\"\n- \"If you left tomorrow, what would you regret not doing here?\"\n\n**Team health (probe with care):**\n- \"Who on the team do you learn the most from? The least?\"\n- \"Is there anyone whose work you don't trust to review?\"\n- \"What's something the team avoids talking about?\"\n- \"If you were me, what would you change about how this team operates?\"\n\n**Feedback solicitation (for YOU):**\n- \"What's one thing I could do differently that would help you most?\"\n- \"Am I giving you too much direction or too little?\"\n- \"Is there context I have that I'm not sharing that would help you?\"\n- \"When was the last time I frustrated you? What happened?\"\n\n### Flight Risk Detection\n\nMonitor these signals — if 3+ present, have a retention conversation within a week:\n\n| Signal | Weight | Detection |\n|--------|--------|-----------|\n| LinkedIn profile update | 🔴 High | Someone mentions it, or you notice |\n| Declining 1:1 engagement | 🔴 High | Shorter answers, less eye contact, \"everything's fine\" |\n| Stopped volunteering for projects | 🟡 Medium | Used to raise hand, now doesn't |\n| Increased PTO without travel | 🟡 Medium | Interviewing signal |\n| Disengaged in meetings | 🟡 Medium | Camera off, multitasking, no opinions |\n| Complaining shifted from specific to general | 🟡 Medium | \"This sprint is rough\" → \"This place...\" |\n| Stopped arguing for their ideas | 🔴 High | They've mentally checked out |\n| Life event (new baby, move, partner change) | 🟡 Medium | Re-evaluating everything |\n\n**Retention conversation framework:**\n1. Name it: \"I've noticed [specific behavior change]. I want to check in.\"\n2. Listen: Let them talk. Don't interrupt. Don't get defensive.\n3. Understand: \"What would make this the best job you've ever had?\"\n4. Act: Make a concrete commitment within 48 hours — title, comp, scope, flexibility\n5. Follow up: Check back in 1 week. Did what you promised make a difference?\n\n---\n\n## Phase 3: Performance Management\n\n### Performance Calibration Framework\n\nRate on two axes (both matter):\n\n**Delivery Impact (What)**\n| Level | Description |\n|-------|-------------|\n| 1 - Below | Missing commitments, quality issues, needs close oversight |\n| 2 - Meeting | Delivering assigned work reliably |\n| 3 - Exceeding | Delivering beyond scope, finding better solutions |\n| 4 - Outstanding | Multiplying team output, solving problems no one asked them to |\n\n**Behaviors (How)**\n| Level | Description |\n|-------|-------------|\n| 1 - Below | Creating friction, not collaborating, ignoring feedback |\n| 2 - Meeting | Professional, collaborative, receptive to feedback |\n| 3 - Exceeding | Mentoring others, proactively improving processes |\n| 4 - Outstanding | Shaping culture, attracting talent, raising the entire bar |\n\n**Calibration matrix:**\n\n| | Behavior 1 | Behavior 2 | Behavior 3 | Behavior 4 |\n|---|---|---|---|---|\n| **Delivery 4** | Coach behaviors | Strong | Top performer | Superstar |\n| **Delivery 3** | Coach behaviors | Solid | Strong | Top performer |\n| **Delivery 2** | PIP candidate | Meets expectations | Developing | Growing |\n| **Delivery 1** | Exit | PIP | Coach delivery | Coach delivery |\n\n### Feedback Framework: SBI-I (Situation-Behavior-Impact-Intent)\n\n**Template:**\n\"In [situation], when you [specific behavior], the impact was [concrete effect]. I'd like to see [specific change] because [intent/why it matters].\"\n\n**Examples:**\n\n✅ Good: \"In yesterday's design review, when you challenged the API schema with the versioning concern, it caught a breaking change we would have shipped. That's exactly the kind of technical leadership I want to see more of.\"\n\n❌ Bad: \"You're doing great work. Keep it up.\" (Too vague — they learn nothing)\n\n✅ Good: \"In the last two sprints, PRs have been sitting in review for 3+ days. The impact is features are merging late and we're missing sprint commitments. I'd like us to commit to <24h first review because velocity depends on review speed.\"\n\n❌ Bad: \"You need to review PRs faster.\" (No situation, no impact, no collaboration)\n\n### Performance Improvement Plan (PIP) Template\n\n```yaml\npip:\n  employee: \"[Name]\"\n  role: \"[Title]\"\n  manager: \"[Your name]\"\n  start_date: \"YYYY-MM-DD\"\n  end_date: \"YYYY-MM-DD\"  # 30-60 days, never >90\n  \n  context: |\n    [Specific pattern of underperformance with dates and examples.\n     Must reference prior feedback conversations and dates they occurred.]\n  \n  expectations:\n    - area: \"[Specific skill/behavior]\"\n      current_state: \"[What's happening now — with examples]\"\n      target_state: \"[What success looks like — measurable]\"\n      measurement: \"[How we'll measure — PR metrics, sprint completion, etc.]\"\n      support: \"[What I'll provide — pairing, training, reduced scope]\"\n  \n  check_ins:\n    frequency: weekly\n    day: \"[Day]\"\n    format: \"[30 min 1:1 with written summary]\"\n  \n  outcomes:\n    success: \"[What happens if targets met — return to normal performance management]\"\n    failure: \"[What happens if targets not met — typically termination]\"\n  \n  # CRITICAL: Have HR review before sharing. Document every check-in.\n  hr_reviewed: false\n  hr_reviewer: \"[Name]\"\n```\n\n**PIP rules:**\n- A PIP should never be a surprise — if it is, YOU failed at feedback\n- PIPs are for capability gaps, not attitude problems (attitude = manage out faster)\n- 70% of PIPs end in termination — be honest with yourself about whether this is a development tool or a documentation exercise\n- Weekly check-ins are non-negotiable — document everything in writing\n- If performance improves during PIP then declines after: second PIP is rarely worth it\n\n### Promotion Case Template\n\n```yaml\npromotion_case:\n  candidate: \"[Name]\"\n  current_level: \"[Level]\"\n  target_level: \"[Level]\"\n  manager: \"[Your name]\"\n  date: \"YYYY-MM-DD\"\n  \n  # Already operating at next level (past 6+ months)\n  evidence:\n    - dimension: \"Technical complexity\"\n      examples:\n        - \"[Specific project/decision with measurable impact]\"\n        - \"[Another example]\"\n    - dimension: \"Scope & ownership\"\n      examples:\n        - \"[Owned X end-to-end, previously needed guidance]\"\n    - dimension: \"Influence & leadership\"\n      examples:\n        - \"[Mentored Y, led Z initiative, shaped team direction]\"\n    - dimension: \"Business impact\"\n      examples:\n        - \"[Revenue/efficiency/reliability improvement with numbers]\"\n  \n  peer_feedback:\n    - from: \"[Name, role]\"\n      quote: \"[Specific praise with examples]\"\n  \n  # Why now, not 6 months from now?\n  timing_justification: |\n    [They've been consistently operating at next level for X months.\n     Delaying creates retention risk and sends wrong signal to team.]\n  \n  # What's the gap? (Be honest — calibration committees will find it)\n  growth_areas: |\n    [Areas they're still developing. Frame as \"growing into\" not \"lacking.\"]\n```\n\n---\n\n## Phase 4: Hiring Machine\n\n### Hiring Pipeline\n\n```\nRole opened → Job description → Sourcing (5-7 days)\n→ Resume screen → Recruiter screen (30 min)\n→ Technical phone screen (60 min) → Take-home OR live coding (2-4 hrs)\n→ Onsite/virtual loop (3-4 hrs) → Debrief → Offer → Close\n\nTarget: <21 days from first screen to offer\n```\n\n### Job Description Template\n\n```markdown\n# [Role Title] — [Team Name]\n\n## What you'll do\n[3-5 bullet points of ACTUAL work, not generic responsibilities]\n- Ship [specific feature/system] that [specific impact]\n- Own [specific domain] end-to-end\n- [Concrete example of a recent problem this person would solve]\n\n## What you'll need\n[Must-haves only — each one must be a genuine filter]\n- X years building [specific technology/domain]\n- Experience with [specific technical requirement]\n- [Skill that actually differentiates candidates]\n\n## Nice to have (genuinely nice, not secretly required)\n- [Thing that would accelerate ramp-up]\n- [Adjacent skill that adds value]\n\n## What we offer\n[Be specific — \"competitive salary\" means nothing]\n- Salary range: $X-$Y (based on [location/level])\n- [Specific benefits that matter to engineers]\n- [Team/culture thing that's actually true and differentiating]\n\n## How we hire\n[Timeline and what to expect — respect their time]\n1. [Step]: [Duration] — [What we're assessing]\n2. [Step]: [Duration] — [What we're assessing]\nTotal time investment: ~X hours\n```\n\n### Interview Scorecard (Per Interviewer)\n\n```yaml\nscorecard:\n  candidate: \"[Name]\"\n  interviewer: \"[Name]\"\n  interview_type: \"technical | system design | behavioral | culture\"\n  date: \"YYYY-MM-DD\"\n  \n  # Score each dimension 1-4 (no 3s allowed — forces a decision)\n  dimensions:\n    - name: \"Technical depth\"\n      score: _  # 1=no hire, 2=lean no, 4=lean yes, 5=strong yes (skip 3)\n      evidence: \"[Specific examples from the interview]\"\n    - name: \"Problem solving approach\"\n      score: _\n      evidence: \"[How they broke down the problem, handled hints]\"\n    - name: \"Communication clarity\"\n      score: _\n      evidence: \"[Could they explain their thinking? Did they ask good questions?]\"\n    - name: \"Collaboration signals\"\n      score: _\n      evidence: \"[How did they respond to pushback? Did they build on ideas?]\"\n  \n  # Overall\n  hire_recommendation: strong_no | no | yes | strong_yes\n  level_recommendation: \"[What level would you place them?]\"\n  concerns: \"[Anything that gave you pause]\"\n  highlights: \"[What impressed you most]\"\n```\n\n### Debrief Protocol\n\n1. **No pre-discussion** — Submit scorecards BEFORE the debrief meeting\n2. **Hire bar holder speaks last** — Prevent anchoring\n3. **Discuss each dimension, not overall vibes** — \"Tell me about their system design approach\" not \"What did you think?\"\n4. **Any strong_no is a veto** — Unless the interviewer can be convinced their signal was a misread\n5. **Decide in the room** — Don't \"sleep on it\" unless genuinely torn (then it's probably a no)\n6. **Leveling before offer** — Agree on level first, then comp follows from band\n\n### Closing Candidates\n\n**The 3 things that close engineers:**\n1. **The problem** — \"Here's the specific hard problem you'd work on\"\n2. **The people** — Connect them with future teammates before offer\n3. **The growth** — \"Here's where this role leads in 18 months\"\n\n**Offer call structure (15-20 min):**\n1. Express genuine excitement (2 min)\n2. Present offer details — base, equity, bonus, start date (3 min)\n3. Explain equity/comp philosophy (3 min)\n4. Ask: \"How does this compare to what you were expecting?\" (listen)\n5. Address concerns immediately if possible\n6. Set a decision deadline (3-5 business days, not open-ended)\n7. Ask: \"Is there anything that would make this a clear yes?\"\n\n---\n\n## Phase 5: Technical Leadership\n\n### Architecture Decision Record (ADR)\n\n```yaml\nadr:\n  id: \"ADR-NNN\"\n  title: \"[Decision title]\"\n  date: \"YYYY-MM-DD\"\n  status: proposed | accepted | deprecated | superseded\n  superseded_by: \"ADR-NNN\"  # if applicable\n  \n  context: |\n    [What situation are we in? What forces are at play?\n     Include constraints: timeline, team skill, budget, scale requirements.]\n  \n  options:\n    - name: \"[Option A]\"\n      pros: [\"pro 1\", \"pro 2\"]\n      cons: [\"con 1\", \"con 2\"]\n      effort: \"[T-shirt size]\"\n      risk: low | medium | high\n    - name: \"[Option B]\"\n      pros: [\"pro 1\"]\n      cons: [\"con 1\", \"con 2\", \"con 3\"]\n      effort: \"[T-shirt size]\"\n      risk: low | medium | high\n  \n  decision: |\n    [What we decided and WHY. The \"why\" is the most important part.\n     Future readers need to understand the reasoning, not just the choice.]\n  \n  consequences: |\n    [What follows from this decision? What becomes easier/harder?\n     What do we need to monitor?]\n  \n  review_date: \"YYYY-MM-DD\"  # When to revisit this decision\n```\n\n### Tech Debt Prioritization\n\nScore each debt item on two axes:\n\n**Impact of fixing (1-5):**\n- 5: Unblocks multiple teams or critical features\n- 4: Significant velocity improvement for our team\n- 3: Moderate improvement, prevents future problems\n- 2: Nice to have, minor improvement\n- 1: Cosmetic or theoretical benefit\n\n**Cost of NOT fixing (1-5):**\n- 5: Will cause incidents or data loss\n- 4: Blocking hiring/onboarding (can't explain the code)\n- 3: Slowing every feature by >20%\n- 2: Occasional friction, workarounds exist\n- 1: Annoying but harmless\n\n**Priority = Impact × Cost-of-not-fixing**\n\n| Score | Action |\n|-------|--------|\n| 20-25 | Fix THIS sprint — it's an emergency |\n| 12-19 | Schedule within 2 sprints |\n| 6-11 | Add to quarterly tech debt budget (allocate 15-20% of sprint capacity) |\n| 1-5 | Backlog — revisit quarterly |\n\n### Code Review Culture Guidelines\n\n```yaml\ncode_review_standards:\n  sla:\n    first_review: \"< 4 hours during work hours\"\n    follow_up: \"< 2 hours\"\n    max_pr_size: 400  # lines changed — larger needs pre-review or splitting\n  \n  what_to_review:\n    always:\n      - \"Correctness — does it do what it claims?\"\n      - \"Edge cases — what happens with nil/empty/max/concurrent?\"\n      - \"Security — auth checks, input validation, secrets exposure\"\n      - \"Naming — will someone understand this in 6 months?\"\n    sometimes:\n      - \"Performance — only if in hot path or O(n²)+ risk\"\n      - \"Style — only if it significantly hurts readability\"\n    never:\n      - \"Personal preference disguised as improvement\"\n      - \"Premature optimization suggestions\"\n      - \"Rewriting working code to your style\"\n  \n  tone_rules:\n    - \"Ask questions instead of making demands: 'What happens if X is nil?' not 'Handle the nil case'\"\n    - \"Prefix opinion with 'nit:' or 'optional:' — make severity clear\"\n    - \"Praise good code — 'Nice abstraction here' costs nothing\"\n    - \"If >5 comments, offer to pair instead\"\n    - \"Approve with comments when nothing is blocking — trust your team\"\n```\n\n---\n\n## Phase 6: Sprint & Delivery\n\n### Sprint Ceremony Cheat Sheet\n\n| Ceremony | Duration | Who | Purpose | Your Role |\n|----------|----------|-----|---------|-----------|\n| **Sprint planning** | 1-2 hrs | Team + PO | Commit to sprint goal | Facilitate, challenge estimates, protect capacity |\n| **Daily standup** | 15 min | Team | Surface blockers | Listen for problems, DON'T manage tasks |\n| **Backlog refinement** | 1 hr | Team + PO | Prepare future work | Ensure technical feasibility, flag risks |\n| **Sprint review** | 30 min | Team + stakeholders | Demo working software | Let the team present, handle stakeholder Qs |\n| **Retrospective** | 1 hr | Team only | Improve process | Facilitate, ensure psychological safety, track actions |\n\n### Sprint Health Metrics\n\nTrack these weekly — trend matters more than absolute numbers:\n\n| Metric | Healthy Range | Red Flag |\n|--------|---------------|----------|\n| **Sprint completion rate** | 80-100% of committed points | <70% for 2+ sprints |\n| **Carry-over stories** | 0-1 per sprint | Same story carried 3+ sprints |\n| **PR cycle time** | <48 hours open to merge | >72 hours consistently |\n| **Bug escape rate** | <10% of stories create bugs | Rising trend |\n| **Deployment frequency** | Daily to weekly | Monthly or less |\n| **Sprint goal achievement** | Yes/No binary | No for 3+ consecutive sprints |\n\n### Estimation Heuristic\n\nWhen the team struggles with estimation:\n\n| Certainty Level | Approach |\n|----------------|----------|\n| \"We've done this exact thing before\" | Size by comparison to past work |\n| \"We understand the problem but not the solution\" | Spike first (timeboxed), then estimate |\n| \"We don't fully understand the problem\" | Discovery task (1-2 days), then re-scope |\n| \"We have no idea\" | Break it down until you reach pieces you can estimate |\n\n**Rule:** If an estimate is >8 points (or >5 days), it's not estimated — it's a guess. Break it down further.\n\n---\n\n## Phase 7: Incident Management\n\n### Incident Response Framework\n\n```yaml\nincident:\n  id: \"INC-YYYY-NNN\"\n  severity: SEV1 | SEV2 | SEV3 | SEV4\n  detected: \"YYYY-MM-DD HH:MM UTC\"\n  resolved: \"YYYY-MM-DD HH:MM UTC\"\n  duration: \"Xh Ym\"\n  commander: \"[Name]\"\n  \n  # Severity guide\n  # SEV1: Revenue impact, data loss, full outage — ALL HANDS, exec notification\n  # SEV2: Degraded service, partial outage — On-call + team lead\n  # SEV3: Minor degradation, workaround exists — On-call handles\n  # SEV4: Cosmetic, no user impact — Normal ticket\n  \n  timeline:\n    - time: \"HH:MM\"\n      action: \"[What happened / what was done]\"\n      who: \"[Name]\"\n  \n  root_cause: |\n    [Technical root cause — be specific. \n     \"Human error\" is never the root cause. What system allowed the error?]\n  \n  contributing_factors:\n    - \"[Factor 1 — e.g., missing monitoring on X]\"\n    - \"[Factor 2 — e.g., deployment during peak without feature flag]\"\n  \n  action_items:\n    - description: \"[Specific fix]\"\n      owner: \"[Name]\"\n      due_date: \"YYYY-MM-DD\"\n      priority: P0 | P1 | P2\n      status: open | in_progress | done\n```\n\n### Blameless Post-Mortem Template\n\n**Facilitation rules:**\n1. Focus on systems, not individuals\n2. \"What\" and \"how,\" never \"who\"\n3. Everyone involved attends (including on-call who was paged)\n4. Schedule within 48 hours of resolution (memories fade)\n5. Write it up and share publicly within the engineering org\n\n**Structure (60-90 min):**\n1. **Timeline review** (20 min) — Walk through chronologically. Fill gaps.\n2. **Root cause analysis** (15 min) — \"5 Whys\" until you hit a systemic issue\n3. **What went well** (10 min) — Reinforce good incident response behaviors\n4. **What went wrong** (15 min) — Process failures, detection gaps, communication issues\n5. **Action items** (15 min) — Each must have an owner and due date. Max 5 items — focus beats volume.\n\n### On-Call Health Guidelines\n\n| Metric | Healthy | Unhealthy |\n|--------|---------|-----------|\n| Pages per week | <5 | >10 |\n| Off-hours pages | <2/week | >5/week |\n| Time to acknowledge | <5 min | >15 min |\n| False positive rate | <20% | >50% |\n| Rotation size | 4+ people | <3 people |\n| Consecutive weeks on-call | Never >2 | Regular 3+ week stretches |\n\n**If on-call is unhealthy:** This is a tech debt problem, not a people problem. Invest in reliability before adding headcount.\n\n---\n\n## Phase 8: Scaling & Org Design\n\n### When to Split a Team\n\n| Signal | Action |\n|--------|--------|\n| Team >8 people | Split before communication overhead kills velocity |\n| Two distinct domains in one team | Split along domain boundaries |\n| Standup takes >15 min | Too many threads — people are tuning out |\n| PR review queue >48 hours consistently | Not enough context overlap — specialize |\n| On-call covers too many services | Reduce blast radius per team |\n\n### Splitting Protocol\n\n1. **Define boundaries clearly** — What does each new team OWN? Write it down.\n2. **Split the backlog** — Every ticket gets a home. Shared backlogs = shared ownership = no ownership.\n3. **Split on-call** — Each team owns their services' reliability.\n4. **Name the teams** — Sounds trivial, matters for identity.\n5. **Designate tech leads** — Don't leave both teams looking to you for technical decisions.\n6. **Give it 3 months** — Resist re-orging again too quickly. Turbulence is normal.\n\n### Manager-to-IC Ratio\n\n| Team Size | Structure |\n|-----------|-----------|\n| 3-5 ICs | Player-coach (you're still coding ~30-40%) |\n| 5-8 ICs | Full-time manager (stop coding in critical path) |\n| 8-12 ICs | Split the team OR add a tech lead as force multiplier |\n| 12+ ICs | Must split — you cannot manage this effectively |\n\n### The IC-to-Manager Transition\n\nIf you're newly managing (or coaching someone through it):\n\n**Stop doing:**\n- Writing code in the critical path (you're now the bottleneck)\n- Solving every technical problem yourself\n- Being the best engineer on the team (your job changed)\n\n**Start doing:**\n- Asking \"who should own this?\" instead of doing it yourself\n- Measuring success by team output, not your output\n- Having uncomfortable conversations early (feedback, performance, conflict)\n- Blocking time for thinking, not just meetings\n\n**Keep doing:**\n- Staying technical enough to evaluate decisions (read code, review designs)\n- Coding on side projects, tools, or prototypes (stay sharp)\n- Having strong technical opinions (but hold them loosely)\n\n**Timeline to competence:**\n- Month 1-3: Imposter syndrome, everything feels slow. Normal.\n- Month 3-6: Finding your rhythm, some wins, some failures. Normal.\n- Month 6-12: Confident in the role, building systems. Target.\n- Month 12+: Multiplying impact. If you're not here by month 18, honest conversation needed.\n\n---\n\n## Phase 9: Communication & Stakeholder Management\n\n### Weekly Status Update Template\n\nSend this to your manager and stakeholders every Friday:\n\n```markdown\n# [Team Name] — Week of [Date]\n\n## 🎯 Sprint Goal: [Goal] — On Track / At Risk / Off Track\n\n## ✅ Shipped This Week\n- [Feature/fix] — [Impact in user/business terms]\n- [Feature/fix] — [Impact]\n\n## 🔨 In Progress\n- [Work item] — [Status, ETA, any blockers]\n\n## 🚨 Risks & Blockers\n- [Risk] — [What you're doing about it, what you need]\n\n## 📊 Key Metrics\n- Deploy frequency: X\n- Incident count: X (SEV breakdown)\n- Sprint completion: X%\n\n## 🔮 Next Week\n- [Priority 1]\n- [Priority 2]\n```\n\n### Managing Up Checklist\n\n| Do | Don't |\n|----|-------|\n| Bring solutions with problems | Dump problems without proposals |\n| Flag risks early with mitigation plans | Surprise with bad news at the last minute |\n| Quantify impact (hours, $$, users) | Use vague language (\"it's kinda slow\") |\n| Say \"I need X from you by Y\" | Hope they'll figure out you need help |\n| Send written updates proactively | Wait to be asked for status |\n| Disagree in private | Disagree in public meetings |\n| Ask for feedback regularly | Assume no news is good news |\n\n### Cross-Functional Relationship Map\n\n```yaml\nstakeholders:\n  - name: \"[Product Manager]\"\n    relationship: partner\n    cadence: \"Daily async + weekly 1:1\"\n    currency: \"Scope clarity, user data, priority decisions\"\n    \n  - name: \"[Design Lead]\"\n    relationship: partner\n    cadence: \"Bi-weekly sync + ad-hoc\"\n    currency: \"Early technical feasibility input\"\n    \n  - name: \"[Platform/Infra Team]\"\n    relationship: dependency\n    cadence: \"Monthly sync + Slack\"\n    currency: \"Clear requirements, advance notice of needs\"\n    \n  - name: \"[Your Manager]\"\n    relationship: air_cover\n    cadence: \"Weekly 1:1\"\n    currency: \"No surprises, clear asks, good judgment\"\n```\n\n---\n\n## Phase 10: Engineering Manager Rituals\n\n### Daily (15 min total)\n\n- [ ] Scan Slack/email for blockers — unblock before standup\n- [ ] Attend standup — listen for patterns, not task updates\n- [ ] Check PR queue — nudge any >24h reviews\n- [ ] One piece of feedback (positive or constructive) to someone\n\n### Weekly\n\n- [ ] All 1:1s completed (never cancel — reschedule if needed)\n- [ ] Sprint metrics reviewed\n- [ ] Status update sent to stakeholders\n- [ ] Calendar audit — am I in meetings I shouldn't be in?\n- [ ] One skip-level or cross-functional conversation\n\n### Monthly\n\n- [ ] Team health radar updated\n- [ ] Career development conversation with each report\n- [ ] Tech debt review and prioritization\n- [ ] On-call health review\n- [ ] Update team topology doc\n\n### Quarterly\n\n- [ ] Performance calibration (formal or informal)\n- [ ] Team goals review and reset\n- [ ] Architecture review — any ADRs need revisiting?\n- [ ] Headcount planning — what do we need in 6 months?\n- [ ] Retrospective on YOUR performance — ask your team for feedback\n\n---\n\n## Phase 11: Difficult Situations Playbook\n\n### Scenario: Two Senior Engineers Disagree on Architecture\n\n1. Let them present both approaches in a design doc (each writes their own section)\n2. Define decision criteria BEFORE evaluating: reversibility, maintenance cost, team familiarity, timeline\n3. Facilitate a time-boxed discussion (60 min max)\n4. If no consensus: the tech lead or DRI decides. Not you (unless you must).\n5. Document the decision as an ADR — the \"why\" matters more than the \"what\"\n6. The person who \"lost\" must commit fully. Monitor for passive resistance.\n\n### Scenario: High Performer Wants to Be a Manager\n\n1. Explore motivation: \"Tell me what you think a manager does day-to-day\"\n2. Test with real work: lead a project, mentor a junior, run a retrospective\n3. Be honest about tradeoffs: less coding, more meetings, slower feedback loops, ambiguous success metrics\n4. Offer the Staff/Principal IC path as a genuine alternative, not a consolation prize\n5. If they proceed: set explicit check-in at 3 months — \"Is this what you wanted?\"\n\n### Scenario: You Inherit a Low-Performing Team\n\n1. **Week 1-2:** Listen. 1:1 with every person. Don't change anything yet.\n2. **Week 3-4:** Identify the 1-2 systemic issues (usually: unclear priorities, no accountability, or trust deficit)\n3. **Month 2:** Make ONE process change. Get a quick win. Build credibility.\n4. **Month 3:** Address performance issues you've now observed firsthand\n5. **Never:** Blame the previous manager publicly. Never say \"things are going to change around here.\"\n\n### Scenario: Layoffs / Reorg Affecting Your Team\n\n1. **Before announcement:** Prepare a plan for remaining team — who covers what?\n2. **During:** Be honest about what you know and what you don't. \"I don't know\" > corporate-speak.\n3. **After:** 1:1 with every remaining person within 48 hours. Expect anger, fear, guilt.\n4. **Ongoing:** Workload audit — don't expect same output from fewer people. Push back on scope.\n5. **Self-care:** This is one of the hardest parts of the job. Talk to your own manager or a coach.\n\n### Scenario: Your Best Engineer Gives Notice\n\n1. **Same day:** Have a real conversation. Not a counteroffer — understand why.\n2. **If it's about money:** Match or beat if they're worth it. If your company won't, that tells you something.\n3. **If it's about growth/role:** Can you create what they want? Be honest if you can't.\n4. **If they're leaving for the right reasons:** Celebrate them. Write a recommendation. Don't make it weird.\n5. **Immediately:** Start knowledge transfer plan. Identify what only they know.\n6. **To the team:** Transparent but positive. \"X is leaving for a great opportunity. Here's our transition plan.\"\n\n---\n\n## Scoring Rubric: Engineering Manager Effectiveness (0-100)\n\n| Dimension | Weight | Indicators |\n|-----------|--------|------------|\n| **Team health** | 20% | Retention, engagement scores, psychological safety signals |\n| **Delivery** | 20% | Sprint completion, quality metrics, stakeholder satisfaction |\n| **People development** | 20% | Promotions, skill growth, 1:1 quality, mentorship |\n| **Technical stewardship** | 15% | Tech debt trajectory, architecture quality, incident trends |\n| **Hiring** | 10% | Pipeline health, offer acceptance rate, new hire ramp time |\n| **Communication** | 10% | Stakeholder relationships, information flow, no surprises |\n| **Self-improvement** | 5% | Seeking feedback, adapting, growing as a leader |\n\n**Scoring:**\n- 90-100: Exceptional — team thriving, people growing, shipping reliably\n- 75-89: Strong — most things working, some areas to develop\n- 60-74: Developing — foundational skills present, needs coaching\n- 40-59: Struggling — significant gaps, at risk of losing team trust\n- <40: Intervention needed — coaching, role change, or transition\n\n---\n\n## Natural Language Commands\n\n- \"Prepare 1:1 with [name]\" → Generate agenda from recent context\n- \"Write performance review for [name]\" → Calibrate and draft using framework\n- \"Create job description for [role]\" → Generate using template\n- \"Run team health check\" → Walk through radar dimensions\n- \"Draft ADR for [decision]\" → Structure architecture decision\n- \"Incident post-mortem for [incident]\" → Generate post-mortem template\n- \"Sprint health report\" → Analyze metrics and flag issues\n- \"Promotion case for [name]\" → Build evidence-based promotion doc\n- \"Evaluate tech debt [item]\" → Score using prioritization matrix\n- \"Flight risk assessment\" → Review signals for each team member\n- \"Stakeholder update\" → Generate weekly status from context\n- \"Interview scorecard for [candidate]\" → Create structured evaluation\n","readmeExcerpt":"--- name: Engineering Manager OS description: Complete engineering management system — team building, 1:1s, performance, hiring, architecture decisions, incident management, and scaling. From IC-to-manager transition through director-level operations. metadata: {\"clawdbot\":{\"emoji\":\"⚙️\",\"os\":[\"linux\",\"darwin\",\"win32\"]}} --- Engineering Manager Operating System Your complete playbook for engineering leadership. Not ge","codeSnippets":[],"executableExamples":[{"language":"yaml","snippet":"team_topology:\n  name: \"[Team Name]\"\n  type: stream-aligned | platform | enabling | complicated-subsystem\n  mission: \"[One sentence — what does this team exist to do?]\"\n  boundaries:\n    owns: [\"service-x\", \"domain-y\", \"pipeline-z\"]\n    consumes: [\"auth-service\", \"data-platform\"]\n    provides: [\"checkout-api\", \"payment-events\"]\n  cognitive_load: low | medium | high | overloaded\n  interaction_modes:\n    - team: \"[Other Team]\"\n      mode: collaboration | x-as-a-service | facilitating\n      friction: low | medium | high\n      notes: \"[What's working/not working]\"\n  current_headcount: N\n  ideal_headcount: N\n  skill_gaps: [\"observability\", \"mobile\", \"ML\"]"},{"language":"yaml","snippet":"one_on_one:\n  date: \"YYYY-MM-DD\"\n  person: \"[Name]\"\n  role: \"[Title]\"\n  tenure: \"[X months on team]\"\n  \n  # Their agenda first — ALWAYS\n  their_topics: []\n  \n  # Check-in (2 min)\n  energy_level: 1-10  # \"How are you feeling about work this week?\"\n  energy_trend: up | stable | down\n  \n  # Delivery (5 min)\n  current_work: \"[What they're working on]\"\n  blockers: []\n  help_needed: \"[What can I unblock?]\"\n  \n  # Growth (10 min — skip if urgent topics dominate, but never 3 weeks in a row)\n  career_conversation: \"[Topic discussed]\"\n  feedback_given: \"[Specific behavior → impact → request]\"\n  feedback_received: \"[What they told me]\"\n  stretch_opportunity: \"[Current or upcoming]\"\n  \n  # Action items\n  my_actions: []  # What I committed to do\n  their_actions: []  # What they committed to do\n  \n  # Signals (private — don't share these)\n  flight_risk: low | medium | high\n  performance_trajectory: improving | stable | declining\n  notes: \"[Anything notable]\""},{"language":"yaml","snippet":"pip:\n  employee: \"[Name]\"\n  role: \"[Title]\"\n  manager: \"[Your name]\"\n  start_date: \"YYYY-MM-DD\"\n  end_date: \"YYYY-MM-DD\"  # 30-60 days, never >90\n  \n  context: |\n    [Specific pattern of underperformance with dates and examples.\n     Must reference prior feedback conversations and dates they occurred.]\n  \n  expectations:\n    - area: \"[Specific skill/behavior]\"\n      current_state: \"[What's happening now — with examples]\"\n      target_state: \"[What success looks like — measurable]\"\n      measurement: \"[How we'll measure — PR metrics, sprint completion, etc.]\"\n      support: \"[What I'll provide — pairing, training, reduced scope]\"\n  \n  check_ins:\n    frequency: weekly\n    day: \"[Day]\"\n    format: \"[30 min 1:1 with written summary]\"\n  \n  outcomes:\n    success: \"[What happens if targets met — return to normal performance management]\"\n    failure: \"[What happens if targets not met — typically termination]\"\n  \n  # CRITICAL: Have HR review before sharing. Document every check-in.\n  hr_reviewed: false\n  hr_reviewer: \"[Name]\""},{"language":"yaml","snippet":"promotion_case:\n  candidate: \"[Name]\"\n  current_level: \"[Level]\"\n  target_level: \"[Level]\"\n  manager: \"[Your name]\"\n  date: \"YYYY-MM-DD\"\n  \n  # Already operating at next level (past 6+ months)\n  evidence:\n    - dimension: \"Technical complexity\"\n      examples:\n        - \"[Specific project/decision with measurable impact]\"\n        - \"[Another example]\"\n    - dimension: \"Scope & ownership\"\n      examples:\n        - \"[Owned X end-to-end, previously needed guidance]\"\n    - dimension: \"Influence & leadership\"\n      examples:\n        - \"[Mentored Y, led Z initiative, shaped team direction]\"\n    - dimension: \"Business impact\"\n      examples:\n        - \"[Revenue/efficiency/reliability improvement with numbers]\"\n  \n  peer_feedback:\n    - from: \"[Name, role]\"\n      quote: \"[Specific praise with examples]\"\n  \n  # Why now, not 6 months from now?\n  timing_justification: |\n    [They've been consistently operating at next level for X months.\n     Delaying creates retention risk and sends wrong signal to team.]\n  \n  # What's the gap? (Be honest — calibration committees will find it)\n  growth_areas: |\n    [Areas they're still developing. Frame as \"growing into\" not \"lacking.\"]"},{"language":"text","snippet":"Role opened → Job description → Sourcing (5-7 days)\n→ Resume screen → Recruiter screen (30 min)\n→ Technical phone screen (60 min) → Take-home OR live coding (2-4 hrs)\n→ Onsite/virtual loop (3-4 hrs) → Debrief → Offer → Close\n\nTarget: <21 days from first screen to offer"},{"language":"markdown","snippet":"# [Role Title] — [Team Name]\n\n## What you'll do\n[3-5 bullet points of ACTUAL work, not generic responsibilities]\n- Ship [specific feature/system] that [specific impact]\n- Own [specific domain] end-to-end\n- [Concrete example of a recent problem this person would solve]\n\n## What you'll need\n[Must-haves only — each one must be a genuine filter]\n- X years building [specific technology/domain]\n- Experience with [specific technical requirement]\n- [Skill that actually differentiates candidates]\n\n## Nice to have (genuinely nice, not secretly required)\n- [Thing that would accelerate ramp-up]\n- [Adjacent skill that adds value]\n\n## What we offer\n[Be specific — \"competitive salary\" means nothing]\n- Salary range: $X-$Y (based on [location/level])\n- [Specific benefits that matter to engineers]\n- [Team/culture thing that's actually true and differentiating]\n\n## How we hire\n[Timeline and what to expect — respect their time]\n1. [Step]: [Duration] — [What we're assessing]\n2. [Step]: [Duration] — [What we're assessing]\nTotal time investment: ~X hours"}],"parameters":{},"dependencies":[],"permissions":[],"extractedFiles":[],"languages":["typescript"],"docsSourceLabel":"CLAWHUB","editorialOverview":"Complete engineering management system — team building, 1:1s, performance, hiring, architecture decisions, incident management, and scaling. From IC-to-manager transition through director-level operations. --- name: Engineering Manager OS description: Complete engineering management system — team building, 1:1s, performance, hiring, architecture decisions, incident management, and scaling. From IC-to-manager transition through director-level operations. metadata: {\"clawdbot\":{\"emoji\":\"⚙️\",\"os\":[\"linux\",\"darwin\",\"win32\"]}} --- Engineering Manager Operating System Your complete playbook for engineering leadership. Not ge","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":384,"uniquenessScore":63,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-04-15T00:45:39.800Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T20:55:44.706Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}