Engineering

Plugin

Everyday software engineering plugin: standup summaries, code review, structured debugging, architecture decision records, incident response and pre-deploy checks. Official from Anthropic, built mainly for Cowork but also usable in Claude Code.

anthropics/knowledge-work-plugins · engineering29.9k
GitHub で見る
README

Engineering Plugin

A software engineering plugin primarily designed for Cowork, Anthropic's agentic desktop application — though it also works in Claude Code. Helps with standups, code review, architecture decisions, incident response, debugging, and technical documentation. Works with any engineering team — standalone with your input, supercharged when you connect your source control, project tracker, and monitoring tools.

Installation

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

Commands

Explicit workflows you invoke with a slash command:

CommandDescription
/standupGenerate a standup update from your recent activity — commits, PRs, tickets, and chat
/reviewReview code changes — security, performance, style, and correctness
/debugStructured debugging session — reproduce, isolate, diagnose, and fix
/architectureCreate or evaluate architecture decisions — ADR format with trade-off analysis
/incidentRun an incident response workflow — triage, communicate, mitigate, and write postmortem
/deploy-checklistPre-deployment checklist — verify tests, review changes, check dependencies, confirm rollback plan

All commands work standalone (paste code, describe your system, upload files) and get supercharged with MCP connectors.

Skills

Domain knowledge Claude uses automatically when relevant:

SkillDescription
code-reviewReview code for bugs, security issues, performance, and maintainability
incident-responseTriage and manage production incidents — status updates, runbooks, postmortems
system-designDesign systems and services — architecture diagrams, API design, data modeling
tech-debtIdentify, categorize, and prioritize technical debt — build a remediation plan
testing-strategyDesign test strategies — unit, integration, e2e coverage, test plan creation
documentationWrite and maintain technical documentation — READMEs, API docs, runbooks, onboarding guides

Example Workflows

Morning Standup

/standup

If your tools are connected, I'll pull your recent commits, PR activity, and ticket updates. Otherwise, tell me what you worked on and I'll format it.

Code Review

/review https://github.com/org/repo/pull/123

Share a PR link, paste a diff, or point to files. Get a structured review covering security, performance, correctness, and style.

Debugging an Issue

/debug Users are getting 500 errors on the checkout page

Walk through a structured debugging process: reproduce, isolate, diagnose, fix. I'll help you think through it systematically.

Architecture Decision

/architecture Should we use a message queue or direct API calls between services?

Get a structured ADR with options analysis, trade-offs, and a recommendation.

Incident Response

/incident The payments service is returning 503s

Start an incident workflow: triage severity, draft communications, track timeline, and generate a postmortem when resolved.

Pre-Deploy Check

/deploy-checklist auth-service v2.3.0

Get a customized deployment checklist based on your service and what's changing.

Standalone + Supercharged

Every command and skill works without any integrations:

What You Can DoStandaloneSupercharged With
Standup updatesDescribe your workSource control, Project tracker, Chat
Code reviewPaste diff or codeSource control (pull PRs automatically)
Debug sessionsDescribe the problemMonitoring (pull logs and metrics)
Architecture decisionsDescribe the systemKnowledge base (find prior ADRs)
Incident responseDescribe the incidentMonitoring, Incident management, Chat
Deploy checklistsDescribe the deployCI/CD, Source control

MCP Integrations

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Connect your tools for a richer experience:

CategoryExamplesWhat It Enables
Source controlGitHub, GitLabPR diffs, commit history, branch status
Project trackerLinear, Jira, AsanaTicket status, sprint data, assignments
MonitoringDatadog, New RelicLogs, metrics, alerts, dashboards
Incident managementPagerDuty, OpsgenieOn-call schedules, incident tracking, paging
ChatSlack, TeamsTeam discussions, standup channels
Knowledge baseNotion, ConfluenceADRs, runbooks, onboarding docs

See CONNECTORS.md for the full list of supported integrations.

Settings

Create a local settings file at engineering/.claude/settings.local.json to personalize:

{
  "name": "Your Name",
  "title": "Software Engineer",
  "team": "Your Team",
  "company": "Your Company",
  "techStack": ["Python", "TypeScript", "PostgreSQL", "AWS"],
  "defaultBranch": "main",
  "deployProcess": "canary"
}

The plugin will ask you for this information interactively if it's not configured.