Context
Identified in discussion #17680 — a quality analysis of workflow message configuration. The Archie workflow messages use a first-person persona announcement and casual phrasing that appears in issue comments viewed by engineering teams.
File to Modify
.github/workflows/archie.md
Current State
run-started: "📐 Archie here! [{workflow_name}]({run_url}) is sketching the architecture on this {event_type}..."
run-success: "🎨 Blueprint complete! [{workflow_name}]({run_url}) has visualized the connections. The architecture speaks for itself! ✅"
run-failure: "📐 Drafting interrupted! [{workflow_name}]({run_url}) {status}. The diagram remains incomplete..."
Issues
"Archie here!" — first-person persona greeting is inappropriate for issue tracker context
"The architecture speaks for itself!" — casual boastful phrasing
{status} in failure message provides no actionable guidance
Proposed Changes
Remove the first-person announcement, maintain the architectural theme but with professional tone, and add actionable context to the failure message. Example direction:
run-started: "📐 [{workflow_name}]({run_url}) is analyzing the architecture for this {event_type}..."
run-success: "🎨 [{workflow_name}]({run_url}) has completed the architecture visualization. ✅"
run-failure: "📐 [{workflow_name}]({run_url}) encountered an issue and could not complete the architecture diagram. Check the [run logs]({run_url}) for details."
Acceptance Criteria
Generated by Plan Command for issue #discussion #17680
Context
Identified in discussion #17680 — a quality analysis of workflow message configuration. The Archie workflow messages use a first-person persona announcement and casual phrasing that appears in issue comments viewed by engineering teams.
File to Modify
.github/workflows/archie.mdCurrent State
Issues
"Archie here!"— first-person persona greeting is inappropriate for issue tracker context"The architecture speaks for itself!"— casual boastful phrasing{status}in failure message provides no actionable guidanceProposed Changes
Remove the first-person announcement, maintain the architectural theme but with professional tone, and add actionable context to the failure message. Example direction:
Acceptance Criteria
run-startedrun-success{status}