Create PRD for Visual Studio 2026 install support#53
Conversation
Added a Product Requirements Document (PRD) for Visual Studio 2026 installation support, detailing user-level and repository-level installation requirements, current gaps, and proposed solutions.
There was a problem hiding this comment.
Pull request overview
This PR adds a comprehensive Product Requirements Document (PRD) for implementing Visual Studio 2022/2026 installation support in the ai-agents repository. The PRD was generated through the AI agent system's orchestrator → analyst → explainer pipeline and proposes extending the existing multi-platform agent installer to support Visual Studio alongside the currently supported platforms (VS Code, GitHub Copilot CLI, and Claude Code).
The PRD identifies a critical blocker: while repository-level installation can be implemented immediately using the existing .github/agents/ path (shared with VS Code), the primary user request for user-level (global) installation is blocked due to undocumented Visual Studio agent storage paths. The document recommends filing questions with the Visual Studio team before proceeding with global installation support.
Key Changes
- Comprehensive research findings documenting Visual Studio 2022 17.14+ and VS 2026's support for custom agents
- Phased implementation plan separating ready-to-implement repository-level support from blocked user-level support
- Detailed technical design for Config.psd1 and install.ps1 changes following established patterns
- Specific blocking questions formulated for the Visual Studio team regarding global agent storage paths
|
Caution Review failedThe pull request is closed. Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. 📝 WalkthroughWalkthroughReplaced Visual Studio version strings and corrected PowerShell path backslashes in the planning PRD; expanded "MCP" to "Model Context Protocol"; added multiple session logs, a QA report, HANDOFF history edits, a small GitHub Actions checkout change, and two Serena memory docs. All changes are documentation/workflow; no public API changes. (≤50 words) Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20–30 minutes
Possibly related PRs
Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
📜 Recent review detailsConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.agents/planning/PRD-visual-studio-install-support.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (5)
**/.agents/**/*.md
📄 CodeRabbit inference engine (.agents/governance/interview-response-template.md)
Primary deliverables from agents should be saved to
.agents/[category]/[pattern].mdwith naming convention[PREFIX]-NNN-[description].mdSingle-source agent files should use frontmatter markers to delineate platform-specific sections for VS Code and Copilot CLI variants
Files:
.agents/planning/PRD-visual-studio-install-support.md
.agents/**/*.{md,yml,yaml,json}
📄 CodeRabbit inference engine (.agents/critique/001-agent-templating-critique.md)
For agent platform files, evaluate whether near-identical variants (99%+ overlap) can be consolidated with conditional configuration rather than maintaining separate files
Files:
.agents/planning/PRD-visual-studio-install-support.md
.agents/**/*.md
📄 CodeRabbit inference engine (.agents/retrospective/pr43-coderabbit-root-cause-analysis.md)
.agents/**/*.md: Use PREFIX-NNN naming convention (e.g., EPIC-001, CRITIQUE-001) for sequenced artifacts and type-prefixed naming (e.g., prd-, tasks-) for non-sequenced artifacts
Normalize all file paths in markdown documents to be repository-relative before committing, removing absolute machine-specific paths
Files:
.agents/planning/PRD-visual-studio-install-support.md
.agents/planning/**/*.md
📄 CodeRabbit inference engine (.agents/retrospective/pr43-coderabbit-root-cause-analysis.md)
Create CI validation checks to extract and compare effort estimates across related planning documents (epics, PRDs, tasks, memory) and flag discrepancies exceeding 20%
Files:
.agents/planning/PRD-visual-studio-install-support.md
.agents/**
⚙️ CodeRabbit configuration file
Agent configuration files. Only flag security issues or broken cross-references. Ignore style, formatting, and structure.
Files:
.agents/planning/PRD-visual-studio-install-support.md
🪛 LanguageTool
.agents/planning/PRD-visual-studio-install-support.md
[uncategorized] ~22-~22: The official name of this software platform is spelled with a capital “H”.
Context: ...ndary) | 🟢 Ready | Can reuse VS Code's .github/agents/ approach | Recommendation...
(GITHUB)
[uncategorized] ~37-~37: The official name of this software platform is spelled with a capital “H”.
Context: ...ub Copilot CLI | ~/.copilot/agents/ | .github/agents/ | ✅ Supported (global has know...
(GITHUB)
[uncategorized] ~38-~38: The official name of this software platform is spelled with a capital “H”.
Context: ...Chat | %APPDATA%\Code\User\prompts\ | .github/agents/ | ✅ Supported | | **Visual Stu...
(GITHUB)
[uncategorized] ~39-~39: The official name of this software platform is spelled with a capital “H”.
Context: ...Visual Studio 2022/2026** | ❓ Unknown | .github/agents/ | ❌ Not Supported | ### G...
(GITHUB)
[uncategorized] ~45-~45: The official name of this software platform is spelled with a capital “H”.
Context: .... While repository-level installation (.github/agents/) technically works in VS 2022+...
(GITHUB)
[grammar] ~76-~76: Use a hyphen to join words.
Context: ...ject - Feature Flag: "Enable project specific .NET instructions" (auto-enable...
(QB_NEW_EN_HYPHEN)
[uncategorized] ~90-~90: The official name of this software platform is spelled with a capital “H”.
Context: ... | Medium | Roaming profile pattern | | %USERPROFILE%\.github\agents\ | Low | Cross-IDE sharing | | ...
(GITHUB)
[uncategorized] ~99-~99: The official name of this software platform is spelled with a capital “H”.
Context: ...tructions via: - Repository-level: .github/copilot-instructions.md ✅ - **Targeted...
(GITHUB)
[uncategorized] ~100-~100: The official name of this software platform is spelled with a capital “H”.
Context: ...ions.md✅ - **Targeted instructions**:.github/instructions/*.instructions.md` ✅ - **U...
(GITHUB)
[uncategorized] ~111-~111: The official name of this software platform is spelled with a capital “H”.
Context: ... as VS Code** since both IDEs read from .github/agents/. Implementation: ```powe...
(GITHUB)
[uncategorized] ~129-~129: The official name of this software platform is spelled with a capital “H”.
Context: ...S Code and Visual Studio share the same .github/agents/ location for repo-level agents...
(GITHUB)
[uncategorized] ~179-~179: The official name of this software platform is spelled with a capital “H”.
Context: ...as option | | FR-1.2 | Deploy agents to .github/agents/ | All *.agent.md files copie...
(GITHUB)
[uncategorized] ~180-~180: The official name of this software platform is spelled with a capital “H”.
Context: ...ion | | FR-1.3 | Deploy instructions to .github/ | copilot-instructions.md installed...
(GITHUB)
[style] ~296-~296: This phrase is redundant. Consider using “outside”.
Context: ...pport user-level (global) custom agents outside of .github/agents/? > 2. If so, what fil...
(OUTSIDE_OF)
[uncategorized] ~296-~296: The official name of this software platform is spelled with a capital “H”.
Context: ...level (global) custom agents outside of .github/agents/? > 2. If so, what file system ...
(GITHUB)
[uncategorized] ~413-~413: The official name of this software platform is spelled with a capital “H”.
Context: ...tom agents stored outside of repository .github/agents/ folders? If so, what is the re...
(GITHUB)
🔍 Remote MCP DeepWiki
Additional Context from DeepWiki
-
.agents/Directory Conventions
The repository uses a standardized.agents/directory structure where each subdirectory is authored by a specific agent type. In particular, theplanning/directory is the designated location for planning documents written by theplanner_agent. Files here typically follow a numeric prefix naming convention (NNN-*-plan.md) to ensure consistency and ordering. -
New PRD Placement & Naming
- The pull request adds
PRD-visual-studio-install-support.mdunder.agents/planning/, which is the correct subdirectory for a planning document. - However, the filename deviates from the established
NNN-*-plan.mdpattern. Consider renaming to align with the numeric prefix convention (e.g.,053-visual-studio-install-plan.md) for consistency with other planning artifacts.
- The pull request adds
-
Relevant Guidelines
For details on directory usage and naming conventions, seeUSING-AGENTS.mdin the root of the repo. This file outlines how planners should structure and name their documents within the.agents/planning/directory.
🔇 Additional comments (1)
.agents/planning/PRD-visual-studio-install-support.md (1)
11-107: PRD structure and blocking strategy are solid.The document clearly identifies the blocker (unknown user-level path), splits work into phases (repo-level can proceed now; user-level is blocked), and proposes a pragmatic discovery approach. The blocking questions are well-formulated and have clear impact statements. Effort estimates (4–8 hours total) are reasonable.
The phased approach with a decision tree (lines 358–373) lets you ship interim value (repo-level support) while unblocking user-level work via discovery questions.
|
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. 📝 WalkthroughWalkthroughAdds a comprehensive planning document (PRD) for Visual Studio 2022/2026 installation support in ai-agents. Outlines a phased approach starting with repository-level installation, moving toward user-level global installation, with functional requirements, configuration changes, technical design snippets, and implementation milestones. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10–15 minutes This is a planning document with no code changes. Review focuses on validating proposed approach, phased milestones, and identified blockers. No implementation to validate yet.
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (2)
.agents/planning/PRD-visual-studio-install-support.md (2)
118-118: Update DisplayName and menu to reflect 2022/2026 support scope.PRD explicitly targets VS 2022 17.14+ and VS 2026, but DisplayName and menu only mention "2026". Update all occurrences to "Visual Studio 2022/2026" to accurately reflect support scope and avoid confusing VS 2022 users.
- Lines 118 & 233: - DisplayName = "Visual Studio 2026" + DisplayName = "Visual Studio 2022/2026" - Line 258: - Write-Host " 4. Visual Studio 2026" + Write-Host " 4. Visual Studio 2022/2026"Also applies to: 233-233, 258-258
93-93: Define MCP acronym on first use.MCP appears without definition. Expand to "MCP (Model Context Protocol)" on first mention for clarity.
-**Related Configuration**: Visual Studio reads MCP server configs from `%USERPROFILE%\.mcp.json` globally, suggesting a similar pattern *may* exist for agents. +**Related Configuration**: Visual Studio reads MCP (Model Context Protocol) server configs from `%USERPROFILE%\.mcp.json` globally, suggesting a similar pattern *may* exist for agents.
🧹 Nitpick comments (1)
.agents/planning/PRD-visual-studio-install-support.md (1)
109-133: Clarify value proposition of Phase 1 repo-level support.Phase 1 states VS Code and Visual Studio both use
.github/agents/, making Phase 1 "effectively already supported via the VS Code installer" (line 129-130). However, Phase 1 justification claims value from "user intent" and "VS-specific messages." This is minimal incremental value for 1-2 hours of work.Recommendation: Either justify Phase 1 as a low-effort stopgap while pursuing the real blocker (Phase 0 answers for user-level support), or defer Phase 1 if repo-level setup via VS Code installer is acceptable interim solution.
Verify with stakeholders (Matt Kotsenas per line 7) whether Phase 1 repo-level support is worth implementing before Phase 3 user-level support is unblocked.
📜 Review details
Configuration used: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.agents/planning/PRD-visual-studio-install-support.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (5)
**/.agents/**/*.md
📄 CodeRabbit inference engine (.agents/governance/interview-response-template.md)
Primary deliverables from agents should be saved to
.agents/[category]/[pattern].mdwith naming convention[PREFIX]-NNN-[description].mdSingle-source agent files should use frontmatter markers to delineate platform-specific sections for VS Code and Copilot CLI variants
Files:
.agents/planning/PRD-visual-studio-install-support.md
.agents/**/*.{md,yml,yaml,json}
📄 CodeRabbit inference engine (.agents/critique/001-agent-templating-critique.md)
For agent platform files, evaluate whether near-identical variants (99%+ overlap) can be consolidated with conditional configuration rather than maintaining separate files
Files:
.agents/planning/PRD-visual-studio-install-support.md
.agents/**/*.md
📄 CodeRabbit inference engine (.agents/retrospective/pr43-coderabbit-root-cause-analysis.md)
.agents/**/*.md: Use PREFIX-NNN naming convention (e.g., EPIC-001, CRITIQUE-001) for sequenced artifacts and type-prefixed naming (e.g., prd-, tasks-) for non-sequenced artifacts
Normalize all file paths in markdown documents to be repository-relative before committing, removing absolute machine-specific paths
Files:
.agents/planning/PRD-visual-studio-install-support.md
.agents/planning/**/*.md
📄 CodeRabbit inference engine (.agents/retrospective/pr43-coderabbit-root-cause-analysis.md)
Create CI validation checks to extract and compare effort estimates across related planning documents (epics, PRDs, tasks, memory) and flag discrepancies exceeding 20%
Files:
.agents/planning/PRD-visual-studio-install-support.md
.agents/**
⚙️ CodeRabbit configuration file
Agent configuration files. Only flag security issues or broken cross-references. Ignore style, formatting, and structure.
Files:
.agents/planning/PRD-visual-studio-install-support.md
🪛 LanguageTool
.agents/planning/PRD-visual-studio-install-support.md
[uncategorized] ~22-~22: The official name of this software platform is spelled with a capital “H”.
Context: ...ndary) | 🟢 Ready | Can reuse VS Code's .github/agents/ approach | Recommendation...
(GITHUB)
[uncategorized] ~37-~37: The official name of this software platform is spelled with a capital “H”.
Context: ...ub Copilot CLI | ~/.copilot/agents/ | .github/agents/ | ✅ Supported (global has know...
(GITHUB)
[uncategorized] ~38-~38: The official name of this software platform is spelled with a capital “H”.
Context: ...Chat | %APPDATA%\Code\User\prompts\ | .github/agents/ | ✅ Supported | | **Visual Stu...
(GITHUB)
[uncategorized] ~39-~39: The official name of this software platform is spelled with a capital “H”.
Context: ...Visual Studio 2022/2026** | ❓ Unknown | .github/agents/ | ❌ Not Supported | ### G...
(GITHUB)
[uncategorized] ~45-~45: The official name of this software platform is spelled with a capital “H”.
Context: .... While repository-level installation (.github/agents/) technically works in VS 2022+...
(GITHUB)
[grammar] ~76-~76: Use a hyphen to join words.
Context: ...ject - Feature Flag: "Enable project specific .NET instructions" (auto-enable...
(QB_NEW_EN_HYPHEN)
[uncategorized] ~90-~90: The official name of this software platform is spelled with a capital “H”.
Context: ... | Medium | Roaming profile pattern | | %USERPROFILE%\.github\agents\ | Low | Cross-IDE sharing | | ...
(GITHUB)
[uncategorized] ~99-~99: The official name of this software platform is spelled with a capital “H”.
Context: ...tructions via: - Repository-level: .github/copilot-instructions.md ✅ - **Targeted...
(GITHUB)
[uncategorized] ~100-~100: The official name of this software platform is spelled with a capital “H”.
Context: ...ions.md✅ - **Targeted instructions**:.github/instructions/*.instructions.md` ✅ - **U...
(GITHUB)
[uncategorized] ~111-~111: The official name of this software platform is spelled with a capital “H”.
Context: ... as VS Code** since both IDEs read from .github/agents/. Implementation: ```powe...
(GITHUB)
[uncategorized] ~129-~129: The official name of this software platform is spelled with a capital “H”.
Context: ...S Code and Visual Studio share the same .github/agents/ location for repo-level agents...
(GITHUB)
[uncategorized] ~179-~179: The official name of this software platform is spelled with a capital “H”.
Context: ...as option | | FR-1.2 | Deploy agents to .github/agents/ | All *.agent.md files copie...
(GITHUB)
[uncategorized] ~180-~180: The official name of this software platform is spelled with a capital “H”.
Context: ...ion | | FR-1.3 | Deploy instructions to .github/ | copilot-instructions.md installed...
(GITHUB)
[style] ~296-~296: This phrase is redundant. Consider using “outside”.
Context: ...pport user-level (global) custom agents outside of .github/agents/? > 2. If so, what fil...
(OUTSIDE_OF)
[uncategorized] ~296-~296: The official name of this software platform is spelled with a capital “H”.
Context: ...level (global) custom agents outside of .github/agents/? > 2. If so, what file system ...
(GITHUB)
[uncategorized] ~413-~413: The official name of this software platform is spelled with a capital “H”.
Context: ...tom agents stored outside of repository .github/agents/ folders? If so, what is the re...
(GITHUB)
🔍 Remote MCP DeepWiki, GitHub Copilot
Perfect! Now I have comprehensive information. Let me compile the findings into a focused review summary.
PR #53 Review Context Summary
Repository Context
The ai-agents repository is a multi-platform coordinated agent system designed for software development with specialized AI agents that handle different phases of the development lifecycle, supporting VS Code (GitHub Copilot), GitHub Copilot CLI, and Claude Code CLI platforms.
The system consists of 18 specialized agents implemented across three platforms, resulting in 54 agent definition files organized into platform-specific directories (vs-code-agents/, copilot-cli/, claude/), with a cloudmcp-manager server providing persistent cross-session memory.
PR Details
PR #53 adds a comprehensive PRD document (534 lines, documentation-only change) for Visual Studio 2022/2026 install support that documents requirements, research findings, blocking questions for the VS team, and a phased implementation plan.
The PR has 6 active review threads with comments from both Copilot code reviewer and CodeRabbit, identifying issues around: inconsistent naming of VS versions (should include VS 2022), undefined acronyms (MCP), file naming conventions, and PowerShell syntax errors.
Related Issue Context
Issue #51 requests install support for Visual Studio 2026 with both user-level and repository-level installation capabilities. The PRD documents that user-level (global) installation is BLOCKED due to unknown user-level agent storage paths requiring answers from Visual Studio team, while repository-level installation is ready to implement using the same .github/agents/ destination as VS Code.
Key PRD Content
The PRD includes blocking questions to the Visual Studio team about: user-level agent storage paths, whether support exists in VS 2022 17.14+ or VS 2026 only, and whether there's a programmatic path discovery mechanism.
The implementation plan is organized in four phases: Phase 0 (ask blockers), Phase 1 (repository-level support, estimated 1-2 hours), Phase 2 (empirical discovery, estimated 2-4 hours), and Phase 3 (user-level support, blocked pending answers, estimated 1-2 hours).
Review Findings to Address
The active review has identified several issues to resolve:
- Naming consistency: DisplayName and menu options should reflect "Visual Studio 2022/2026" not just "2026" to match the broader scope discussed throughout the PRD
- Acronym definition: MCP should be expanded to "Model Context Protocol" on first use
- File naming convention: Consider following repository patterns with lowercase prefix (prd-visual-studio-install-support.md) or numeric sequence
- PowerShell syntax errors: Path on line 238 uses single quotes and forward slashes, preventing variable expansion; should use double quotes and backslashes
🔇 Additional comments (1)
.agents/planning/PRD-visual-studio-install-support.md (1)
305-355: Verify effort estimates against related planning documents.Per coding guidelines, effort estimates should be validated against related planning documents (epics, tasks, issue #51) and flagged if discrepancies exceed 20%. Phase 1 (1-2 hours), Phase 2 (2-4 hours), and Phase 3 (1-2 hours) are documented here.
Check if issue #51 or other related planning documents contain conflicting effort estimates that exceed a 20% variance. Run the CI validation check if available.
- Fix PowerShell path syntax: use double quotes and Windows backslashes for proper $env: variable expansion - Update DisplayName to "Visual Studio 2022/2026" for accuracy since PRD covers both VS 2022 (17.14+) and VS 2026 - Define MCP acronym as "Model Context Protocol" on first use - Rename file from uppercase PRD- to lowercase prd- per convention 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
All review feedback addressed in commit eccd28d. Fixed:
|
AI Quality Gate ReviewTip ✅ Final Verdict: PASS WalkthroughThis PR was reviewed by six AI agents in parallel, analyzing different aspects of the changes:
Review Summary
QA Review DetailsBased on my analysis, I can now provide the QA review: QA Review: PRD Visual Studio Install SupportTest Coverage Assessment
Quality Concerns
Regression Risk Assessment
Documentation Quality Check
Changes Verified
DevOps Review DetailsNow I'll review the PR changes and related infrastructure to complete the DevOps review. I have reviewed the PR. This is a documentation-only PR that renames a PRD file (from uppercase to lowercase) and makes minor text clarifications. Let me provide my DevOps assessment. DevOps Review: Visual Studio Install Support PRDPipeline Impact Assessment
CI/CD Quality Checks
Findings
Template Assessment
Automation Opportunities
Recommendations
VerdictRoadmap Review DetailsLet me also check the product roadmap to understand strategic alignment. Now I have complete context for the roadmap review. Let me provide my strategic assessment. Strategic Alignment Assessment
Feature Completeness
Impact Analysis
Concerns
Recommendations
VerdictArchitect Review DetailsDesign Quality Assessment
Overall Design Score: 5/5 Architectural Concerns
Breaking Change Assessment
Technical Debt Analysis
ADR Assessment
Recommendations
VerdictAnalyst Review DetailsAnalysis: PR Review - PRD Visual Studio Install SupportCode Quality Score
Overall: 5/5 Impact Assessment
Findings
Recommendations
VerdictSecurity Review DetailsSecurity Analysis: PRD for Visual Studio 2026 Install SupportFindings
Analysis SummaryThis PR contains only documentation changes to a Product Requirements Document (PRD). The file is a planning document that:
The example PowerShell snippets reference standard Windows environment variables ( RecommendationsNone required. This is a documentation-only change with no security implications. VerdictRun Details
Powered by AI Quality Gate - View Workflow |
Completed bigboss HCOM request to process 20 notifications within 59 minutes. Results: - PR #147: All 29 comments addressed, fixes implemented (commit 663cf23) - PR #53: Scope clarified from 2022/2026 to 2026 only - 18 notifications triaged (14 merged, 4 closed - no action required) Execution: 12 minutes actual time vs 59-minute deadline Quality: 100% of URGENT items completed Generated with Claude Code
Session 41 summary: - Processed 20 GitHub notifications within 59-minute deadline - PR #147: All 29 comments addressed, fixes implemented - PR #53: Scope clarified to 2026 only - Stale notifications triaged (14 merged, 4 closed) - Execution time: 12 minutes (under deadline) Ready for next session: PR #147 human review, PR #53 approval Generated with Claude Code
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
.agents/HANDOFF.md (1)
97-118: Use markdown link format for session log reference.Per coding guidelines, session log references in HANDOFF.md should use markdown link format
[Session NN](./sessions/YYYY-MM-DD-session-NN.md)for navigation. Line 109 currently uses plain text path.🔎 Proposed fix
**Artifacts**: -- Session log: `.agents/sessions/2025-12-20-session-41-batch-notification-review.md` +- Session log: [Session 41](./sessions/2025-12-20-session-41-batch-notification-review.md) - Batch analysis: `.agents/pr-batch-review-session-2025-12-20.md` - PR #147 comments and tasks: `.agents/pr-comments/PR-147/`
📜 Review details
Configuration used: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.agents/HANDOFF.md(2 hunks).agents/sessions/2025-12-20-session-41-batch-notification-review.md(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- .agents/sessions/2025-12-20-session-41-batch-notification-review.md
🧰 Additional context used
📓 Path-based instructions (5)
**/.agents/**/*.md
📄 CodeRabbit inference engine (.agents/governance/interview-response-template.md)
Primary deliverables from agents should be saved to
.agents/[category]/[pattern].mdwith naming convention[PREFIX]-NNN-[description].mdSingle-source agent files should use frontmatter markers to delineate platform-specific sections for VS Code and Copilot CLI variants
Files:
.agents/HANDOFF.md
.agents/**/*.{md,yml,yaml,json}
📄 CodeRabbit inference engine (.agents/critique/001-agent-templating-critique.md)
For agent platform files, evaluate whether near-identical variants (99%+ overlap) can be consolidated with conditional configuration rather than maintaining separate files
Files:
.agents/HANDOFF.md
.agents/**/*.md
📄 CodeRabbit inference engine (.agents/retrospective/pr43-coderabbit-root-cause-analysis.md)
.agents/**/*.md: Use PREFIX-NNN naming convention (e.g., EPIC-001, CRITIQUE-001) for sequenced artifacts and type-prefixed naming (e.g., prd-, tasks-) for non-sequenced artifacts
Normalize all file paths in markdown documents to be repository-relative before committing, removing absolute machine-specific paths
.agents/**/*.md: Session logs and documentation must include Phase checklist verification (Phase 1-3 protocol compliance including agent activation, instruction reading, handoff file updates, and session logging)
Session logs must document Session ID, date, agent name, and branch information in a standardized header formatAll artifact files in .agents/ must be in Markdown format
Document analysis recommendations with specific rationale when adding new governance documents like PROJECT-CONSTRAINTS.md
Maintain debugging skills documentation in
.agents/directoryDocument implementation notes explaining deviations from user prompts or decisions made during development (e.g., using plural form for directory names)
Files:
.agents/HANDOFF.md
.agents/HANDOFF.md
📄 CodeRabbit inference engine (.agents/SESSION-END-PROMPT.md)
.agents/HANDOFF.md: Update.agents/HANDOFF.mdwith current phase and task status, what was completed, what's next, any blockers/concerns, and branch state
Verify HANDOFF.md accurately reflects current state so next session can start from it aloneRead
.agents/HANDOFF.mdthird - contains previous session context and current stateMaintain HANDOFF.md with current project context, phase completion status, next phase preparation, and any blockers for session continuity
Create and maintain .agents/HANDOFF.md for enhancement project documentation and handoff protocols
Update HANDOFF.md document at the end of each session with current state, what's next, blockers, and session history
Update
.agents/HANDOFF.mdto document the canonical MCP config formats for each client (Claude, VS Code, Copilot CLI) and reference the new sync tooling documentation
.agents/HANDOFF.md: Link the session log in HANDOFF.md using format[Session NN](./sessions/YYYY-MM-DD-session-NN.md)when updating handoff information
Update.agents/HANDOFF.mdwith session log link and relevant information before ending a sessionHANDOFF.md must be updated at session end with session summary and decisions before changes are committed
.agents/HANDOFF.md: Read.agents/HANDOFF.mdat the start of each session to understand context
Update.agents/HANDOFF.mdat the end of each sessionUpdates to
.agents/HANDOFF.mdmust be completed before session closingUpdate
.agents/HANDOFF.mdwith new session entries that include session number, date, branch, objective, and key implementation detailsHANDOFF.md updates from parallel sessions MUST be consolidated by an orchestrator agent to prevent staging conflicts and ensure single authoritative state
.agents/HANDOFF.md: HANDOFF.md MUST be updated at session end with: session log link, brief summary, work completed, next steps, and updated status for all affected phases
Parallel agent execution MUST use orchestrator-coordinated HANDOFF updat...
Files:
.agents/HANDOFF.md
.agents/**
⚙️ CodeRabbit configuration file
Agent configuration files. Only flag security issues or broken cross-references. Ignore style, formatting, and structure.
Files:
.agents/HANDOFF.md
🔇 Additional comments (1)
Combined session histories from main and PR #201 feature branch: - Sessions 61-58: From main (PRs #223, #53) - Sessions 57-55: Parallel work on #222 and #201 Expanded to Last 10 to capture full context of parallel work streams. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Initial plan * feat(copilot): add context synthesis system for intelligent issue assignment - Add Invoke-CopilotAssignment.ps1 script for synthesizing context from trusted sources - Add copilot-synthesis.yml config with maintainers and AI agents configuration - Add Pester tests (60 tests) for the synthesis script - Update SKILL.md with documentation for copilot operations Implements Issue #92 Phase 1 Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com> * chore: verify implementation and documentation Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com> * refactor(copilot): improve code cohesion and DRY - Move reusable functions to GitHubHelpers.psm1: - Get-IssueComments, Update-IssueComment, New-IssueComment - Get-TrustedSourceComments (useful for pr-comment-responder) - Move script from scripts/copilot/ to scripts/issue/ (no nested dir) - Move config from .github/ to .claude/skills/github/ (app config) - Use config extraction patterns in Get-CodeRabbitPlan - Fix timestamp to use Get-Date -AsUTC - Remove unused $IssueTitle parameter from New-SynthesisComment - Fix regex efficiency (remove redundant Where-Object) - Update tests to reflect new structure Addresses PR review feedback from @rjmurillo Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com> * fix: address PR review feedback - YAML parsing and functional tests - Fix YAML parsing bug: synthesis marker regex now specifically targets 'synthesis:' section to avoid matching 'ai_triage.marker' first - Add 29 functional tests that execute functions and verify behavior: - Get-MaintainerGuidance: empty input, bullet extraction, checkboxes - Get-CodeRabbitPlan: implementation extraction, issue references - Get-AITriageInfo: priority/category extraction - Find-ExistingSynthesis: idempotency marker detection - New-SynthesisComment: comment generation with all sections - Get-SynthesisConfig: YAML parsing and marker extraction Total: 90 tests pass (61 pattern-based + 29 functional) Co-authored-by: rjmurillo-bot <250269933+rjmurillo-bot@users.noreply.github.com> * fix: address code review feedback from copilot-pull-request-reviewer - Use deep copy for config hashtable to avoid modifying defaults - Wrap ForEach-Object results in @() to ensure arrays (not null) - Use JSON payload via --input for large comment bodies in both Update-IssueComment and New-IssueComment functions All 146 tests pass. Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com> * fix: correct module path and corrupted Unicode in Invoke-CopilotAssignment Addresses cursor[bot] review comments: - Fix module path: Use "../.." to navigate from scripts/issue/ to modules/ (was using only ".." which resolved to non-existent scripts/modules/) - Fix corrupted Unicode: Replace corrupted emoji in related_prs pattern with correct link emoji Comment-ID: 2637061449, 2637061451 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat: add Copilot and cursor[bot] to trusted AI agents Add PR reviewers to ai_agents trusted sources: - Copilot (GitHub Copilot) - cursor[bot] (Cursor Bugbot) Updated both config file and script defaults. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: add extensive documentation to copilot-synthesis.yml Add comprehensive inline documentation covering: - Purpose and overview of the synthesis system - Usage examples and related files - Detailed explanation of trusted_sources section - Description of each AI agent and their contributions - Extraction patterns with examples - Synthesis marker and idempotency behavior - Extension guide for adding maintainers, agents, and patterns 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * refactor: move rjmurillo-bot from maintainers to ai_agents rjmurillo-bot is a bot account, so it belongs in ai_agents rather than maintainers. Updated config, script defaults, and tests to match. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(workflow): add copilot-context-synthesis automation for Issue #92 Implements the GitHub Actions workflow for automated Copilot context synthesis and assignment when the 'copilot-ready' label is added. Changes: - Create .github/workflows/copilot-context-synthesis.yml workflow - Triggers on issues:labeled event with 'copilot-ready' gate - Supports workflow_dispatch for manual testing - Generates step summary on success - Fix empty comments handling in Invoke-CopilotAssignment.ps1 - Wrap comments in @() to ensure array even if null - Fix Get-TrustedSourceComments in GitHubHelpers.psm1 - Add [AllowEmptyCollection()] attribute - Return empty array early for empty input Addresses all acceptance criteria from Issue #92 Phase 4. Fixes #92 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(workflow): remove copilot-ready label after successful synthesis - Add step to remove the copilot-ready label after successful processing - Only removes label for labeled trigger (not workflow_dispatch) - Update step summary to reflect label removal action Also created the copilot-ready label: - Color: #6e40c9 (GitHub Copilot purple) - Description: Triggers automated context synthesis and Copilot assignment 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(workflow): add scheduled sweep for eventual consistency Add a second job that runs hourly to catch any missed issues: - schedule: Runs every hour via cron "0 * * * *" - sweep-missed job: Lists all open issues with copilot-ready label - Processes each issue using the same Invoke-CopilotAssignment.ps1 (DRY) - Removes label after successful processing - Continues processing even if individual issues fail Smart workflow_dispatch modes: - With issue_number: Process single issue - Without issue_number: Run sweep mode Both jobs use the same PowerShell script as the single source of truth, ensuring consistent behavior across all trigger types. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs(planning): add PR #147 review feedback action plan Comprehensive analysis of 56 review comments: - 47 addressed (84%), 9 pending (16%) - P0 (Blocking): 0 - All resolved - P1 (High): 2 items (functional tests complete) - P2 (Medium): 4 items (deferred to follow-up) - P3 (Low): 3 items (cosmetic) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs(handoff): add PR #147 session summary Session 38: Executed action plan for PR #147 review feedback - Verified 90/90 tests pass (including functional tests) - Posted summary comment and re-requested review from rjmurillo - All P1 items complete, P2-P3 deferred to follow-up 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(copilot-synthesis): improve regex and AI visibility check - Use non-greedy regex quantifier with boundary for maintainers/ai_agents extraction to prevent over-matching in YAML parsing (P2-001) - Add RelatedPRs to hasAIContent check so AI recommendations section displays when only related PRs exist (P2-002) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs(governance): add test location standards Define where test files should be located: - All Pester tests in /tests/ directory at repo root - Naming convention: {ScriptName}.Tests.ps1 - Pattern-based vs functional test organization Addresses P2-003 from PR #147 review feedback. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(copilot-synthesis): add JSON schema for config validation Define JSON Schema for copilot-synthesis.yml covering: - trusted_sources (maintainers, ai_agents) - extraction_patterns (coderabbit, ai_triage) - synthesis (marker) Enables IDE validation and autocompletion for config files. Addresses P2-004 from PR #147 review feedback. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * test(copilot-synthesis): add edge case tests and AAA documentation Add edge case test coverage for: - Empty and malformed config file handling - Multiple maintainer comments order preservation - Unicode character handling in patterns - RelatedPRs visibility in AI section Add test approach documentation explaining: - Pattern-based tests for structural validation - Functional tests for behavior verification - Why both approaches are used together Addresses P3-001 and P3-003 from PR #147 review feedback. Total tests: 100 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(skills): import CodeRabbit AI learnings as skills Import 12 learnings from CodeRabbit AI export, validating each for atomicity and checking against existing skills for duplicates. Summary: - 8 valid skills created (7 new + 1 supplementary) - 4 duplicates identified (already in skills-linting) - Cross-reference added to skills-linting Skills added: - Skill-CodeRabbit-001: MCP tool path case sensitivity (95%) - Skill-CodeRabbit-002: Template bracket notation placeholders (93%) - Skill-CodeRabbit-003: Infrastructure naming avoids spaces (90%) - Skill-CodeRabbit-004: Expression injection labeling is intentional (95%) - Skill-CodeRabbit-005: MCP tool naming with duplicated segments (92%) - Skill-CodeRabbit-006: Generated files omit edit warnings (90%) - Skill-CodeRabbit-007: Analyst vs impact analysis architecture (95%) - Skill-CodeRabbit-008: Nested code fence syntax (88%) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(skills): address Copilot review comments on skills-coderabbit-learnings - Fix numeric count: change 'Valid Skills Created: 7' to 8 (correct count) - Clarify nested code fence syntax: replace inline backticks with 'four backticks' - Add MCP tool naming breakdown: concrete example showing server/tool-id segments Addresses PR #201 review comments from @Copilot: - Comment 2638064485 (line 10 numeric correction) - Comment 2638064487 (line 107 backtick clarity) - Comment 2638064489 (line 52 MCP naming example) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs(session): add PR #201 review response artifacts - Session log for 3 Copilot comment responses - QA report for skills clarity fixes * docs(session): add Session 56 - PR #201 review response Session 56 completed PR #201 review comment response workflow: - Acknowledged 2 NEW Copilot review comments with eyes emoji - Created comment map at .agents/pr-comments/PR-201/comments.md - Verified all 3 Copilot comments already fixed in d69707b - Posted resolution replies to comments 2638064487 and 2638064489 - Updated HANDOFF.md with session summary All 3 Copilot review comments addressed: - 2638064485: Count corrected (7 to 8) + replied - 2638064487: Backtick clarity fix + replied - 2638064489: MCP naming breakdown + replied 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs(session): update Session 56 with final commit SHA Final validation passed with commit SHA baa3e87. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(skills): clarify MCP tool naming and nested code fence syntax per Copilot review - Skill-CodeRabbit-005: Add explicit breakdown of MCP identifier segments - Skill-CodeRabbit-008: Replace backtick with quoted text to avoid formatting issues Addresses review comments: - r2638064487: Nested code fence backtick escaping - r2638064489: MCP tool naming pattern clarification * fix(docs): correct skill count and session log comment count Addresses PR review comments from Copilot - Fixed partial duplicate explanation (8+4=12, not 8+4+1=13) - Corrected session log from '3 NEW comments' to '2 NEW comments' Comment-IDs: 2638129806, 2638129810 * fix(handoff): resolve merge conflict and update session history - Resolve merge conflict in HANDOFF.md (Session 56 vs Session 55) - Update current phase to Session 57 - Add Session 57 and 56 to session history table - Session 55 reference remains correct (mcp-prd-planning.md) Addresses Copilot review comments: - Comment 2638159077: Merge conflict resolution - Comment 2638159082: Session history table accuracy * docs: complete session 57 log with work performed Session 57 addressed 2 NEW Copilot comments: - Merge conflict in HANDOFF.md (resolved) - Session history table accuracy (updated) All 8 phases completed successfully. * docs: finalize session 57 log with session end checklist All MUST requirements completed: - HANDOFF.md updated with Session 57 - Session log complete - Markdown lint passed (0 errors, 138 files) - All changes committed (0c6f610, bacdf92) - Git status clean * fix(handoff): merge session histories from both branches Combined session histories from main and PR #201 feature branch: - Sessions 61-58: From main (PRs #223, #53) - Sessions 57-55: Parallel work on #222 and #201 Expanded to Last 10 to capture full context of parallel work streams. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs(skills): add HANDOFF.md merge session history skill Skill-Workflow-011: Merge session histories chronologically when resolving HANDOFF.md conflicts, preserving parallel work streams. Lesson learned from PR #201 merge conflict where feature branch session history was initially discarded instead of merged. Artifacts: - Skill-Workflow-011 in multi-agent-workflow.md (atomicity: 92%) - Serena memory: pattern-handoff-merge-session-histories 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: rjmurillo <6811113+rjmurillo@users.noreply.github.com> Co-authored-by: rjmurillo-bot <rjmurillo-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Pull Request
Summary
Add comprehensive PRD for Visual Studio 2022/2026 install support. This PRD documents requirements, research findings, blocking questions for the VS team, and a phased implementation plan.
Changes
.agents/planning/PRD-visual-studio-install-support.md- Full product requirements document for VS install supportType of Change
Testing
Agent Review
Security Review
.agents/security/)Files requiring security review:
None - documentation only.
Other Agent Reviews
Checklist
Related Issues
Related to #51 (does not close - implementation blocked pending VS team answers)
PRD Highlights
Key Finding: User-level (global) installation is BLOCKED pending answers from Visual Studio team about agent storage paths.
Blocking Questions for VS Team:
Next Steps:
🤖 Generated with Claude Code
Note
No files changed; no functional or documentation updates included.
Written by Cursor Bugbot for commit 0dfb9b7. This will update automatically on new commits. Configure here.