Engineering

Skills (10)

Claude uses these on its own when your request matches.

• architectureCreate or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and…
• code-reviewReview code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
• debugStructured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
• deploy-checklistPre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production, or documenting rollback triggers ahead of time.
• documentationWrite and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
• incident-responseRun an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
• standupGenerate a standup update from recent activity. Use when preparing for daily standup, summarizing yesterday's commits and PRs and ticket moves, formatting work into yesterday/today/blockers, or structuring a few rough notes into a shareable update.
• system-designDesign systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
• tech-debtIdentify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.
• testing-strategyDesign test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.

MCP servers (10)

Added to Claude Code when you install the plugin. You sign in to Engineering the first time it is used.

• slackRemotehttps://mcp.slack.com/mcp
• linearRemotehttps://mcp.linear.app/mcp
• asanaRemotehttps://mcp.asana.com/v2/mcp
• atlassianRemotehttps://mcp.atlassian.com/v1/mcp
• notionRemotehttps://mcp.notion.com/mcp
• githubRemotehttps://api.githubcopilot.com/mcp/
• pagerdutyRemotehttps://mcp.pagerduty.com/mcp
• datadogRemotehttps://mcp.datadoghq.com/api/unstable/mcp-server/mcp
• google calendarRemote
• gmailRemote

Install

claude plugin marketplace add anthropics/knowledge-work-plugins && claude plugin install engineering@knowledge-work-plugins

/plugin marketplace add anthropics/knowledge-work-plugins

/plugin install engineering@knowledge-work-plugins