Persona Overview
- Agent: agentic-workflows
- Personas This Run: Program Manager, Designer, Legal / Compliance
- Scenarios Tested: 4
- Average Quality Score: 4.7/5.0
Key Findings
- The agent strongly favors smallest-fit triggers, especially
pull_request with paths: for scoped reviews and schedule + workflow_dispatch for digests.
github via gh-proxy is the default read path; optional tools such as playwright are only suggested when the scenario explicitly needs them.
- Security guidance was consistently good: read-only permissions, safe outputs for writes, and explicit
noop criteria.
- The strongest responses were for designer governance and license-compliance review scenarios.
- Recurring audit/report scenarios were solid but slightly less specific about cadence and lifecycle defaults.
Top Patterns
- Most common triggers:
pull_request with scoped paths: and schedule often paired with workflow_dispatch.
- Most recommended tools:
github (gh-proxy), with optional playwright only for visual/browser tasks.
- Security practices observed: read-only agent jobs, safe-output-only writes, explicit dedup keys, and
noop on empty or out-of-scope cases.
View High Quality Responses (Top 2-3)
- legal-license-scan — Excellent compliance pattern: manifest-scoped trigger, tiered license classification, PR comment for review items, issue escalation only for blocked licenses.
- designer-token-governance — Excellent PR-local governance: tight
paths: scoping, PR comments instead of issues, and optional playwright only when truly needed.
- program-manager-weekly-milestones — Strong digest framing with explicit window/dedup/noop requirements and issue-based reporting.
View Areas for Improvement (Top 2-3)
- Scheduled compliance audits could be more explicit about cadence defaults and what qualifies as “material drift.”
- Recurring report guidance should more consistently mention lifecycle helpers like
close-older-issues when recommending issue-based digests.
- Non-technical persona examples remain less numerous than engineering examples, which may limit specificity for PM/program-style requests.
Recommendations
- Add a compact recurring-report lifecycle checklist to
.github/aw/create-agentic-workflow.md that explicitly includes close-older-issues, report window, grouping, and dedup key guidance.
- Expand
.github/aw/triggers.md with one concrete compliance-audit example defining “material drift” and the preferred schedule cadence.
- Add another non-technical persona example to
.github/aw/github-agentic-workflows.md covering program management or stakeholder-digest workflows.
Generated by 🎭 Agent Persona Explorer · 15.2 AIC · ⌖ 17.4 AIC · ⊞ 6.5K · ◷
Persona Overview
Key Findings
pull_requestwithpaths:for scoped reviews andschedule+workflow_dispatchfor digests.githubviagh-proxyis the default read path; optional tools such asplaywrightare only suggested when the scenario explicitly needs them.noopcriteria.Top Patterns
pull_requestwith scopedpaths:andscheduleoften paired withworkflow_dispatch.github(gh-proxy), with optionalplaywrightonly for visual/browser tasks.noopon empty or out-of-scope cases.View High Quality Responses (Top 2-3)
paths:scoping, PR comments instead of issues, and optionalplaywrightonly when truly needed.View Areas for Improvement (Top 2-3)
close-older-issueswhen recommending issue-based digests.Recommendations
.github/aw/create-agentic-workflow.mdthat explicitly includesclose-older-issues, report window, grouping, and dedup key guidance..github/aw/triggers.mdwith one concrete compliance-audit example defining “material drift” and the preferred schedule cadence..github/aw/github-agentic-workflows.mdcovering program management or stakeholder-digest workflows.