Reviewed sourceDeveloper Toolsv1.0.0

software-engineering-team Agent Plugin

Cover the software lifecycle with seven specialist agents for UX research, technical writing, product management, GitOps and CI, responsible AI, architecture review, and security review.

0 repository stars MIT Updated Aug 6, 2026
Reviewed seed

Software Engineering Team

with reviewed context.

The catalog adds a fixed-commit inventory, operating summary, prerequisites, and task-fit guidance for Software Engineering Team.

Inspect, compare, verify

Installation

Install Software Engineering Team

Install from github/awesome-copilot in a compatible Agent Plugins client. The package contains advisory agents rather than a single orchestrated workflow; users must select roles and reconcile recommendations for their repository.

Terminal · Git sparse checkout
git clone --filter=blob:none --sparse https://github.com/github/awesome-copilot.git
cd awesome-copilot
git sparse-checkout set plugins/software-engineering-team
The package contains advisory agents rather than a single orchestrated workflow; users must select roles and reconcile recommendations for their repository.
Review the fixed-source README and manifest before enabling the workflow.

Explainable standards check

Conforms to Agent Plugins 1.0.0

Official latest version: 1.0.0 (Working Draft). The value is read from the official specification and cached for one day.

Read the official specification

This is a static package-format check, not a security audit, quality score, malware scan, or guarantee of client compatibility.

Canonical manifest schema

plugin.json targets the official 1.0.0 schema.

Agent Plugins specification §5.2

Required name and naming rules

The plugin name “software-engineering-team” satisfies the 1–64 character naming rules.

Agent Plugins specification §§5.3 and 5.5

Closed top-level schema

No unknown top-level manifest fields were found.

Agent Plugins specification §5.2

Manifest field types

All present metadata and extension fields use permitted JSON types.

Agent Plugins specification §§5.2–5.6

Root plugin.json file

A regular plugin.json file exists at the plugin root.

Agent Plugins specification §§4.1 and 5.1

Agent Skills discovery and format

0 immediate-child Agent Skills discovered; every SKILL.md passed required frontmatter and naming checks.

Agent Plugins specification §7.1 and Agent Skills specification

MCP configuration

No root mcp.json is present; MCP is optional and its absence is conforming.

Agent Plugins specification §§6.2 and 7.2

Capabilities

What can you do with software-engineering-team?

Cover the software lifecycle with seven specialist agents for UX research, technical writing, product management, GitOps and CI, responsible AI, architecture review, and security review.

The reviewed package declares 0 skills and 7 agent resources for its documented workflow.

  • Map user journeys and Jobs-to-be-Done
  • Create developer documentation and tutorials
  • Design reliable CI/CD and GitOps workflows
  • Align product issues with user and business value
  • Review AI work for bias, accessibility, and ethics
  • Evaluate architecture for scalability and resilience
  • Review code against OWASP, Zero Trust, and LLM security practices

Select the right lifecycle specialist

Map user journeys and Jobs-to-be-Done; Create developer documentation and tutorials; Design reliable CI/CD and GitOps workflows.

Review design, delivery, and risk

Align product issues with user and business value; Review AI work for bias, accessibility, and ethics; Evaluate architecture for scalability and resilience.

Practical workflow

A reviewed Software Engineering Team workflow

Pass 01 / Start

Select the right lifecycle specialist

Match the task to the UX, writing, product, delivery, architecture, responsible-AI, or security role.

Pass 02 / Verify

Review design, delivery, and risk

Use the specialist's output as focused review evidence and reconcile cross-discipline tradeoffs before implementation.

Package contents

What is included in software-engineering-team?

software-engineering-team declares 0 Skills, 0 MCP configurations, and 7 additional resources. The included-file links below point to the reviewed source repository.

Agent Skills

0

None

MCP servers

0

No runtime service

Package format

Agent Plugins

Official latest 1.0.0

Synced source content

Repository README

View original README

This README snapshot is stored by Agent Plugins Hub and refreshed by the daily GitHub synchronization pipeline. Remote images and embedded content are not loaded.

Source
https://github.com/github/awesome-copilot#readme

This repository does not currently provide a README snapshot. The plugin instructions below remain available.

Source documentation

Software Engineering Team source documentation

Rendered from the linked GitHub source. Raw HTML is disabled, scripts cannot execute, remote images are omitted, and external links open separately.

What this catalog entry adds

This entry summarizes the fixed reviewed manifest and README without extending the upstream package's claims.

Package scope

Cover the software lifecycle with seven specialist agents for UX research, technical writing, product management, GitOps and CI, responsible AI, architecture review, and security review.

Declared package inventory

Skills: None declared.

Agent resources: se-gitops-ci-specialist, se-product-manager-advisor, se-responsible-ai-code, se-security-reviewer, se-system-architecture-reviewer, se-technical-writer, se-ux-ui-designer

Agents are listed as resources because the extension declares them separately from skills. Only the real upstream plugin.json and README.md are listed as package files.

Documented capabilities

  • Map user journeys and Jobs-to-be-Done
  • Create developer documentation and tutorials
  • Design reliable CI/CD and GitOps workflows
  • Align product issues with user and business value
  • Review AI work for bias, accessibility, and ethics
  • Evaluate architecture for scalability and resilience
  • Review code against OWASP, Zero Trust, and LLM security practices

Workflow

  1. Match the task to the UX, writing, product, delivery, architecture, responsible-AI, or security role.
  2. Use the specialist's output as focused review evidence and reconcile cross-discipline tradeoffs before implementation.

Requirements and limitations

The package contains advisory agents rather than a single orchestrated workflow; users must select roles and reconcile recommendations for their repository.

Review generated output and consequential actions with the relevant maintainer or subject-matter expert.

License

The upstream manifest and README identify the plugin as MIT licensed.