Proposal: Add mandatory label requirements to supervisor tracking issue creation #3070

Open
opened 2026-04-05 04:52:37 +00:00 by freemo · 7 comments
Owner

Agent Improvement Proposal

Pattern Detected

Type: Prompt improvement — label compliance enforcement
Affected Agents: product-builder.md (supervisor launch prompts), ca-uat-tester.md, ca-bug-hunter.md, ca-system-watchdog.md, and other supervisors that create their own tracking issues
Evidence: Across all three sessions (issues #1314, #1458, #1530, #2877), the system watchdog consistently reports label compliance gaps:

Session 3 (issue #2877, watchdog cycle 1):

  • Issue #2876 (Spec Updater tracker): Missing ALL required labels
  • Issue #2875 (UAT Pool tracker): Missing ALL required labels

Session 3 (issue #2877, watchdog cycle 6):

  • Issue #2882 (Docs Writer tracker): Missing ALL required labels
  • Issue #2881 (Bug Hunter tracker): Missing ALL required labels
  • Issues #2925, #2924 (UAT direct issues): Missing ALL required labels

Persistent pattern: Issues created via ca-new-issue-creator are properly labeled . Issues created directly by supervisors (bypassing ca-new-issue-creator) consistently miss required labels.

The CONTRIBUTING.md requires every issue to have exactly one State/ label, one Type/ label, and one Priority/ label. Supervisors that create their own tracking issues via direct Forgejo API calls skip the label enforcement built into ca-new-issue-creator.

Proposed Change

Two surgical modifications:

  1. In product-builder.md: Add a "Label Requirements for Tracking Issues" section that instructs the product-builder to include labels in every supervisor launch prompt. Specifically, add to each launch_supervisor() prompt text:

    When creating tracking issues, ALWAYS include these labels:
    Type/Automation, State/In Progress, Priority/Medium
    
  2. In ca-uat-tester.md: The pool supervisor's tracking issue creation (line ~119-128) already creates a tracking issue but only includes Type/Automation. Add State/In Progress and Priority/Medium to the label list:

    labels: ["Type/Automation", "State/In Progress", "Priority/Medium"]
    
  3. Similar fix in any other supervisor that creates tracking issues directly (ca-bug-hunter, ca-system-watchdog, etc.).

Expected Impact

  • Eliminates the persistent label compliance gap reported by the watchdog every cycle
  • Reduces watchdog remediation actions (currently the watchdog or backlog groomer has to fix labels after the fact)
  • Ensures all issues in the tracker meet the CONTRIBUTING.md requirements from creation

Risk Assessment

  • Very low risk: The change only adds labels to issue creation calls. It does not modify any supervisor logic, testing behavior, or coordination protocol.
  • No downside: There is no scenario where having correct labels on tracking issues causes problems.

This is a proposal from the agent evolver. A human must approve this issue before the change will be implemented. To approve: remove the needs feedback label, add State/Verified, or comment with approval.


Automated by CleverAgents Bot
Supervisor: Agent Evolver | Agent: ca-agent-evolver

## Agent Improvement Proposal ### Pattern Detected **Type**: Prompt improvement — label compliance enforcement **Affected Agents**: `product-builder.md` (supervisor launch prompts), `ca-uat-tester.md`, `ca-bug-hunter.md`, `ca-system-watchdog.md`, and other supervisors that create their own tracking issues **Evidence**: Across all three sessions (issues #1314, #1458, #1530, #2877), the system watchdog consistently reports label compliance gaps: **Session 3 (issue #2877, watchdog cycle 1):** - Issue #2876 (Spec Updater tracker): Missing ALL required labels - Issue #2875 (UAT Pool tracker): Missing ALL required labels **Session 3 (issue #2877, watchdog cycle 6):** - Issue #2882 (Docs Writer tracker): Missing ALL required labels - Issue #2881 (Bug Hunter tracker): Missing ALL required labels - Issues #2925, #2924 (UAT direct issues): Missing ALL required labels **Persistent pattern**: Issues created via `ca-new-issue-creator` are properly labeled ✅. Issues created directly by supervisors (bypassing ca-new-issue-creator) consistently miss required labels. The CONTRIBUTING.md requires every issue to have exactly one `State/` label, one `Type/` label, and one `Priority/` label. Supervisors that create their own tracking issues via direct Forgejo API calls skip the label enforcement built into ca-new-issue-creator. ### Proposed Change Two surgical modifications: 1. **In `product-builder.md`**: Add a "Label Requirements for Tracking Issues" section that instructs the product-builder to include labels in every supervisor launch prompt. Specifically, add to each `launch_supervisor()` prompt text: ``` When creating tracking issues, ALWAYS include these labels: Type/Automation, State/In Progress, Priority/Medium ``` 2. **In `ca-uat-tester.md`**: The pool supervisor's tracking issue creation (line ~119-128) already creates a tracking issue but only includes `Type/Automation`. Add `State/In Progress` and `Priority/Medium` to the label list: ``` labels: ["Type/Automation", "State/In Progress", "Priority/Medium"] ``` 3. **Similar fix in any other supervisor** that creates tracking issues directly (ca-bug-hunter, ca-system-watchdog, etc.). ### Expected Impact - Eliminates the persistent label compliance gap reported by the watchdog every cycle - Reduces watchdog remediation actions (currently the watchdog or backlog groomer has to fix labels after the fact) - Ensures all issues in the tracker meet the CONTRIBUTING.md requirements from creation ### Risk Assessment - **Very low risk**: The change only adds labels to issue creation calls. It does not modify any supervisor logic, testing behavior, or coordination protocol. - **No downside**: There is no scenario where having correct labels on tracking issues causes problems. --- *This is a proposal from the agent evolver. A human must approve this issue before the change will be implemented. To approve: remove the `needs feedback` label, add `State/Verified`, or comment with approval.* --- **Automated by CleverAgents Bot** Supervisor: Agent Evolver | Agent: ca-agent-evolver
Author
Owner

Approved

Approved
Author
Owner

Transitioning issue #3070 from State/Unverified to State/Verified based on maintainer triage and human approval.

  • Removed labels: State/Unverified
  • Added labels: State/Verified
  • Removed label if present: needs feedback (none present)
  • Preconditions: None failed. Issue was approved by freemo with comment: "Approved".

Notes: If there were multiple State/* labels, all would be removed before adding the new one to ensure a single active state label.


Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-state-updater

Transitioning issue #3070 from State/Unverified to State/Verified based on maintainer triage and human approval. - Removed labels: State/Unverified - Added labels: State/Verified - Removed label if present: needs feedback (none present) - Preconditions: None failed. Issue was approved by freemo with comment: "Approved". Notes: If there were multiple State/* labels, all would be removed before adding the new one to ensure a single active state label. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-state-updater
Author
Owner

Proposal approved by @freemo. Transitioned from State/Unverified to State/Verified.

This proposal is now ready for implementation by the agent evolver.


Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: ca-human-liaison

Proposal approved by @freemo. Transitioned from `State/Unverified` to `State/Verified`. This proposal is now ready for implementation by the agent evolver. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: ca-human-liaison
Author
Owner

MoSCoW classification: Should Have

Rationale: This proposal addresses a persistent, recurring label compliance gap that the system watchdog reports every cycle. Fixing the root cause (supervisors not applying labels at creation time) eliminates repetitive remediation work and ensures all issues meet CONTRIBUTING.md requirements from the start. This is a process improvement that reduces waste and improves data quality across the project.

The fix is low-risk (only adds labels to API calls) and high-value (eliminates a recurring compliance gap). It should be implemented when convenient but is not blocking any milestone deliverable.

Note: This issue also needs a milestone assignment. Since it's an automation/process improvement, I'm assigning it to v3.6.0 (Advanced Concepts & Deferred Features) as it fits the "plugin architecture extensions" scope.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

MoSCoW classification: **Should Have** Rationale: This proposal addresses a persistent, recurring label compliance gap that the system watchdog reports every cycle. Fixing the root cause (supervisors not applying labels at creation time) eliminates repetitive remediation work and ensures all issues meet CONTRIBUTING.md requirements from the start. This is a process improvement that reduces waste and improves data quality across the project. The fix is low-risk (only adds labels to API calls) and high-value (eliminates a recurring compliance gap). It should be implemented when convenient but is not blocking any milestone deliverable. **Note:** This issue also needs a milestone assignment. Since it's an automation/process improvement, I'm assigning it to v3.6.0 (Advanced Concepts & Deferred Features) as it fits the "plugin architecture extensions" scope. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo added this to the v3.6.0 milestone 2026-04-05 06:22:12 +00:00
Author
Owner

Label compliance issue detected: This issue has two conflicting State/* labels: State/In Progress and State/Verified. Per CONTRIBUTING.md, each issue should have exactly one State/* label.

Please remove one of these labels:

  • If work is actively in progress → keep State/In Progress, remove State/Verified
  • If the issue is ready for implementation → keep State/Verified, remove State/In Progress

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

**Label compliance issue detected:** This issue has two conflicting `State/*` labels: `State/In Progress` and `State/Verified`. Per CONTRIBUTING.md, each issue should have exactly one `State/*` label. Please remove one of these labels: - If work is actively in progress → keep `State/In Progress`, remove `State/Verified` - If the issue is ready for implementation → keep `State/Verified`, remove `State/In Progress` --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
Author
Owner

PR #3335 Closed as Superseded

PR #3335 (which implemented the ca-uat-tester.md fix from this proposal) has been closed as superseded.

Why

After rebasing PR #3335 onto the latest master, the change was completely absorbed — the tracking issue creation block in ca-uat-tester.md was removed by a subsequent master commit (feat!: restructure PR workflow to keep implementors accountable through merge). The new architecture uses SESSION_STATE_ISSUE_NUMBER provided by product-builder.md, which already creates the session state issue with all required labels (Type/Task,State/In Progress,Priority/Medium,Type/Automation).

Remaining Work from This Proposal

The proposal also mentioned fixing:

  • product-builder.md Already fixed (creates session state issue with all required labels)
  • ca-uat-tester.md Fixed architecturally (no longer creates its own tracking issue)
  • ca-bug-hunter.md Already uses SESSION_STATE_ISSUE_NUMBER pattern (no self-created tracking issue)
  • ca-system-watchdog.md Already uses SESSION_STATE_ISSUE_NUMBER pattern (no self-created tracking issue)

Based on this analysis, the core problem described in this proposal appears to have been resolved architecturally by the SESSION_STATE_ISSUE_NUMBER refactor. All supervisors now rely on product-builder.md to create the session state issue with proper labels, rather than creating their own tracking issues.

This issue can likely be closed as resolved. A human should verify and close if appropriate.


Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-worker

## PR #3335 Closed as Superseded PR #3335 (which implemented the `ca-uat-tester.md` fix from this proposal) has been **closed as superseded**. ### Why After rebasing PR #3335 onto the latest master, the change was completely absorbed — the tracking issue creation block in `ca-uat-tester.md` was removed by a subsequent master commit (`feat!: restructure PR workflow to keep implementors accountable through merge`). The new architecture uses `SESSION_STATE_ISSUE_NUMBER` provided by `product-builder.md`, which already creates the session state issue with all required labels (`Type/Task,State/In Progress,Priority/Medium,Type/Automation`). ### Remaining Work from This Proposal The proposal also mentioned fixing: - `product-builder.md` — ✅ **Already fixed** (creates session state issue with all required labels) - `ca-uat-tester.md` — ✅ **Fixed architecturally** (no longer creates its own tracking issue) - `ca-bug-hunter.md` — ✅ **Already uses SESSION_STATE_ISSUE_NUMBER pattern** (no self-created tracking issue) - `ca-system-watchdog.md` — ✅ **Already uses SESSION_STATE_ISSUE_NUMBER pattern** (no self-created tracking issue) Based on this analysis, the core problem described in this proposal appears to have been **resolved architecturally** by the SESSION_STATE_ISSUE_NUMBER refactor. All supervisors now rely on `product-builder.md` to create the session state issue with proper labels, rather than creating their own tracking issues. This issue can likely be closed as resolved. A human should verify and close if appropriate. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
Author
Owner

Label compliance fix applied:

  • Added missing label: Priority/Backlog
  • Added missing label: Type/Task
  • Reason: Issue was missing required Priority/* and Type/* labels per CONTRIBUTING.md. Inferred Type/Task from the proposal/improvement nature of the issue. Applied Priority/Backlog as default.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Label compliance fix applied: - Added missing label: `Priority/Backlog` - Added missing label: `Type/Task` - Reason: Issue was missing required Priority/* and Type/* labels per CONTRIBUTING.md. Inferred `Type/Task` from the proposal/improvement nature of the issue. Applied `Priority/Backlog` as default. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#3070
No description provided.