Campaign: Security Alert Burndown

[mnkiefer]

🎯 Campaign Setup Status

Campaign ID: issue-10444-campaign
State: Planned (Awaiting Customization)

---

✅ Completed Steps

1. GitHub Project Board Created

A new GitHub Project has been created with:

• Title: Campaign: Template Campaign (Issue Campaign: Security Alert Burndown #10444)
• Organization: githubnext
• Default Views:
  • Campaign Roadmap (timeline view)
  • Task Tracker (table view)
  • Progress Board (kanban board)

2. Workflow Discovery Complete

Comprehensive workflow catalog created with 99 agentic workflows organized into 12 categories:

Category	Count	Examples
Analysis & Research	13	agent-performance-analyzer, research, scout
Code Quality	19	code-scanning-fixer, duplicate-code-detector, grumpy-reviewer
Documentation	12	daily-doc-updater, technical-doc-writer, docs-noob-tester
Security & Compliance	9	security-review, static-analysis-report, code-scanning-fixer
Monitoring & Health	20	ci-doctor, audit-workflows, workflow-health-manager
Content Generation	12	daily-team-status, discussion-task-miner, weekly-issue-summary
Command-Based	9	/craft, /brave, /archie, /plan
Dependency Management	6	cli-version-checker, daily-workflow-updater, dependabot-go-checker
Development Assistance	8	issue-classifier, changeset, dev-hawk
Testing & Validation	6	smoke-claude, smoke-copilot, daily-multi-device-docs-tester
Examples & Templates	4	example-workflow-analyzer, example-permissions-warning
Report Generation	4	copilot-pr-merged-report, org-health-report

3. Campaign Specification File Created

Location: .github/workflows/issue-10444-campaign.campaign.md

The campaign spec file has been generated with:

• Template structure ready for customization
• Complete workflow catalog reference
• Suggested workflow combinations by campaign type
• Placeholder configuration (owners, workflows, goals)

---

⏳ Next Steps Required

Missing Information

To complete the campaign setup, the following information is needed from this issue:

1. Campaign Goal: What is the primary objective of this campaign?
2. Scope: Which repositories, teams, or components are involved?
3. Workflows Needed: Which specific workflows should be included?
4. Timeline: When should this campaign start and end?
5. Ownership: Who owns this campaign and who are the sponsors?
6. Risk Level: Low, Medium, or High?
7. Success Metrics: How will success be measured?

Suggested Campaign Types

Based on available workflows, here are some common campaign patterns:

🔒 Security Hardening Campaign

• Workflows: security-review, code-scanning-fixer, static-analysis-report, daily-malicious-code-scan
• Goal: Comprehensive security scanning and vulnerability remediation

✨ Code Quality Sprint Campaign

• Workflows: breaking-change-checker, duplicate-code-detector, pr-nitpick-reviewer, daily-code-metrics
• Goal: Systematic code quality improvement

📚 Documentation Refresh Campaign

• Workflows: daily-doc-updater, docs-noob-tester, technical-doc-writer, glossary-maintainer
• Goal: Complete documentation review and enhancement

⚡ Performance Optimization Campaign

• Workflows: ci-coach, daily-cli-performance, portfolio-analyst, hourly-ci-cleaner
• Goal: CI/CD and runtime performance improvements

🏥 Repository Health Campaign

• Workflows: audit-workflows, workflow-health-manager, metrics-collector, stale-repo-identifier
• Goal: Overall repository health and maintenance

---

🤖 Instructions for Copilot Coding Agent

Once the campaign requirements are clarified and the specification file is customized:

Your Task

Run the following command to compile the campaign and generate all necessary files:

gh aw compile issue-10444-campaign

What This Does

The compile command will:

1. Parse the campaign specification file
2. Generate compiled workflow files for each selected workflow
3. Set up project board integration
4. Create any necessary configuration files
5. Validate the campaign structure

After Compilation

1. Review all generated files
2. Ensure custom project fields are properly configured
3. Create a pull request with:
   • Title: [Campaign] Setup: Issue #10444 Campaign
   • Body: Summary of the campaign configuration and generated files
   • Files: All compiled campaign files and the specification

Project Field Setup

After the PR is merged, the project will need custom fields created:

• Worker/Workflow: Single select (list of workflow IDs)
• Priority: Single select (High, Medium, Low)
• Status: Single select (Todo, In Progress, Review required, Blocked, Done, Closed)
• Start Date: Date field
• End Date: Date field
• Effort: Single select (Small 1-3 days, Medium 1 week, Large 2+ weeks)

---

📋 Campaign Specification Template

The campaign spec file includes:

• Complete frontmatter configuration
• Workflow category reference
• Suggested workflow combinations
• Agent behavior guidelines
• Timeline and success metrics sections
• Next steps for customization

File Location: .github/workflows/issue-10444-campaign.campaign.md

---

🔄 Workflow Status

• ✅ Project board created
• ✅ Workflow catalog compiled
• ✅ Campaign spec file generated
• ⏳ Awaiting issue requirements clarification
• ⏳ Campaign customization pending
• ⏳ Compilation and PR creation pending

[github-actions]

✅ Campaign setup complete! Campaign Generator has successfully coordinated your campaign creation.