feat: add campaign-style playbook and update refs

[mnkiefer]

• Adds new playbook for designing campaign-style and KPI workflows, and updates several documentation and prompt files to reference this playbook.
• Clarifies that campaign and KPI workflows are patterns within agentic workflows, not separate workflow types.
• Also provides guidance on pacing, stop conditions, and cross-repo coordination.

/cc @pelikhan

[Copilot]

Pull request overview

This PR adds a new campaign workflow playbook and updates all workflow creation/modification prompts to reference it. The playbook provides guidance on designing campaign-style workflows (time-bounded coordinated pushes with measurable outcomes) and KPI workflows (metric tracking and improvement over time). The key message is that campaigns are a design pattern within agentic workflows, not a separate workflow type.

Changes:

• Adds .github/aw/campaign.md playbook documenting patterns for campaign/KPI workflows including pacing strategies, stop conditions, goal-aware early exits, and cross-repo coordination
• Updates five prompt files to reference the campaign playbook when users mention related keywords (campaign, KPI, pacing, cadence, stop-after)

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
.github/aw/campaign.md	New playbook providing comprehensive guidance on campaign and KPI workflow patterns, including minimal viable specs, pacing levers, goal-aware early exits, and cross-repo coordination
.github/aw/upgrade-agentic-workflows.md	Adds reference to campaign playbook for upgrade prompts
.github/aw/update-agentic-workflow.md	Adds reference to campaign playbook for update prompts
.github/aw/debug-agentic-workflow.md	Adds reference to campaign playbook for debug prompts
.github/aw/create-shared-agentic-workflow.md	Adds reference to campaign playbook for shared workflow creation
.github/aw/create-agentic-workflow.md	Adds reference to campaign playbook for workflow creation prompts

Comments suppressed due to low confidence (1)

.github/aw/campaign.md:75

• The codebase consistently uses explicit permission objects rather than the read-all shorthand. While read-all is valid GitHub Actions syntax, it's inconsistent with the repository's convention of explicitly specifying each permission. Consider using an explicit permissions object like permissions: { contents: read } to match the pattern used in all other workflows in this repository.

permissions: read-all

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.