豆豆友情提示:这是一个非官方 GitHub 代理镜像,主要用于网络测试或访问加速。请勿在此进行登录、注册或处理任何敏感信息。进行这些操作请务必访问官方网站 github.com。 Raw 内容也通过此代理提供。
Skip to content

[plan] Add trigger cadence clarifying question to create-agentic-workflow.md #27501

@github-actions

Description

@github-actions

Objective

Add a clarifying question about response-time requirements to the interactive mode guidance in .github/aw/create-agentic-workflow.md, so agents ask about cadence before defaulting to daily for scheduled workflows.

Context

From discussion #27482 (Agent Persona Exploration - 2026-04-21), the DevOps scenario scored 4/5 on trigger selection (not 5) because the agent defaulted to daily monitoring when 6-hour cadence could be better for true incident-response use cases. No clarifying question exists to help distinguish these scenarios.

Approach

In .github/aw/create-agentic-workflow.md, within the interactive clarifying questions section (around line 227 near trigger selection guidance), add:

- 📅 **For scheduled workflows**: Ask **"How quickly do you need to be notified after an event?"** before defaulting to `daily`.
  - Answers like "within the hour", "as fast as possible", or "incident response" → suggest `every 6 hours` or `every 4 hours`
  - Answers like "next morning", "daily summary", or "digest" → `daily on weekdays` (default)
  - Answers like "weekly report" or "end of week" → `weekly`
  - Tip: If the user describes an **incident-response** or **monitoring** scenario, always ask about cadence before scheduling

Files to Modify

  • .github/aw/create-agentic-workflow.md — add cadence clarifying question near the scheduled workflow trigger guidance (around line 247)

Acceptance Criteria

  • A cadence clarifying question is documented in the interactive guidance
  • The guidance maps user answers to appropriate schedule intervals (hourly, daily, weekly)
  • Incident-response and monitoring scenarios are explicitly called out as needing the cadence question
  • The existing daily on weekdays fuzzy schedule guidance is preserved and referenced

Generated by Plan Command for issue #discussion #27482 · ● 292.8K ·

  • expires on Apr 23, 2026, 5:16 AM UTC

Metadata

Metadata

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions