This report summarizes a systematic exploration of the agentic-workflows custom agent across 7 representative software worker personas and automation scenarios, conducted on 2026-04-02.

Persona Overview

• Agent tested: developer.instructions (agentic-workflows / create mode)
• Scenarios tested: 7 (across 5 personas)
• Average quality score: 4.8 / 5.0
• Workflow run: §23882503037

Key Findings

• 🏆 Prompt clarity and completeness scored perfectly (5.0/5.0) — every response included structured phase-based prompts, security tables, full frontmatter, and actionable examples
• 🔐 Security posture is consistently strong — strict: true, network: defaults, minimal permissions, and safe-outputs write isolation were applied in all 7 scenarios
• ⚠️ Tool selection is the weakest dimension (4.43/5.0) — some responses used broad bash tools; explicit tool enumeration (as in be-1) is the superior pattern
• 🔄 Guard clause / early-exit pattern was used well in issue triggers (qa-2, be-1) but could be more prominently documented
• 🚨 One possible hallucination detected: the roles: field in the release notes response — not a documented gh-aw frontmatter field

Top Patterns Observed

1. Trigger selection was highly accurate: workflow_run for deployment events, issues for bug triage, pull_request with paths: for component-scoped PRs, schedule for digests
2. Safe-outputs used correctly as the write layer: all write operations (comments, labels, issues, discussions) routed via safe-outputs — never via direct issues: write permission on the agent job
3. Anti-hallucination instructions emerged in the weekly digest response: "Never fabricate PR content — only use data returned by the API" — a notable prompt quality indicator
4. concurrency: cancel-in-progress: true appeared in be-1 as a standout pattern for PR-triggered workflows to prevent comment duplication on force-pushes
5. Prerequisite documentation appeared in fe-1 and qa-1 — proactively telling users what repo configuration is required before the workflow can succeed

Recommendations

1. Document the guard clause / early-exit pattern in .github/aw/create-agentic-workflow.md — every issue/label-triggered workflow should show the noop early-exit as a first-class pattern with an example
2. Add a "bash tool enumeration" best practice in .github/aw/github-agentic-workflows.md — show explicit ["grep", "awk"] enumeration as preferred over bash: true, with security rationale
3. Add a scheduled workflow guide in .github/aw/ (e.g., scheduled-digest.md) covering the digest/release-notes pattern: cron trigger + workflow_dispatch, discussions: write permission, anti-hallucination instructions, and max: 1 discussion cap

References:

• §23882503037

AI generated by Agent Persona Explorer · history