[WIP] Start implementation of monorepo game plan

[Copilot]

• Explore repository structure and understand existing patterns
• Create dotnet/101-create-item/ - CRUD operations sample (.NET)
• Create dotnet/102-query-items/ - Query items sample (.NET)
• Create python/101-create-item/ - CRUD operations sample (Python)
• Create python/102-query-items/ - Query items sample (Python)
• Create go/002-connect-connection-string/ - Connection string auth sample (Go)
• Create go/201-change-feed/ - Change feed sample (Go)
• Create .github/copilot-instructions.md - General Copilot instructions
• Create .github/instructions/validation-workflows.instructions.md - Validation workflow instructions
• Fix readme.md trailing content issue
• Run code review and security checks

Original prompt

Start implementation

[Chronological Review: The conversation began with the user requesting a review of a user story and a Teams chat to develop a game plan for a monorepo. The user then defined a numbering standard for samples, requested a breakdown of work into manageable pieces, and delegated tasks to cloud agents. The user continued to refine the project plan, focusing on validation workflows and sample implementations. The conversation evolved to include updates on agent tasks, comments on Azure DevOps work items, and adjustments to agent specifications. The user also requested the creation of custom instructions files for Copilot, emphasizing best practices and validation workflows.]

[Intent Mapping:

1. Review user story and Teams chat for planning: "Help me come up with a game plan to make a v1/draft iteration of this monorepo."
2. Define a numbering standard for samples: "Let's define a numbering standard we can use for the samples repository."
3. Delegate tasks to cloud agents: "Delegate to a separate agent the task of creating the validation workflow."
4. Update project plan and README: "Let's start implementation by adding the project plan to the README file."
5. Review and update comments on Azure DevOps: "Can you update the existing comment."
6. Create custom instructions files for Copilot: "Can we also create a specific custom instructions file for the validation workflows with our best practices codified."]

[Technical Inventory:

• Technologies: Azure Cosmos DB, .NET, Python, Go, TypeScript
• Tools: Azure DevOps, GitHub, cloud agents for task delegation
• Concepts: Numbering standard for samples, validation workflows, project planning, custom instructions for Copilot]

[Code Archaeology:

• Files discussed: README file for project plan, validation workflow files, agent specifications
• Functions and patterns: Delegation of tasks to cloud agents, creation of validation workflows, implementation of code samples]

[Progress Assessment:

• Completed Tasks: Defined numbering standard, delegated tasks to agents, updated project plan in README
• Partially Complete Work: Ongoing development of validation workflows, implementation of code samples in various languages
• Validated Outcomes: Initial project plan established, tasks assigned to agents]

[Context Validation: All critical information for continuation is captured, including user goals for sample implementation, validation workflows, and project planning.]

[Recent Commands Analysis:

• Last Agent Commands: User requested to "Go back through the ENTIRE history of this conversation and look at the current state of the code samples."
• Tool Results Summary: The user utilized the 'semantic_search' tool to review the conversation history and current state of code samples.
• Pre-Summary State: The agent was actively working on reviewing the entire conversation history and the state of code samples when the token budget was exceeded.
• Operation Context: These commands were executed to gather context for creating a custom instructions file for Copilot, aligning with the user's goal of establishing best practices and validation workflows.]

1. Conversation Overview: - Primary Objectives: The user aimed to develop a monorepo for Azure Cosmos DB samples, establish a numbering standard, delegate tasks to cloud agents, and create custom instructions for Copilot. - Session Context: The conversation progressed from planning and defining standards to delegating tasks and refining project details, including validation workflows and sample implementations. - User Intent Evolution: The user's focus shifted from high-level planning to detailed implementation and validation strategies, culminating in requests for specific instructions files.

2. Technical Foundation:

• Azure Cosmos DB: Central technology for sample implementations.
• .NET, Python, Go, TypeScript: Languages for code samples.
• Validation Workflows: Emphasized for continuous testing and pull request validation.

3. Codebase Status:

• README file:
  • Purpose: Document project plan and standards.
  • Current State: Updated with project plan details.
  • Key Code Segments: Project plan outline.
• Validation Workflow Files: To be created based on best practices.

4. Problem Resolution:

• Issues Encountered: Need for clear validation workflows and project structure.
• Solutions Implemented: Delegation of tasks to agents, establishment of a numbering standard.
• Debugging Context: Ongoing refinement of project details and agent specifications.

5. Progress Tracking:

• Completed Tasks: Defined numbering standard, delegated tasks, updated README.
• Partially Complete Work: Development of validation workflows and code samples.
• Validated Outcomes: Initial project plan established.

6. Active Work State:

• Current Focus: Reviewing conversation history and state of code samples for creating custom instructions.
• Recent Context: User requested a comprehensive review...

Created from VS Code.

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.