refactor(agents): address comments

Author: georgianastasov

.github/agents/bug-fixing-implementer-agent.md

@@ -39,8 +39,6 @@ Check the relevant skill file for component APIs and patterns:
 - Grid components → `skills/igniteui-angular-grids/SKILL.md`
 - Theming & styling → `skills/igniteui-angular-theming/SKILL.md`
 
-Each skill file is a routing hub pointing to detailed reference files under its `references/` folder. **Read the relevant reference files in full** before modifying any component code.
-
 ---
 
 ## GREEN Phase — Fix the Bug

.github/agents/bug-fixing-orchestrator-agent.md

@@ -134,7 +134,13 @@ src/app/<component>/                              ← demo pages
 
 Run `npm start` if the bug involves UI behavior or user interaction to visually confirm the issue.
 
-### Step 2 — Present a Scope Summary
+### Step 2 — Request Missing Context
+
+If the report is missing information needed to reproduce or scope the bug safely, pause and ask for the missing context before routing any work.
+
+Keep the follow-up short and specific.
+
+### Step 3 — Present a Scope Summary
 
 Present a brief scope summary to the user:
 
@@ -149,7 +155,7 @@ Keep it short and high-level. Confirm scope, not solution details.
 
 Wait for user confirmation.
 
-### Step 3 — Route Work
+### Step 4 — Route Work
 
 Delegate work only through isolated subagent execution when available. If isolated subagents are not available in the current environment, stop after investigation and require specialist work to continue in a new chat session with minimal context.
 
@@ -168,11 +174,11 @@ Use agents in this order:
 4. **`migration-agent`** — only if the fix introduces a breaking change
 5. **`changelog-agent`** — only if the fix warrants an entry under an existing CHANGELOG sections; otherwise leave `CHANGELOG.md` unchanged
 
-### Step 4 — Verify Completeness
+### Step 5 — Verify Completeness
 
 After all agents finish, check:
 
-- Does the failing test now pass?
+- Does the newly added failing test now pass?
 - Were all affected areas covered?
 - Were public exports preserved or updated?
 - Was the component README updated (if needed)?
@@ -199,7 +205,7 @@ Report what was done and any remaining items.
 
 ## Multi-branch Fixes
 
-When a bug exists in multiple release branches:
+When a bug exists in multiple supported release branches:
 1. Target the fix at the **oldest affected branch** first.
 2. Cherry-pick the commit to each newer branch up to and including `master`.
 3. Create separate PRs for each cherry-pick.

.github/agents/feature-orchestrator-agent.md

@@ -119,7 +119,13 @@ src/app/<component>/                              ← demo pages
    - Whether i18n strings are affected
    - Which test suite to use (grid vs non-grid)
 
-### Step 2 — Present a Scope Summary
+### Step 2 — Request Missing Context
+
+If the request is missing information needed to discover scope safely, pause and ask for the missing context before routing any work.
+
+Keep the follow-up short and specific.
+
+### Step 3 — Present a Scope Summary
 
 Present a brief scope summary to the user:
 
@@ -133,7 +139,7 @@ Keep it short and high-level. Confirm scope, not solution details.
 
 Wait for user confirmation.
 
-### Step 3 — Route Work
+### Step 4 — Route Work
 
 Delegate work only through isolated subagent execution when available. If isolated subagents are not available in the current environment, stop after scope discovery and require specialist work to continue in a new chat session with minimal context.
 
@@ -158,7 +164,7 @@ Use agents in this order:
 4. **`migration-agent`** — only if breaking changes exist
 5. **`changelog-agent`** — updates CHANGELOG.md
 
-### Step 4 — Verify Completeness
+### Step 5 — Verify Completeness
 
 After all agents finish, check:
 

AGENTS.md

@@ -54,10 +54,10 @@ css-naming-convention.md           ← CSS naming rules
 - Keep accessibility intact: ARIA, keyboard navigation, focus behavior, and screen reader semantics.
 - Keep i18n intact when user-facing text changes.
 - Add JSDoc with `@param`, `@returns`, and `@example` on every new public member.
-- Add or update ng update migrations for breaking changes.
+- Add or update `ng update` migrations for true breaking changes such as removals, renames, moved entry points, selector changes, or incompatible default-behavior changes.
 - Update the component `README.md` when the public API surface changes.
 - Consider demo/sample updates in `src/app/` for user-visible changes.
-- Update `CHANGELOG.md` for every new feature, deprecation, or breaking change.
+- Update `CHANGELOG.md` for new features, deprecations, breaking changes, and notable user-visible fixes when they fit the existing changelog section structure.
 
 ### Never
 
@@ -118,6 +118,9 @@ Feature implementation is handled by a set of specialized agents in `.github/age
 | `migration-agent` | `migration-agent.md` | Creates `ng update` migration schematics for breaking changes |
 | `changelog-agent` | `changelog-agent.md` | Updates `CHANGELOG.md` following repo conventions |
 
+Feature and bug orchestrators route work in this order:
+TDD → implementer → README (if needed) → migration (if breaking) → changelog (if needed).
+
 ## Commit Message Conventions
 
 When creating or suggesting a commit message, follow this format: