mirror of
https://github.com/github/awesome-copilot.git
synced 2026-02-23 20:05:12 +00:00
Add Software Engineering Team Collection - AI Assistants for Multi-Disciplinary Development Teams (#478)
* Add Software Engineering Team collection with 7 specialized agents
Adds a complete Software Engineering Team collection with 7 standalone
agents covering the full development lifecycle, based on learnings from
The AI-Native Engineering Flow experiments.
New Agents (all prefixed with 'se-' for collection identification):
- se-ux-ui-designer: Jobs-to-be-Done analysis, user journey mapping,
and Figma-ready UX research artifacts
- se-technical-writer: Creates technical documentation, blogs, and tutorials
- se-gitops-ci-specialist: CI/CD pipeline debugging and GitOps workflows
- se-product-manager-advisor: GitHub issue creation and product guidance
- se-responsible-ai-code: Bias testing, accessibility, and ethical AI
- se-system-architecture-reviewer: Architecture reviews with Well-Architected
- se-security-reviewer: OWASP Top 10/LLM/ML security and Zero Trust
Key Features:
- Each agent is completely standalone (no cross-dependencies)
- Concise display names for GitHub Copilot dropdown ("SE: [Role]")
- Fills gaps in awesome-copilot (UX design, content creation, CI/CD debugging)
- Enterprise patterns: OWASP, Zero Trust, WCAG, Well-Architected Framework
Collection manifest, auto-generated docs, and all agents follow
awesome-copilot conventions.
Source: https://github.com/niksacdev/engineering-team-agents
Learnings: https://medium.com/data-science-at-microsoft/the-ai-native-engineering-flow-5de5ffd7d877
* Fix Copilot review comments: table formatting and code block syntax
- Fix table formatting in docs/README.collections.md by converting multi-line
Software Engineering Team entry to single line
- Fix code block language in se-gitops-ci-specialist.agent.md from yaml to json
for package.json example (line 41-51)
- Change comment syntax from # to // to match JSON conventions
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Fix model field capitalization to match GitHub Copilot convention
- Change all agents from 'model: gpt-5' to 'model: GPT-5' (uppercase)
- Aligns with existing GPT-5 agents in the repo (blueprint-mode, gpt-5-beast-mode)
- Addresses Copilot reviewer feedback on consistency
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Add ADR and User Guide templates to Technical Writer agent
- Add Architecture Decision Records (ADR) template following Michael Nygard format
- Add User Guide template with task-oriented structure
- Include references to external best practices (ADR.github.io, Write the Docs)
- Update Specialized Focus Areas to reference new templates
- Keep templates concise without bloating agent definition
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Fix inconsistent formatting: DevOps/CI-CD to DevOps/CI/CD
- Change "DevOps/CI-CD" (hyphen) to "DevOps/CI/CD" (slash) for consistency
- Fixed in collection manifest, collection docs, and README
- Aligns with standard industry convention and agent naming
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Shorten collection description per maintainer feedback
- Brief description in table: "7 specialized agents covering the full software
development lifecycle from UX design and architecture to security and DevOps."
- Move detailed context (Medium article, design principles, agent list) to
usage section following edge-ai-tasks pattern
- Addresses @aaronpowell feedback: descriptions should be brief for table display
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -40,6 +40,7 @@ Curated collections of related prompts, instructions, and agents organized aroun
|
||||
| [Ruby MCP Server Development](../collections/ruby-mcp-development.md) | Complete toolkit for building Model Context Protocol servers in Ruby using the official MCP Ruby SDK gem with Rails integration support. | 3 items | ruby, mcp, model-context-protocol, server-development, sdk, rails, gem |
|
||||
| [Rust MCP Server Development](../collections/rust-mcp-development.md) | Build high-performance Model Context Protocol servers in Rust using the official rmcp SDK with async/await, procedural macros, and type-safe implementations. | 3 items | rust, mcp, model-context-protocol, server-development, sdk, tokio, async, macros, rmcp |
|
||||
| [Security & Code Quality](../collections/security-best-practices.md) | Security frameworks, accessibility guidelines, performance optimization, and code quality best practices for building secure, maintainable, and high-performance applications. | 6 items | security, accessibility, performance, code-quality, owasp, a11y, optimization, best-practices |
|
||||
| [Software Engineering Team](../collections/software-engineering-team.md) | 7 specialized agents covering the full software development lifecycle from UX design and architecture to security and DevOps. | 7 items | team, enterprise, security, devops, ux, architecture, product, ai-ethics |
|
||||
| [Swift MCP Server Development](../collections/swift-mcp-development.md) | Comprehensive collection for building Model Context Protocol servers in Swift using the official MCP Swift SDK with modern concurrency features. | 3 items | swift, mcp, model-context-protocol, server-development, sdk, ios, macos, concurrency, actor, async-await |
|
||||
| [Tasks by microsoft/edge-ai](../collections/edge-ai-tasks.md) | Task Researcher and Task Planner for intermediate to expert users and large codebases - Brought to you by microsoft/edge-ai | 3 items | architecture, planning, research, tasks, implementation |
|
||||
| [Technical Spike](../collections/technical-spike.md) | Tools for creation, management and research of technical spikes to reduce unknowns and assumptions before proceeding to specification and implementation of solutions. | 2 items | technical-spike, assumption-testing, validation, research |
|
||||
|
||||
Reference in New Issue
Block a user