Add Grid-specific Jira templates and product-aware routing

prompts/skills/jira/SKILL.md

@@ -109,9 +109,12 @@ Each ticket has exactly **one** track value. Never set multiple track values on
 
 ### Templates
 
-- **Feature/Task**: `templates/feature-task.md` (12-section numbered format)
+- **Feature/Task (Grid)**: `templates/feature-task-grid.md` (12-section numbered format)
+- **Feature/Task (Charts/Studio)**: `templates/feature-task-charts.md` (12-section numbered format)
 - **Bug**: `templates/bug.md` (TC-based format)
 
+Select the feature/task template based on the detected product (see Product Detection above).
+
 Follow the exact structure from the template. Do not use free-form markdown headers (`##`), tables, or code blocks for top-level structure.
 
 ### Reading JIRA Comments

prompts/skills/jira/products/grid.md

@@ -20,6 +20,41 @@
 
 Grid is the reference version. Charts major version = Grid major version - 22.
 
+## Task Structure Conventions
+
+When a larger requirement needs subtasks, follow this pattern:
+
+1. Add a single top-level task for the feature request and create subtasks:
+    - **Non-functional requirements subtasks:**
+        - Conceptual UX and UI design.
+        - Production of design assets.
+        - Localization.
+        - Accessibility.
+        - Theming.
+    - **Functional requirements subtasks:** Different functional areas or materially different configurations where the new feature will work.
+
+2. Each subtask must be self-contained. The top-level task contains an overview and shows the overall structure of subtasks.
+
+3. Only include subtasks which are in scope for the initial release. Subtasks not part of the initial release are moved to a separate containing task for later implementation.
+
+4. Re-link ZenDesk tickets to the relevant subtasks so they can easily be accessed within the context of each subtask.
+
+### Task Assignment
+
+- The top-level task is assigned to the Product Manager who owns it.
+- UX Design and Design Production subtasks are assigned to the UX Designer.
+- Development implementation subtasks are assigned to the developer involved.
+
+### Title Format
+
+- Precede the title with `[Feature Name]` to indicate its feature area.
+- New end-user features: `"Allow <user action> when <relevant grid configuration>"`.
+- New API features: `"Add support for <desired behavior> when using <existing grid feature>"`.
+
+### Reference Example
+
+See [AG-7954](https://ag-grid.atlassian.net/browse/AG-7954) for an example task following this format.
+
 ## Estimation Calibration Data
 
 TBD — to be populated by the Grid team.

prompts/skills/jira/templates/bug.md

@@ -1,4 +1,4 @@
-[Charts] Brief bug title
+[Product] Brief bug title
 
 **TC1 - First test case label**
 

prompts/skills/jira/templates/feature-task-grid.md

@@ -0,0 +1,89 @@
+[Grid] Feature title
+
+1. **Requirements Statement**
+
+    1. What is the desired behavior or capability?
+    2. Avoid implementation detail—focus on what, not how.
+
+2. **Current Behavior & Problem Statement**
+
+    1. How does this feature currently work?
+    2. What is missing or problematic?
+
+3. **Use Cases**
+
+    1. What are users trying to achieve in each scenario?
+    2. Provide specific examples extracted from support tickets.
+
+4. **API Design**
+
+    1. **Location:** (e.g., gridOptions, column definitions, API method).
+    2. **New Members:** Name, type, description.
+    3. **Default Values:** Default values, valid values (e.g., boolean, or between 0 and 1).
+    4. **Updating existing callback params objects.**
+
+5. **API Deprecations/Hiding**
+
+    1. Deprecated members, replacement members — document in the DEPRECATIONS field.
+
+6. **Breaking Changes in API or Behavior**
+
+    1. API/appearance/behavior changes — document in the BREAKING CHANGES field.
+
+7. **UX Design**
+
+    1. **Wireframes / Visuals:** Link to Figma or attachments. All design resources are stored in Figma and marked with the relevant task key. Once the conceptual design is validated in the relevant subtask, the design itself is attached to the top-level task and relevant subtasks.
+    2. **Interaction Notes:** Keyboard handling, tooltips, animations.
+
+8. **Dependencies**
+
+    1. Other tasks or refactors this depends on.
+    2. Other work that can/should be tackled together with this.
+
+9. **Functional Acceptance Criteria**
+
+    1. **Basic Scenarios:**
+
+        1. New behavior in basic and edge scenarios.
+        2. Expected output/state changes.
+
+    2. **Feature Interactions:**
+
+        1. How this interacts with other features (e.g., sorting, filtering).
+        2. Different configurations.
+        3. State of features.
+
+10. **Non-functional Acceptance Criteria**
+
+    1. **State:** Define default or initial state clearly.
+    2. **Documentation:**
+
+        1. API docs updated.
+        2. New section added to docs.
+
+    3. **Accessibility:**
+
+        1. WCAG-compliant: ARIA, focus, keyboard nav.
+        2. Screen reader announcements.
+
+    4. **Localization:**
+
+        1. All user-facing strings are translatable and translated in supported languages.
+
+    5. **RTL Support:**
+
+        1. Layouts and interactions should adapt to RTL.
+
+    6. **Theming:**
+
+        1. Supports legacy and new themes.
+
+11. **Out of Scope**
+
+    1. What is not being implemented in this task?
+    2. Future enhancements to consider.
+
+12. **Design Documents**
+
+    1. Link to design documents.
+    2. Link to Figma designs.

prompts/skills/jira/workflows/create.md

@@ -25,7 +25,8 @@ Use this when the user specifically asks for an improvement task or when behavio
 Based on ticket type, read the relevant template (in the `templates/` subdirectory of this skill):
 
 - **Bug tickets and Improvement tasks**: Read `templates/bug.md`.
-- **Feature/Tech-debt/Docs**: Read `templates/feature-task.md`.
+- **Feature/Tech-debt/Docs (Grid)**: Read `templates/feature-task-grid.md`.
+- **Feature/Tech-debt/Docs (Charts/Studio)**: Read `templates/feature-task-charts.md`.
 
 ## Step 2: Gather Information
 

prompts/skills/jira/workflows/plan.md

@@ -20,7 +20,8 @@ Use this workflow when the user is **planning** JIRA ticket creation — i.e., d
 Read the appropriate template file (from the `templates/` subdirectory):
 
 - **Bug / Improvement task**: `templates/bug.md`
-- **Feature / Tech-debt / Docs**: `templates/feature-task.md`
+- **Feature / Tech-debt / Docs (Grid)**: `templates/feature-task-grid.md`
+- **Feature / Tech-debt / Docs (Charts/Studio)**: `templates/feature-task-charts.md`
 
 ## Step 2: Output the Plan