You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tl;dr Add a new scheduled report workflow (e.g., agent-suggestions) modeled on existing scheduled-report agents to file a weekly issue with 1–3 concrete new agent ideas after checking for duplicates.
Recommendation
Create a new scheduled-report workflow (gh-aw-agent-suggestions.md) that runs weekly and uses create-issue safe output with close-older-issues and a clear title prefix, mirroring other scheduled report agents.
In the prompt, require a duplicate check against existing workflows and open issues/PRs, and default to noop when there isn’t a strong, actionable suggestion.
Add the new workflow to the workflow tables in README.md and gh-agent-workflows/README.md, plus a new gh-agent-workflows/agent-suggestions/README.md + example.yml trigger.
Findings
Scheduled report behavior is standardized in .github/workflows/gh-aw-fragments/scheduled-report.md:1-67 (process + quality gate).
Existing scheduled report workflows (.github/workflows/gh-aw-project-summary.md:1-66, .github/workflows/gh-aw-stale-issues.md:1-65) show the expected frontmatter structure and create-issue safe output settings.
Weekly trigger pattern exists in gh-agent-workflows/release-update/example.yml:1-16 (cron weekly + workflow_dispatch).
The current workflow catalog (gh-agent-workflows/README.md:7-26, README.md:24-39) does not list an “agent suggestion” workflow.
New workflow addition steps are documented in gh-agent-workflows/DEVELOPING.md:134-140.
Any workflow that sets expires for create-issue requires the agentics-maintenance workflow, documented in gh-agent-workflows/README.md:54-62.
Verification
Not run (triage only; no tests executed).
Detailed Action Plan
Add .github/workflows/gh-aw-agent-suggestions.md using the scheduled report imports and structure from .github/workflows/gh-aw-project-summary.md:1-66, and include gh-aw-fragments/scheduled-report.md:1-67 plus safe-output-create-issue with a title prefix like [agent-suggestions].
Define the Report Assignment to:
Read gh-agent-workflows/README.md:7-26 and README.md:24-39 for existing workflows.
Search open issues/PRs for agent requests (e.g., github-search_issues / github-search_pull_requests) and check for duplicates.
Propose 1–3 new agents with concrete trigger + safe-output needs; otherwise noop.
Add gh-agent-workflows/agent-suggestions/README.md and example.yml (weekly cron + workflow_dispatch), following gh-agent-workflows/release-update/example.yml:1-16.
Update workflow tables in README.md:24-39 and gh-agent-workflows/README.md:7-26 to list the new workflow.
Run make compile and commit the new .lock.yml + trigger (per gh-agent-workflows/DEVELOPING.md:134-140).
If expires is used for the report issue, ensure the repo has agentics-maintenance installed (per gh-agent-workflows/README.md:54-62).
added the agent-suggestions scheduled report prompt (includes downstream repo evaluation, dev needs review, and noop path)
added docs + weekly trigger example
updated workflow catalogs
Testing: make lint.
Note: the shim lives in github/workflows/gh-aw-agent-suggestions.md due to workflow guardrails; it should be moved to .github/workflows/ and compiled to generate the lock file.
Activity
github-actions commentedon Feb 19, 2026
tl;dr Add a new scheduled report workflow (e.g.,
agent-suggestions) modeled on existing scheduled-report agents to file a weekly issue with 1–3 concrete new agent ideas after checking for duplicates.Recommendation
gh-aw-agent-suggestions.md) that runs weekly and usescreate-issuesafe output withclose-older-issuesand a clear title prefix, mirroring other scheduled report agents.noopwhen there isn’t a strong, actionable suggestion.README.mdandgh-agent-workflows/README.md, plus a newgh-agent-workflows/agent-suggestions/README.md+example.ymltrigger.Findings
.github/workflows/gh-aw-fragments/scheduled-report.md:1-67(process + quality gate)..github/workflows/gh-aw-project-summary.md:1-66,.github/workflows/gh-aw-stale-issues.md:1-65) show the expected frontmatter structure andcreate-issuesafe output settings.gh-agent-workflows/release-update/example.yml:1-16(cron weekly +workflow_dispatch).gh-agent-workflows/README.md:7-26,README.md:24-39) does not list an “agent suggestion” workflow.gh-agent-workflows/DEVELOPING.md:134-140.expiresforcreate-issuerequires theagentics-maintenanceworkflow, documented ingh-agent-workflows/README.md:54-62.Verification
Not run (triage only; no tests executed).
Detailed Action Plan
.github/workflows/gh-aw-agent-suggestions.mdusing the scheduled report imports and structure from.github/workflows/gh-aw-project-summary.md:1-66, and includegh-aw-fragments/scheduled-report.md:1-67plussafe-output-create-issuewith a title prefix like[agent-suggestions].gh-agent-workflows/README.md:7-26andREADME.md:24-39for existing workflows.github-search_issues/github-search_pull_requests) and check for duplicates.noop.gh-agent-workflows/agent-suggestions/README.mdandexample.yml(weekly cron +workflow_dispatch), followinggh-agent-workflows/release-update/example.yml:1-16.README.md:24-39andgh-agent-workflows/README.md:7-26to list the new workflow.make compileand commit the new.lock.yml+ trigger (pergh-agent-workflows/DEVELOPING.md:134-140).expiresis used for the report issue, ensure the repo hasagentics-maintenanceinstalled (pergh-agent-workflows/README.md:54-62).Related Items
.github/workflows/gh-aw-fragments/scheduled-report.md:1-67.github/workflows/gh-aw-project-summary.md:1-66create-issue.gh-agent-workflows/release-update/example.yml:1-16What is this? | From workflow: Issue Triage Agent
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #129
strawgate commentedon Feb 19, 2026
/ai make a PR. Ensure it evaluates software development needs, work going on in downstream repos and noop is an option
github-actions commentedon Feb 19, 2026
PR opened: "Add agent suggestions workflow".
Summary:
Testing:
make lint.Note: the shim lives in
github/workflows/gh-aw-agent-suggestions.mddue to workflow guardrails; it should be moved to.github/workflows/and compiled to generate the lock file.What is this? | From workflow: Issue Assistant
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #129