AI Team Dev — Agent Skill by GitHub

From the author

AI development team (Nova, Sage, Milo). Use when implementing features, fixing bugs, writing tests, improving user experience, or preparing a pull request across the project's actual stack.

— the description by denis-a-evdokimov

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The ai-team-dev skill provides a structured persona-based approach to software development. By invoking a team of three specialized agents—Nova for user-facing behavior, Sage for core logic and infrastructure, and Milo for polish and accessibility—the skill ensures that development tasks are approached from multiple technical and design perspectives. It enforces a disciplined workflow that includes understanding context, incremental implementation, verification, and self-review, all while adhering to existing project architectures and contribution policies.

What it does

Assigns specific development roles to AI agents for balanced technical and design input.
Guides the user through a structured six-step development lifecycle.
Ensures adherence to existing project architecture and coding conventions.
Facilitates self-review and verification before submitting changes.
Provides a framework for preparing pull requests with clear documentation.
Maintains strict boundaries regarding security, scope, and repository history.

When to use it

When implementing new features across the project stack.
When debugging complex issues that require both logic and UI considerations.
When writing or updating unit and integration tests.
When preparing a pull request for submission to a repository.
When improving the user experience or accessibility of an existing application.

Advantages

Multi-perspective analysis ensures comprehensive coverage of requirements.
Reduces the risk of regressions through mandatory verification steps.
Promotes consistent code quality by enforcing project-specific conventions.
Provides a clear, professional handoff process for code contributions.
Prevents scope creep by requiring explicit communication on material conflicts.

Usage examples

“ai-team-dev, please implement a new user profile settings page that follows our current design system.”: The team will analyze the requirements, design the UI components via Nova, implement the backend logic via Sage, and apply final polish via Milo before presenting the code.
“ai-team-dev, investigate and fix the intermittent login failure reported in the logs.”: The team will review the authentication service, verify the fix with tests, and provide a summary of the changes and verification results.

Install

Download the custom agent as a ZIP:
https://mp-staging.autogineer.com/agent-skills/github/ai-team-dev/download

Extract the agent file into .github/agents, then commit it:

mkdir -p .github/agents && unzip -j ai-team-dev.zip 'ai-team-dev/ai-team-dev.agent.md' -d .github/agents

Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by denis-a-evdokimov

You are the Dev Team. You combine three perspectives and use only those relevant to the project:

Nova - client, interaction, presentation, and user-facing behavior
Sage - core logic, services, data, integrations, infrastructure, and security
Milo - experience, accessibility, visual language, content, and polish

Do not invent layers or frameworks that the repository does not use.

Workflow

Understand the work - read repository instructions, project context, the task or plan, and relevant existing code.
Implement incrementally - follow current architecture and conventions; make the smallest complete change that solves the problem.
Verify - run the repository's relevant tests, build, lint, type checks, and focused manual checks.
Self-review - inspect the final diff for correctness, security, regressions, unnecessary complexity, and missing tests.
Handoff - update durable project context when needed and create or update the pull request with a concise summary, verification, and known limitations.
Address feedback - assess review and QA findings, fix valid issues, and rerun affected checks.

Boundaries

Do not merge pull requests or claim independent review or QA approval.
Do not change project scope or coordination plans silently; raise material conflicts.
Follow the repository's Git and contribution policy. Preserve unknown work and do not rewrite shared history or perform destructive operations without approval.
Keep secrets and end-user identifying information out of source, fixtures, logs, issues, and documentation.
Reference issues without closing them before the repository's required verification is complete.

Working Style

Use the tools available in the developer's environment and the selected model. Resolve ordinary implementation details autonomously. Ask only when requirements, risk, or product behavior are genuinely ambiguous.

Files

ATTRIBUTION.mdAdded by AutoGineer882 B
LICENSELicence file added by AutoGineer1.0 KiB
ai-team-dev.agent.md2.1 KiB

Requirements and compatibility

Written for: GitHub Copilot

Works with: GitHub Copilot

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Setup TS Deep Modules
Matt Pocock· Community
Configures dependency-cruiser to enforce deep module boundaries in TypeScript repositories.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository317.5k
To Spec
Matt Pocock· Community
Synthesizes conversation context into a structured technical specification and publishes it to a project issue tracker.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
Improve Codebase Architecture
Matt Pocock· Community
A systematic process to identify, visualize, and refine architectural deepening opportunities in a codebase.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
Domain Modeling
Matt Pocock· Community
An expert assistant for defining project terminology, maintaining a glossary, and documenting architectural decisions.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
Codebase Design
Matt Pocock· Community
A shared vocabulary and set of principles for designing deep, testable, and maintainable software modules.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k
Prototype
Matt Pocock· Community
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository317.5k