Engineering Workflow (Standup, Tickets, Code Quality)
Standups, code review, architecture decisions, debugging sessions, incident response, and deploy checklists for engineering teams.
Before & after
Same prompt, same agent — the only difference is the skill.
A standup report should summarize what the team has been working on. You'd want to include recent commits and any open pull requests. It helps to organize by person and show what's in progress. Teams often find it useful to list blockers or upcoming work. You could add notes about code review status. It might be good to highlight any deployments. Would you like me to create a template or walk through what to include?
STANDUP REPORT: 2026-07-31 ALEX CHEN Completed: Merged payment retry logic (PR #847), updated Stripe webhook handler In Progress: Adding transaction audit logging Blockers: None MARIA SANTOS Completed: Fixed database connection pool leak, profiled query performance In Progress: Optimizing search indexing Blockers: Waiting on schema approval from database team JAKE RODRIGUEZ Completed: Code review on 3 PRs, deployed hotfix to production In Progress: Security scanning integration for CI/CD Blockers: None UPCOMING: Deploy to staging Wednesday; audit compliance review Friday CRITICAL ISSUES: One P1 bug in checkout flow—investigating root cause now
About this skill
name: kw-engineering-workflow description: Use when standups, code review, architecture decisions, debugging sessions, incident response, and deploy checklists for engineering teams.
Engineering Workflow (Standup, Tickets, Code Quality)
Anthropic's Engineering plugin (called 'engineering' in the repo, not 'engineering-workflow') helps with standups, code review, architecture decisions, incident response, debugging, and technical documentation. Commands include /standup (from recent activity — commits, PRs, tickets, chat), /review (security, performance, style, correctness), /debug (reproduce, isolate, diagnose, fix), /architecture (ADR format with trade-off analysis), /incident (triage, communicate, mitigate, postmortem), and /deploy-checklist (verify tests, review changes, check dependencies, confirm rollback). Standalone with pasted code or wired to source control, project tracker, and monitoring MCPs.
What you get
- /standup command (recent activity summary)
- /review command (security, performance, style, correctness)
- /debug command (reproduce → diagnose → fix)
- /architecture command (ADR with trade-offs)
- /incident command (triage → postmortem)
- /deploy-checklist command
- standalone with pasted code, supercharged with source-control / tracker / monitoring MCPs
Customize your output
- Command: standup, review, debug, architecture, incident, deploy-checklist
- Review focus: security, performance, style, correctness
Example output
Post-incident: /incident walks triage, drafts the status-page update, guides mitigation, then drafts a five-part postmortem (impact, timeline, root cause, action items, owners).
Best for
Software engineers, engineering managers, and platform teams running standups, reviews, and incidents
SKILL.md preview
---
name: kw-engineering-workflow
description: Use this skill for standups, code review, architecture decisions, debugging sessions, incident response, or deploy checklists on an engineering team.
version: 1.0.0
category: Engineering
author: AgentVolt
license: proprietary
tags:
- engineering
- p3
---
# Engineering Workflow (Standup, Tickets, Code Quality)
Runs the recurring operational surfaces of an engineering team: standups, code review, architecture decisions, incident response, debugging, and deploy checklists.
## When to use
… (sign up to view the full skill)