Skills for
エンジニアリングマネージャー

Engineering managers commonly own hiring loops, interview calibration, and competency assessment.

Directly supports EM prioritization, code-health assessment, and remediation planning.

Useful for documenting and challenging engineering decisions.

Sets up repo issue-tracking and engineering documentation conventions.

Broad engineering-role index, potentially useful for EM delegation but not EM-specific.

Engineering leadership-relevant tools, but a broad technical bundle rather than an EM skill.

Leadership operations for AI platforms; useful to AI engineering managers but specialized.

Supports startup hiring and org design, but extends beyond engineering management.

Broad engineering tools can support managers, but lacks EM workflows.

Useful quality capability for an EM, but it is a specialized implementation audit.

Useful pre-merge quality mechanism for EMs, but a specialized code-review skill.

Relevant when an EM manages agentic engineering systems, but it is specialized architecture.

Managed verification loops can support EM execution, but it is agent-workflow infrastructure.

Workflow orchestration may help technical EMs, but it is not team-management guidance.

Multi-agent coordination resembles EM orchestration but is tool-specific.

Supports EM technical governance, but is a narrow API-review specialty.

Release management supports EM work, but this is a narrow changelog utility.

Useful for engineering managers responsible for reliability, but specialized SRE practice.

Code-quality oversight supports EM responsibilities but is not manager-specific.

Useful for EM-led onboarding and codebase communication, but not EM-specific.

Directly useful for EM onboarding responsibilities, though it is documentation-focused.

Can inform EM quality planning, but is a narrow test-coverage workflow.

Engineering-lead role appears relevant, but excerpt lacks substantive content.

Project coordination overlaps EM delivery work, but it is not engineering-specific.

Progressive delivery is relevant to EM release ownership but is a specialized engineering skill.

Supports parallel engineering coordination, but is a narrow Git workflow tool.

Plan stress-testing can aid EM decision-making, but it is a generic facilitation skill.

Documentation-grounded design review can support EMs, but is not role-specific.

Useful for engineering team handoffs but is a generic collaboration aid.

Operational incident leadership is relevant to EMs, though it is an SRE specialty.

Useful code-quality discipline for EM review, but not management-focused.

Useful for AI engineering-manager cost governance, but narrowly AI-cost focused.

High-risk migration planning is relevant to EM delivery oversight, but specialized.

Supports high-quality technical review, but not core EM management workflows.

Reliability and alerting oversight matter to EMs, but this is an observability specialty.

PR governance helps EMs maintain quality, but it is not a management role skill.

Relevant to managers of AI teams, but specialized to production prompt governance.

Test reporting can aid an EM, but it is a narrow QA utility.

Test quality review helps EM quality oversight but is not role-specific.

Operational readiness and on-call documentation support EM responsibilities.

Architecture decisions are relevant to technical EMs, but it targets architects.

Pre-production governance helps EM release accountability, but it is a technical audit.

Reliability targets and error-budget policy can support EM operations, but are specialized.

Useful for EM planning and acceptance governance, but not specifically people or team management.

Structured change tracking and handoffs aid EM delivery management, but it is a process tool.

Supports EM technical strategy decisions but targets technology evaluation broadly.

Reusable multi-agent coordination is relevant to agentic EM workflows, but tool-specific.