Create an agent that suggests new agents

[strawgate]

Run weekly, suggest a useful agent that isn't crazy

[github-actions]

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

1. 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].
2. 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.
3. 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.
4. Update workflow tables in README.md:24-39 and gh-agent-workflows/README.md:7-26 to list the new workflow.
5. Run make compile and commit the new .lock.yml + trigger (per gh-agent-workflows/DEVELOPING.md:134-140).
6. If expires is used for the report issue, ensure the repo has agentics-maintenance installed (per gh-agent-workflows/README.md:54-62).

Related Items

Type	Link	Relevance
Issue	#127	Documentation split request; new workflow should land in the right category.
PR	#81	Example of adding a new agent workflow.
PR	#44	Example of adding scheduled report workflows.
File	.github/workflows/gh-aw-fragments/scheduled-report.md:1-67	Shared scheduled-report prompt framework.
File	.github/workflows/gh-aw-project-summary.md:1-66	Scheduled-report workflow pattern with create-issue.
File	gh-agent-workflows/release-update/example.yml:1-16	Weekly schedule trigger example.

---

What is this? | From workflow: Issue Triage Agent

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #129

[strawgate]

/ai make a PR. Ensure it evaluates software development needs, work going on in downstream repos and noop is an option

[github-actions]

PR opened: "Add agent suggestions workflow".

Summary:

• 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.

---

What is this? | From workflow: Issue Assistant

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #129