engineering — Claude Code plugin: features and installation
This plugin for Claude Code handles code reviews, incident response, and architecture decisions. Its slash commands launch focused workflows for engineering tasks.
Apache-2.0 ★ 36,654 updated 2026-10-24
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install engineering@knowledge-work-pluginsWhat engineering does
The plugin groups slash commands and skills for software engineering work. /standup turns recent activity into a status update, /review examines code changes, and /debug guides an investigation from reproducing a problem to fixing it. Other commands cover architecture decisions, incidents, and pre-deployment checks.
Skills address code review, system design, technical debt, testing, incident response, and documentation. Commands can work from a task description or pasted code; MCP connections can bring in information from source control, project trackers, monitoring, and chat tools. Without integrations, /review still accepts a diff or code directly.
Team details can go in engineering/.claude/settings.local.json. If that file is absent, the plugin asks for the information interactively. Installation uses two marketplace commands.
What it helps with
- turn recent work into a standup update
- inspect a diff for bugs and security issues
- trace an incident and outline corrective steps
- compare architecture options in an ADR
- prepare a checklist before deployment
Example prompts for the agent
- Create a standup update from my recent work:
/engineering:standup - Review this diff for bugs and security risks:
/engineering:review - Help me investigate this error and plan a fix:
/engineering:debug
How to install engineering
Plugin marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install engineering@knowledge-work-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about engineering
How do I install engineering in Claude Code?
Run these commands in order: /plugin marketplace add anthropics/knowledge-work-plugins, then /plugin install engineering@knowledge-work-plugins.
What does the engineering plugin do?
It provides commands and skills for standups, code review, debugging, architecture decisions, incident response, and technical documentation.
Does engineering require tool integrations?
No. Its commands can work from a description, pasted code, or files. MCP connections to source control, project trackers, monitoring, and other tools can supply information from those services.
Source text
engineering · Apache-2.0
# Engineering Plugin
A software engineering plugin primarily designed for [Cowork](https://claude.com/product/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
```bash
claude plugin marketplace add anthropics/knowledge-work-plugins
claude plugin install engineering@knowledge-work-plugins
```
## Commands
Explicit workflows you invoke with a slash command:
| Command | Description |
|---|---|
| `/standup` | Generate a standup update from your recent activity — commits, PRs, tickets, and chat |
| `/review` | Review code changes — security, performance, style, and correctness |
| `/debug` | Structured debugging session — reproduce, isolate, diagnose, and fix |
| `/architecture` | Create or evaluate architecture decisions — ADR format with trade-off analysis |
| `/incident` | Run an incident response workflow — triage, communicate, mitigate, and write postmortem |
| `/deploy-checklist` | Pre-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:
| Skill | Description |
|---|---|
| `code-review` | Review code for bugs, security issues, performance, and maintainability |
| `incident-response` | Triage and manage production incidents — status updates, runbooks, postmortems |
| `system-design` | Design systems and services — architecture diagrams, API design, data modeling |
| `tech-debt` | Identify, categorize, and prioritize technical debt — build a remediation plan |
| `testing-strategy` | Design test strategies — unit, integration, e2e coverage, test plan creation |
| `documentation` | Write 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 Do | Standalone | Supercharged With |
|-----------------|------------|-------------------|
| Standup updates | Describe your work | Source control, Project tracker, Chat |
| Code review | Paste diff or code | Source control (pull PRs automatically) |
| Debug sessions | Describe the problem | Monitoring (pull logs and metrics) |
| Architecture decisions | Describe the system | Knowledge base (find prior ADRs) |
| Incident response | Describe the incident | Monitoring, Incident management, Chat |
| Deploy checklists | Describe the deploy | CI/CD, Source control |
## MCP Integrations
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](CONNECTORS.md).
Connect your tools for a richer experience:
| Category | Examples | What It Enables |
|---|---|---|
| **Source control** | GitHub, GitLab | PR diffs, commit history, branch status |
| **Project tracker** | Linear, Jira, Asana | Ticket status, sprint data, assignments |
| **Monitoring** | Datadog, New Relic | Logs, metrics, alerts, dashboards |
| **Incident management** | PagerDuty, Opsgenie | On-call schedules, incident tracking, paging |
| **Chat** | Slack, Teams | Team discussions, standup channels |
| **Knowledge base** | Notion, Confluence | ADRs, runbooks, onboarding docs |
See [CONNECTORS.md](CONNECTORS.md) for the full list of supported integrations.
## Settings
Create a local settings file at `engineering/.claude/settings.local.json` to personalize:
```json
{
"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.
© Anthropic · Apache-2.0 · anthropics/knowledge-work-plugins