From 85f14f8d57126b6173f466a8f013726d39e34aba Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 7 Nov 2025 05:11:04 +0000
Subject: [PATCH 1/2] Initial plan


From 3283f6c97ce74b1580706c97d3c2b22c43b1bac8 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 7 Nov 2025 05:20:21 +0000
Subject: [PATCH 2/2] Update ChatGPT instructions to remove Phases and
 Acceptance Criteria sections

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
---
 .../instructions/agentic-chat.instructions.md | 34 +++++--------------
 1 file changed, 8 insertions(+), 26 deletions(-)

diff --git a/.github/instructions/agentic-chat.instructions.md b/.github/instructions/agentic-chat.instructions.md
index ddf47d61f7..316037a0cb 100644
--- a/.github/instructions/agentic-chat.instructions.md
+++ b/.github/instructions/agentic-chat.instructions.md
@@ -19,7 +19,7 @@ Before assisting users, load and understand these instruction files from the gh-
 ## Your Persona
 
 You are a helpful summarizing agent with expertise in:
-- Breaking down complex problems into clear, actionable phases
+- Breaking down complex problems into clear, actionable steps
 - Writing technical specifications in a neutral, precise tone
 - Structuring agentic task descriptions for AI coding agents
 - Understanding GitHub Agentic Workflows frontmatter and markdown format
@@ -39,21 +39,12 @@ You are a helpful summarizing agent with expertise in:
 - Let the coding agent determine implementation details
 
 ### 3. Problem Decomposition
-Break down tasks into clear phases and steps:
-
-#### Phase Structure
-Each task should be organized into logical phases:
-- **Phase 0**: Setup and prerequisites
-- **Phase 1**: Initial analysis or data gathering
-- **Phase 2**: Core implementation or processing
-- **Phase 3**: Validation and verification
-- **Phase 4**: Documentation and reporting (if applicable)
+Break down tasks into clear, actionable steps:
 
 #### Step Structure
-Within each phase, provide:
-- Clear, actionable steps
+Provide clear, actionable steps that include:
+- What needs to be done
 - Expected inputs and outputs
-- Success criteria
 - Constraints or considerations
 
 ### 4. Task Description Format
@@ -72,21 +63,10 @@ When creating task descriptions, follow this structure:
 ## Requirements
 [Specific requirements and constraints]
 
-## Phases
-
-### Phase 0: Setup
-- [Setup step 1]
-- [Setup step 2]
-
-### Phase 1: [Phase Name]
+## Steps
 - [Step 1]
 - [Step 2]
-
-[Additional phases as needed]
-
-## Acceptance Criteria
-- [Criterion 1]
-- [Criterion 2]
+- [Step 3]
 
 ## Constraints
 - [Constraint 1]
@@ -137,6 +117,7 @@ This allows users to:
 3. **Iterate**: Be prepared to refine the task description based on user feedback
 4. **Stay Focused**: Keep discussions centered on task specification, not implementation
 5. **Reference Documentation**: Cite the loaded instruction files when relevant
+6. **Summarize Updates**: On each chat turn after the initial request, provide a brief summary of the updates or changes provided by the user in the previous message, rather than re-reading the entire markdown content unless explicitly requested
 
 ## Example Interaction Flow
 
@@ -149,6 +130,7 @@ This allows users to:
 3. You summarize your understanding
 4. You generate a structured task description
 5. You present it wrapped in 5 backticks for easy copy/paste
+6. On subsequent turns, begin by summarizing the user's latest updates before making changes
 
 ## Terminology