Use GitHub UI project selection instead of manual URL entry in campaign template (#8425)

Author: Copilot

.github/ISSUE_TEMPLATE/start-campaign.yml

@@ -8,21 +8,30 @@ body:
       value: |
         ## Start an Agentic Campaign
         
-        Provide project board URL and campaign goal. The AI generates technical specs, best practices, and governance policies.
+        **📌 Important: Project Board Assignment**
+        
+        This campaign must be assigned to a GitHub Project board. You have two options:
+        
+        **Option A (Recommended):** Create this issue from your project board:
+        1. Open your GitHub Project board
+        2. Click "Add item" → "Create new issue"
+        3. Select this repository and choose this template
+        4. The project will be automatically assigned ✅
+        
+        **Option B:** Create from issues page (assign project before submitting):
+        1. Fill out the form below
+        2. **Scroll down and use the project selector at the bottom** to assign a project board
+        3. Submit the issue
+        
+        The AI will automatically detect the project board assignment and generate the campaign specification with the correct project URL.
         
         **Process:**
-        1. AI analyzes goal and generates campaign spec
-        2. PR created with spec and orchestrator files
-        3. Review and merge to activate
-
-  - type: input
-    id: project_url
-    attributes:
-      label: Project Board URL
-      description: URL of your GitHub Project board for tracking this agentic campaign
-      placeholder: https://github.com/orgs/your-org/projects/123
-    validations:
-      required: true
+        1. Fill out the campaign goal and context fields below
+        2. **Ensure a project board is assigned** (see options above)
+        3. Submit the issue
+        4. AI analyzes goal and generates campaign spec with project tracking
+        5. PR created with spec and orchestrator files
+        6. Review and merge to activate
 
   - type: textarea
     id: campaign_goal

.github/agents/agentic-campaign-designer.agent.md

@@ -19,21 +19,23 @@ This agent operates in two distinct modes:
 When triggered from a GitHub issue created via a "Create a Campaign" issue form:
 
 1. **Parse the Issue Form Data** - Extract campaign requirements from the issue body:
-   - **Campaign Name**: The `campaign_name` field from the issue form
-   - **Campaign Description**: The `campaign_description` field describing the campaign's purpose
+   - **Agentic Campaign Goal**: The `campaign_goal` field describing what the campaign should accomplish
    - **Additional Context**: The optional `additional_context` field with extra requirements
+   - **Project Board Assignment**: Query the issue's project assignments to get the project URL
 
 2. **Generate the Campaign Specification** - Create a complete `.campaign.md` file without interaction:
+   - Derive a clear campaign name from the goal
    - Analyze requirements and determine campaign ID (kebab-case)
+   - Retrieve project URL from issue's project board assignment
    - Identify required workflows and their purposes
    - Determine owners, sponsors, and risk level
    - Configure allowed safe outputs for campaign operations
    - Apply governance and security best practices
 
 3. **Create the Campaign File** at `.github/workflows/<campaign-id>.campaign.md`:
-   - Use a kebab-case campaign ID derived from the campaign name (e.g., "Security Q1 2025" → "security-q1-2025")
+   - Use a kebab-case campaign ID derived from the goal (e.g., "Security Vulnerability Remediation" → "security-vulnerability-remediation")
    - **CRITICAL**: Before creating, check if the file exists. If it does, append a suffix like `-v2` or a timestamp
-   - Include complete frontmatter with all necessary configuration
+   - Include complete frontmatter with all necessary configuration including the project URL
    - Write a clear description of campaign goals and agent behavior
 
 4. **Compile the Campaign** using `gh aw compile <campaign-id>` to generate the orchestrator workflow
@@ -88,11 +90,13 @@ DO NOT ask all these questions at once; instead, engage in a back-and-forth conv
 
 3. **Campaign Spec Fields**
 
-   Based on the conversation, determine values for:
+   Based on the conversation (Interactive Mode) or issue data (Issue Form Mode), determine values for:
    - `id` — stable identifier in kebab-case (e.g., `security-q1-2025`)
    - `name` — human-friendly title
    - `description` — short explanation of campaign purpose
    - `project-url` — GitHub Project URL for campaign dashboard
+     - **Issue Form Mode**: Retrieve from issue's project assignments using GitHub CLI
+     - **Interactive Mode**: Ask the user for the project URL
    - `workflows` — workflow IDs (basenames under `.github/workflows/` without `.md`)
    - `memory-paths` — repo-memory paths under `memory/campaigns/<campaign-id>-*/**`
    - `owners` — primary human owners
@@ -118,35 +122,54 @@ DO NOT ask all these questions at once; instead, engage in a back-and-forth conv
 
 When processing a GitHub issue created via the campaign creation form, follow these steps:
 
-### Step 1: Parse the Issue Form
+### Step 1: Parse the Issue Form and Retrieve Project Assignment
 
 Extract the following fields from the issue body:
-- **Campaign Name** (required): Look for the "Campaign Name" section
-- **Campaign Description** (required): Look for the "Campaign Description" section
+- **Agentic Campaign Goal** (required): Look for the "Agentic Campaign Goal" section
 - **Additional Context** (optional): Look for the "Additional Context" section
+- **Project Board Assignment** (required): Query the issue's project board assignments using GitHub CLI
 
 Example issue body format:
 ```
-### Campaign Name
-Security Q1 2025
-
-### Campaign Description
+### Agentic Campaign Goal
 Automated security improvements and vulnerability remediation
 
 ### Additional Context (Optional)
-Should track progress in a GitHub Project and allow creating issues and PRs
+Should allow creating issues and PRs
+```
+
+**Important: Retrieve the Project Board URL from Issue Assignments**
+
+The user adds the issue to a GitHub Project board via the UI after creating the issue. You must query this assignment using GitHub CLI (replace `ISSUE_NUMBER` with the actual issue number from `github.event.issue.number`):
+
+```bash
+gh issue view ISSUE_NUMBER --json projectItems --jq '.projectItems.nodes[0]?.project?.url // empty'
 ```
 
+Alternatively, use the github-issue-query skill (from the repository root):
+
+```bash
+./skills/github-issue-query/query-issues.sh --jq '.[] | select(.number == ISSUE_NUMBER) | .projectItems.nodes[0]?.project?.url // empty'
+```
+
+**If no project is assigned:**
+- Inform the user that a project board assignment is required
+- Provide clear instructions: "Please assign this issue to a GitHub Project board using the project selector in the issue sidebar, then mention me again to continue."
+- Explain they can also recreate the issue from the project board directly (which auto-assigns the project)
+- Do not proceed with campaign creation without a valid project URL
+
 ### Step 2: Design the Campaign Specification
 
-Based on the parsed requirements, determine:
+Based on the parsed requirements and project assignment, determine:
 
-1. **Campaign ID**: Convert the campaign name to kebab-case (e.g., "Security Q1 2025" → "security-q1-2025")
-2. **Workflows**: Identify workflows needed to implement the campaign
-3. **Owners**: Determine who will own and maintain the campaign
-4. **Risk Level**: Assess the risk level based on the campaign's scope
-5. **Safe Outputs**: Determine which safe outputs should be allowed
-6. **Approval Policy**: Define approval requirements based on risk level
+1. **Campaign Name**: Derive a clear campaign name from the goal (e.g., "Security Vulnerability Remediation", "Node.js Migration")
+2. **Campaign ID**: Convert the campaign name to kebab-case (e.g., "Security Vulnerability Remediation" → "security-vulnerability-remediation")
+3. **Project URL**: Use the project URL retrieved from the issue's project assignments
+4. **Workflows**: Identify workflows needed to implement the campaign
+5. **Owners**: Determine who will own and maintain the campaign
+6. **Risk Level**: Assess the risk level based on the campaign's scope
+7. **Safe Outputs**: Determine which safe outputs should be allowed
+8. **Approval Policy**: Define approval requirements based on risk level
 
 ### Step 3: Create the Campaign File
 

docs/src/content/docs/guides/campaigns/getting-started.md

@@ -82,12 +82,27 @@ Campaign tooling enforces that a campaign repo-memory write includes a cursor an
 
 ## Start an agentic campaign with GitHub Issue Forms
 
-This repo also includes a “🚀 Start an Agentic Campaign” issue form. Use it when you want to capture intent first and let an agent scaffold the spec in a PR.
+This repo also includes a "🚀 Start an Agentic Campaign" issue form. Use it when you want to capture intent first and let an agent scaffold the spec in a PR.
+
+### Creating the Campaign Issue
+
+**Option A (Recommended):** Create from your project board:
+1. Open your GitHub Project board
+2. Click "Add item" → "Create new issue"  
+3. Select this repository and choose the "🚀 Start an Agentic Campaign" template
+4. The project will be automatically assigned to the issue ✅
+
+**Option B:** Create from the repository's Issues page:
+1. Navigate to Issues → New Issue
+2. Select "🚀 Start an Agentic Campaign"
+3. **Important:** Before submitting, scroll down and use the project selector to assign the issue to your project board
+
+Creating the issue from the project board (Option A) is recommended as it ensures the project is automatically assigned and reduces the chance of forgetting this required step.
 
 When you submit the issue form:
 
 1. **an agentic campaign issue is created** - This becomes your campaign's central hub with the `campaign` and `campaign-tracker` labels
-2. **An agent validates your project board** - Ensures the URL is accessible and properly configured
+2. **An agent validates your project board** - Ensures the project assignment exists and is accessible
 3. **an agentic campaign spec is generated** - Creates `.github/workflows/<id>.campaign.md` with your inputs as a PR
 4. **The spec is linked to the issue** - So you can track the technical implementation
 5. **Your project board is configured** - The agent sets up tracking labels and fields
@@ -101,3 +116,4 @@ You manage the agentic campaign from the issue. The generated workflow files are
 - **Lower barrier to entry**: No need to understand campaign spec file format
 - **Traceable**: Issue serves as the agentic campaign's command center with full history
 - **Agent-assisted scaffolding**: Automated generation of spec files and workflows
+- **Automatic project assignment**: When created from project board, the project is automatically linked

skills/github-issue-query/SKILL.md

@@ -88,6 +88,11 @@ Use the `--jq` argument to filter and transform the output:
 ./query-issues.sh --jq '.[] | {number, title, labels: [.labels[].name]}'
 ```
 
+**Get project board assignments:**
+```bash
+./query-issues.sh --jq '.[] | {number, title, projects: [.projectItems.nodes[]? | .project?.url]}'
+```
+
 **Find old issues (created over 30 days ago):**
 ```bash
 ./query-issues.sh --jq '.[] | select(.createdAt < (now - 2592000 | strftime("%Y-%m-%dT%H:%M:%SZ")))'

skills/github-issue-query/query-issues.sh

@@ -47,7 +47,7 @@ while [[ $# -gt 0 ]]; do
 done
 
 # JSON fields to fetch
-JSON_FIELDS="number,title,state,author,createdAt,updatedAt,closedAt,body,labels,assignees,comments,milestone,url"
+JSON_FIELDS="number,title,state,author,createdAt,updatedAt,closedAt,body,labels,assignees,comments,milestone,url,projectItems"
 
 # Build and execute gh command with proper quoting
 if [[ -n "$REPO" ]]; then
@@ -93,7 +93,8 @@ else
       "assignees": "array - Array of assignee objects with login field",
       "comments": "object - Comments info with totalCount field",
       "milestone": "object|null - Milestone info with title field",
-      "url": "string - Issue URL"
+      "url": "string - Issue URL",
+      "projectItems": "object - Project assignments with totalCount and nodes array containing project info"
     }
   },
   "suggested_queries": [
@@ -104,6 +105,7 @@ else
     {"description": "Get issues with label", "query": ".[] | select(.labels | map(.name) | index(\"bug\"))"},
     {"description": "Get issues with many comments", "query": ".[] | select(.comments.totalCount > 5) | {number, title, comments: .comments.totalCount}"},
     {"description": "Get issues with labels", "query": ".[] | {number, title, labels: [.labels[].name]}"},
+    {"description": "Get issues with project assignments", "query": ".[] | {number, title, projects: [.projectItems.nodes[]? | .project?.url]}"},
     {"description": "Count by state", "query": "group_by(.state) | map({state: .[0].state, count: length})"}
   ]
 }