Feature/sql skills updates

[brendankowitz]

Description

This pull request introduces four new agent definition files for the .github/agents directory, each describing a specialized AI coding agent with a clear role, focus areas, and task management approach. These agents are designed to collaborate efficiently by delegating tasks according to complexity, following modern software engineering practices, and enabling comprehensive code and architecture reviews.

The most important changes are:

Agent Definitions and Collaboration Strategy

• Added .github/agents/coding-agent.agent.md: Defines the "Coding Agent" as a modern code expert for refactoring, optimization, and enterprise patterns. Outlines delegation to the "Complex Coding Agent" for complex tasks and to the "Fast Coding Agent" for simple tasks, with explicit sub-task enumeration and parallel handoffs.
• Added .github/agents/complex-coding-agent.agent.md: Introduces the "Complex Coding Agent" for high-complexity tasks, emphasizing deep architectural thinking, multi-file debugging, and sophisticated solutions. Specifies delegation of medium-complexity tasks to the "Coding Agent" and simple tasks to the "Fast Coding Agent."
• Added .github/agents/fast-coding-agent.agent.md: Establishes the "Fast Coding Agent" for quick, focused coding tasks such as single-file edits and test/build fixes, with a strong emphasis on speed, accuracy, and escalation of complex dependencies.

Architecture and Code Review Automation

• Added .github/agents/well-architected-agent.agent.md: Provides a comprehensive framework for code and architecture reviews based on the Well-Architected Framework’s five pillars (Reliability, Security, Cost Optimization, Operational Excellence, Performance Efficiency), including detailed checklists, assessment methodology, and reporting templates for actionable recommendations.

Related issues

Addresses [issue #].

Testing

Describe how this change was tested.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.36%. Comparing base (a894a3b) to head (50b8a43).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5559      +/-   ##
==========================================
+ Coverage   77.02%   77.36%   +0.33%     
==========================================
  Files         983      985       +2     
  Lines       36007    36189     +182     
  Branches     5469     5498      +29     
==========================================
+ Hits        27736    27997     +261     
+ Misses       6927     6838      -89     
- Partials     1344     1354      +10     

see 29 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.