Simplify campaign specs with intelligent defaults and move goals to markdown

.github/aw/orchestrate-agentic-campaign.md

@@ -128,8 +128,6 @@ and synchronizing campaign state into a GitHub Project board.
      body: |
        ## Campaign Overview
 
-       {{ if .Objective }}**Objective**: {{.Objective}}{{ end }}
-
        This Epic issue tracks the overall progress of the campaign. All work items are sub-issues of this Epic.
 
        **Campaign Details:**
@@ -242,7 +240,7 @@ Every campaign run MUST create a status update using `create-project-status-upda
 
 - **Most Important Findings**: Highlight the 2-3 most critical discoveries, insights, or blockers from this run
 - **What Was Learned**: Document key learnings, patterns observed, or insights gained during this run
-- **KPI Trends**: Report progress on EACH campaign KPI{{ if .KPIs }} ({{ range $i, $kpi := .KPIs }}{{if $i}}, {{end}}{{ $kpi.Name }}{{end}}){{ end }} with baseline → current → target format, including direction and velocity
+- **Campaign Progress**: Report on campaign metrics and trends with baseline → current → target format, including direction and velocity
 - **Campaign Summary**: Tasks completed, in progress, blocked, and overall completion percentage
 - **Next Steps**: Clear action items and priorities for the next run
 
@@ -251,13 +249,6 @@ Every campaign run MUST create a status update using `create-project-status-upda
 - Use today's date for start_date and target_date (or appropriate future date for target)
 - Body must be comprehensive yet concise (target: 200-400 words)
 
-{{ if .KPIs }}
-**Campaign KPIs to Report:**
-{{ range .KPIs }}
-- **{{ .Name }}**{{ if .Priority }} ({{ .Priority }}){{ end }}: baseline {{ .Baseline }}{{ if .Unit }} {{ .Unit }}{{ end }} → target {{ .Target }}{{ if .Unit }} {{ .Unit }}{{ end }} over {{ .TimeWindowDays }} days{{ if .Direction }} ({{ .Direction }}){{ end }}
-{{ end }}
-{{ end }}
-
 Example status update:
 ```yaml
 create-project-status-update:
@@ -284,19 +275,19 @@ create-project-status-update:
     - Documentation updates tied to code changes have higher accuracy and completeness
     - Users report fewer issues when examples include error handling patterns
 
-    ## KPI Trends
+    ## Campaign Progress
 
-    **Documentation Coverage** (Primary KPI):
+    **Documentation Coverage** (Primary Metric):
     - Baseline: 85% → Current: 88% → Target: 95%
     - Direction: ↑ Increasing (+3% this week, +1% velocity/week)
     - Status: ON TRACK - At current velocity, will reach 95% in 7 weeks
 
-    **Accessibility Score** (Supporting KPI):
+    **Accessibility Score** (Supporting Metric):
     - Baseline: 90% → Current: 91% → Target: 98%
     - Direction: ↑ Increasing (+1% this month)
     - Status: AT RISK - Slower progress than expected, may need dedicated focus
 
-    **User-Reported Issues** (Supporting KPI):
+    **User-Reported Issues** (Supporting Metric):
     - Baseline: 15/month → Current: 12/month → Target: 5/month
     - Direction: ↓ Decreasing (-3 this month, -20% velocity)
     - Status: ON TRACK - Trending toward target

.github/workflows/security-alert-burndown.campaign.md

@@ -3,36 +3,11 @@ id: security-alert-burndown
 name: Security Alert Burndown
 description: Systematically burns down code security alerts with focus on file write issues
 project-url: https://github.com/orgs/githubnext/projects/134
-version: v1
-state: planned
 workflows:
   - code-scanning-fixer
   - security-fix-pr
   - dependabot-bundler
   - secret-scanning-triage
-allowed-repos:
-  - githubnext/gh-aw
-discovery-repos:
-  - githubnext/gh-aw
-tracker-label: z_campaign_security-alert-burndown
-memory-paths:
-  - memory/campaigns/security-alert-burndown/**
-metrics-glob: memory/campaigns/security-alert-burndown/metrics/*.json
-cursor-glob: memory/campaigns/security-alert-burndown/cursor.json
-objective: Systematically reduce security alerts (code scanning, Dependabot, secret scanning) to zero critical issues and fewer than 5 high-severity issues
-kpis:
-  - name: Critical Security Alerts
-    baseline: 5
-    target: 0
-    unit: alerts
-    time-window-days: 90
-    priority: primary
-  - name: High-Severity Alerts
-    baseline: 15
-    target: 5
-    unit: alerts
-    time-window-days: 90
-    priority: supporting
 governance:
   max-new-items-per-run: 3
   max-discovery-items-per-run: 100
@@ -46,24 +21,30 @@ governance:
 owners:
   - "@mnkiefer"
 risk-level: high
-allowed-safe-outputs:
-  - create-pull-request
-  - create-issue
-  - autofix-code-scanning-alert
-  - add-comment
-  - update-project
-tags:
-  - security
-  - automated-fixes
-  - code-scanning
-  - dependabot
-  - secret-scanning
 ---
 
 # Security Alert Burndown Campaign
 
 This campaign systematically burns down code security alerts with the following strategy:
 
+## Objective
+
+Systematically reduce security alerts (code scanning, Dependabot, secret scanning) to zero critical issues and fewer than 5 high-severity issues.
+
+## Key Performance Indicators (KPIs)
+
+### Primary KPI: Critical Security Alerts
+- **Baseline**: 5 alerts
+- **Target**: 0 alerts
+- **Time Window**: 90 days
+- **Unit**: alerts
+
+### Supporting KPI: High-Severity Alerts
+- **Baseline**: 15 alerts
+- **Target**: 5 alerts
+- **Time Window**: 90 days
+- **Unit**: alerts
+
 ## Focus Areas
 
 - **Prioritizes file write security issues** (highest risk)

docs/src/content/docs/examples/campaigns/security-audit.campaign.md

@@ -2,40 +2,13 @@
 title: Security Audit Campaign Example
 id: security-audit-2026
 name: Security Audit 2026
-version: v1
-state: planned
 project-url: https://github.com/orgs/example/projects/42
-tracker-label: z_campaign_security-audit-2026
 
-# Worker workflows that will be discovered and dispatched
 workflows:
   - security-scanner
   - dependency-updater
   - vulnerability-reporter
 
-# Campaign memory storage
-memory-paths:
-  - memory/campaigns/security-audit-2026/**
-metrics-glob: memory/campaigns/security-audit-2026/metrics/*.json
-cursor-glob: memory/campaigns/security-audit-2026/cursor.json
-
-# Campaign goals and KPIs
-objective: Reduce security vulnerabilities to zero critical and less than 5 high-severity issues
-kpis:
-  - name: Critical Vulnerabilities
-    baseline: 3
-    target: 0
-    unit: issues
-    time_window_days: 90
-    priority: primary
-  - name: High-Severity Vulnerabilities
-    baseline: 12
-    target: 5
-    unit: issues
-    time_window_days: 90
-    priority: supporting
-
-# Governance
 governance:
   max-new-items-per-run: 10
   max-discovery-items-per-run: 100
@@ -46,7 +19,6 @@ governance:
     - no-campaign
     - no-bot
 
-# Team
 owners:
   - "@security-team"
 executive-sponsors:
@@ -58,6 +30,26 @@ risk-level: high
 
 This campaign orchestrates a comprehensive security audit across all repositories, focusing on:
 
+## Objective
+
+Reduce security vulnerabilities to zero critical and less than 5 high-severity issues.
+
+## Key Performance Indicators (KPIs)
+
+### Primary KPI: Critical Vulnerabilities
+- **Baseline**: 3 issues
+- **Target**: 0 issues
+- **Time Window**: 90 days
+- **Unit**: issues
+
+### Supporting KPI: High-Severity Vulnerabilities
+- **Baseline**: 12 issues
+- **Target**: 5 issues
+- **Time Window**: 90 days
+- **Unit**: issues
+
+## Focus Areas
+
 1. **Vulnerability Scanning**: Identify and track security vulnerabilities
 2. **Dependency Updates**: Update outdated dependencies with known vulnerabilities
 3. **Compliance Reporting**: Generate security compliance reports for stakeholders