[Feedback] Add more GitLab-centric Automations + Refine Automation Template UX

[jpelletier1]

GitLab-Centric Automation Templates

Overview

Expand automation templates beyond GitHub with a GitLab-focused set for common software-delivery workflows.

Problem

Current templates are GitHub-centric. GitLab users need equivalent automations for code review, work items, and requirements refinement.

Goals

• Provide GitLab-native automation templates.
• Support workflows from issue/work item through merge request.
• Improve work-item quality before engineering begins.

Initial Templates

1. Code Review Automation

Modeled after the GitHub code review automation, this would be modified to support GitLab-centric concepts like Merge Requests.

2. Work Item to Merge Request Automation

Modeled after the GitHub Issue to PR automation, this would be modified to support GitLab-centric concepts like Work Items and Merge Requests.

• PR: feat: add gitlab issue-to-mr automation #525

3. PRD Refiner

This would be a new Automation designed for Product Manager personas. It would analyze a GitLab work item and post a comment containing:

• Open questions
• Recommendations
• Gaps or ambiguities in the user story

Optionally, the automation can analyze the linked repository/codebase when repository hints appear in the work-item description or comments. This should add implementation-aware context to the refinement feedback.

• Verify the automations should up under Automations > Templates
• Verify the Automations > Templates allow for filtering by integration (e.g., GitHub, GitLab, Jira, etc.)

[github-actions]

⚠️ Not yet ready-for-dev

This issue does not yet meet the readiness criteria, so the
ready-for-dev label has not been applied (or has been removed).
The criteria are type-specific:

Bug reports (bug label):

• The ### Actual Behavior section must describe reproducible steps
  and include a command such as uv run pytest, pytest, python,
  pip, npm run, or node.
• An ### Acceptance Criteria section with at least one checklist item (- [ ] ...).

Enhancements (enhancement label):

• A ### Desired Behavior section.
• An ### Acceptance Criteria section with at least one checklist item.

What is missing:

• The issue has neither the bug nor enhancement label, so its readiness criteria cannot be evaluated. Add the appropriate label.

Edit the issue to address the gaps and the ready-for-dev label will be
applied automatically.

This is an automated readiness check posted by a workflow.