[plan] Add deployment_status trigger guidance to create-agentic-workflow prompt

[github-actions]

Objective

Add deployment_status event documentation and examples to the create-agentic-workflow prompt so the agent suggests it for external deployment monitoring scenarios instead of defaulting to workflow_run.

Context

From Agent Persona Exploration discussion #18250, the DO-1 (Failed Deployment Incident Creator) scenario scored 4.4/5.0. The agent applies the workflow_run + if:failure pattern correctly but misses deployment_status as a better trigger for external deployment services (e.g., Heroku, Vercel, Railway, Fly.io).

Approach

1. Locate the create-agentic-workflow prompt/skill
2. Add a section on deployment_status event:
   • Explain when to use it: external deployment services that post deployment status back to GitHub
   • Show the trigger syntax:

     on:
       deployment_status:

   • Add if: github.event.deployment_status.state == 'failure' condition example
3. Distinguish from workflow_run: use deployment_status for external deployments, workflow_run for GitHub Actions-internal pipelines
4. Consider adding a reference workflow for deployment incident creation

Files to Modify

• Update: the create-agentic-workflow prompt/skill with deployment_status guidance
• Optionally create: .github/workflows/deployment-incident.md reference workflow

Acceptance Criteria

• deployment_status trigger is documented in the create prompt
• Agent suggests deployment_status when user describes external deployment monitoring
• Clear guidance on when to choose deployment_status vs workflow_run

Generated by Plan Command for issue #discussion #18250

• expires on Feb 27, 2026, 4:46 AM UTC

[pelikhan]

Use .github/aw/deployment-status.md