heating the forge...

Name: @forgecat/engineering-agent-team
Author: forgecat

Skills(10)

standup—Generate 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.

code-review—Review 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.

architecture—Create or evaluate an architecture decision record (ADR). Use when choosing between technologies, documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

system-design—Design 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.

debug—Structured 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 is not obvious.

incident-response—Run 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.

deploy-checklist—Pre-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.

documentation—Write 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 API docs, architecture docs, operational runbooks, or other technical writing.

tech-debt—Identify, 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-strategy—Design 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.

Agents

Agent	Owns
`eng-tech-lead`	Broad engineering requests, standups, technical documentation, runbooks, and cross-functional coordination
`eng-architecture-agent`	ADRs, system design, API boundaries, data modeling, service decomposition, and architecture trade-offs
`eng-code-quality-agent`	PR review, code safety, test strategy, missing coverage, refactoring priorities, and technical debt
`eng-debug-incident-agent`	Structured debugging, production issue diagnosis, incident triage, status updates, and postmortems
`eng-release-agent`	Deployment readiness, release checklists, migrations, feature flags, rollback planning, and production-change gates

Included Skills

This profile bundles the Engineering skills directly under skills/ so the agent team works as one install.

Department agent	Skills
`eng-tech-lead`	`standup`, `documentation`
`eng-architecture-agent`	`architecture`, `system-design`
`eng-code-quality-agent`	`code-review`, `testing-strategy`, `tech-debt`
`eng-debug-incident-agent`	`debug`, `incident-response`
`eng-release-agent`	`deploy-checklist`

Central Orchestration

The root AGENTS.md file is the canonical orchestration profile and the single declared ForgeCat rules resource.

The rule tells the host agent to:

start broad engineering questions with eng-tech-lead

route architecture and system design to eng-architecture-agent

route PR review, tests, and debt to eng-code-quality-agent

route debugging and incidents to eng-debug-incident-agent

route deploy readiness and rollback planning to eng-release-agent

call the underlying Engineering skills by exact name

require owner approval before external actions such as merge, deploy, rollback, paging, status updates, ticket changes, or doc publishing

Category	Included servers
Chat	Slack
Source control	GitHub
Project tracker	Linear, Asana, Atlassian
Knowledge base	Notion
Monitoring	Datadog
Incident management	PagerDuty
Calendar and email	Google Calendar, Gmail

Field	Value
Author	ForgeCat
Source profile	`@forgecat/anthropics_knowledge-work-plugins_engineering`
Repository	https://github.com/nota-america/forgecat-agent-profiles/tree/main/profiles/forgecat/forgecat-agent-profiles/engineering-agent-team
License	Apache-2.0
Source platform	Multi-platform

Platform	Status
Claude Code	Tested
Cursor	Tested
Codex	Tested

heating the forge...

engineering-agent-team

Who I Am

Agents(5)

Skills(10)

Rules(1)

README.md

Engineering Agent Team

Installation

Agents

Included Skills

Central Orchestration

MCP Connectors

Details

Compatibility

Tags

Creator

Details

Platforms

Models

Dependencies

Security Risk