Add Responsible AI Development Instructions

[keith-oak]

Summary

This PR adds three comprehensive instruction files aligned with Microsoft's Responsible AI principles to promote trustworthy AI development practices.

New Files

1. responsible-ai-development.instructions.md - Core framework implementing Microsoft's six Responsible AI principles:

   • Fairness: AI systems should treat all people fairly
   • Reliability and Safety: AI systems should perform reliably and safely
   • Privacy and Security: AI systems should be secure and respect privacy
   • Inclusiveness: AI systems should empower everyone
   • Transparency: AI systems should be understandable
   • Accountability: People should be accountable for AI systems

2. human-in-the-loop-development.instructions.md - Best practices for maintaining human oversight, validation, and decision-making in AI-assisted development workflows

3. inclusive-language-bias-awareness.instructions.md - Comprehensive guidelines for using inclusive, bias-aware language in code, documentation, and all technical artifacts

Updated Files

• CONTRIBUTING.md - Updated to emphasize Responsible AI development practices aligned with Microsoft's framework
• README.instructions.md - Automatically updated via npm run build to include the new instruction files

Key Features

• ✅ Aligned with Microsoft's Responsible AI principles
• ✅ Practical examples and checklists for each principle
• ✅ Development workflow integration guidance
• ✅ Comprehensive code examples in JavaScript/TypeScript
• ✅ Links to official Microsoft Responsible AI resources and tools
• ✅ Applies to all files (applyTo: '**')
• ✅ Tested with GitHub Copilot

Why This Matters

These instructions help developers:

• Keep humans in control while using AI assistance
• Build fair, secure, and inclusive AI-powered applications
• Follow industry best practices for AI development
• Uphold Microsoft's commitment to Responsible AI

Checklist

• Files follow naming conventions (lowercase-with-hyphens)
• Frontmatter includes required fields (description, applyTo)
• Description in single quotes and non-empty
• Ran npm run build to update README files
• Tested instructions with GitHub Copilot
• Uses inclusive language throughout
• Aligns with Microsoft Responsible AI principles

Testing

All instruction files have been tested with GitHub Copilot to ensure they provide effective guidance for AI-assisted development while promoting responsible practices.

[Copilot]

Pull Request Overview

This PR adds comprehensive Responsible AI development guidance aligned with Microsoft's six principles (Fairness, Reliability & Safety, Privacy & Security, Inclusiveness, Transparency, and Accountability) to enhance AI-assisted development practices.

Key additions include:

• Three new instruction files implementing Microsoft's Responsible AI framework
• Human-in-the-loop practices emphasizing developer oversight and validation
• Inclusive language guidelines for bias-aware technical communication

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
responsible-ai-development.instructions.md	Core framework implementing Microsoft's six Responsible AI principles with practical examples and checklists
inclusive-language-bias-awareness.instructions.md	Comprehensive guidelines for using inclusive, bias-aware language in all technical artifacts
human-in-the-loop-development.instructions.md	Best practices for maintaining human oversight and decision-making in AI-assisted workflows
README.instructions.md	Auto-generated updates adding the new instruction files to the documentation
CONTRIBUTING.md	Updated to emphasize Responsible AI development practices and Microsoft's framework

[aaronpowell]

Could you revert the changes to the CONTRIBUTING.md file as those kinds of changes are something I'd prefer to discuss where we have gaps in our current guidance and adapt rather than bring in directly.

[jeremiah-snee-openx]

Could you revert the changes to the CONTRIBUTING.md file as those kinds of changes are something I'd prefer to discuss where we have gaps in our current guidance and adapt rather than bring in directly.

@aaronpowell Usage?

• Collections Improvement with Tasks Collection POC #270
• Update Contributing Guide #301