Name: phase_1a_url_manifest
Author: briancl2

Prompt file imported from briancl2/CustomerNewsletter (.github/prompts/phase_1a_url_manifest.prompt.md). Copyright stays with the author.

Phase 1A: URL Manifest - Candidate Generation & Validation

<token_budget> Target: 10,000-20,000 tokens total

Strategy: Generate candidate URLs from known patterns, then spot-check validity

Generate candidates: ~1,000 tokens
Spot-check validation: 200-500 tokens per source
Manifest output: ~2,000 tokens </token_budget>

Generate Candidate URLs from patterns (no fetching yet)
Minimal Validation: Spot-check 1-2 URLs per source to confirm pattern
Boundary Check: Verify earliest/latest candidates span DATE_RANGE
Output Manifest: List of validated URLs for Phase 1B

NOT Phase 1A's job: Extracting content, reading changelogs, parsing features

Inputs

DATE_RANGE: YYYY-MM-DD to YYYY-MM-DD
Reference Year: Extracted from DATE_RANGE

Execution Strategy

STEP 1: Generate Candidates (~5 min, 1,000 tokens) For each source, generate candidate URLs using known patterns + DATE_RANGE months

STEP 2: Spot-Check (~10 min, 2,000-5,000 tokens)
Fetch 1-2 URLs per source to confirm:

URL exists (not 404)
Contains expected date/version info
Pattern is correct

STEP 3: Write Manifest (~2 min, 2,000 tokens) Output validated candidate URLs for Phase 1B

URL Pattern Reference & Candidate Generation

1. VS Code

Pattern: https://code.visualstudio.com/updates/v1_{VERSION} Candidate Generation:

Start: v1_104 (Aug → Sept release)
Range: v1_105 (Sept → Oct), v1_106 (Oct → Nov), v1_107 (Nov → Dec)

Spot-Check: Fetch updates index OR v1_105 to verify Oct release date

2. Visual Studio

Pattern: https://learn.microsoft.com/en-us/visualstudio/releases/{YEAR}/release-notes Candidate Generation:

VS 2022: Base URL (has Oct/Nov/Dec versions)
VS 2026: Base URL (GA Nov 24, 2025)

Spot-Check: Fetch both base URLs to confirm version lists

3. GitHub Changelog

Pattern: https://github.blog/changelog/{YEAR}/{MM}/ Candidate Generation:

/2025/10/ (Oct 6-31)
/2025/11/ (full month)
/2025/12/ (Dec 1-3)

Spot-Check: Sample one month URL to verify structure

4. GitHub Blog

Pattern: https://github.blog/latest/page/{N}/ Candidate Generation:

Page 1-5 (estimate based on ~20 posts/page, weekly cadence)

Spot-Check: Fetch page 1, estimate pagination depth

5. JetBrains

Pattern: https://plugins.jetbrains.com/api/plugins/17718/updates?page={N}&size=8 Candidate Generation:

Pages 1-3 (estimate ~2-3 releases/week = 16-24 versions in range)

Spot-Check: Fetch API page 1, parse JSON for date range

6. Copilot for Xcode

Pattern: https://github.com/github/CopilotForXcode/blob/main/CHANGELOG.md Candidate: Single file Spot-Check: Not needed (single URL)

Phase 1A Execution

Step 1: Generate Candidates (~2 min)

Based on DATE_RANGE, list candidate URLs for each source.

Step 2: Spot-Check (~5-10 min, 2,000-5,000 tokens)

Minimum validation per source:

VS Code: Check updates index OR one version page for date
Visual Studio: Confirm both 2022 and 2026 have releases
GitHub Changelog: Sample one month URL
GitHub Blog: Check page 1 date range
JetBrains: Fetch API page 1, check date range
Xcode: Confirm CHANGELOG.md exists

Key checks:

URLs don't 404
Dates align with expectations
Boundaries span DATE_RANGE

Step 3: Write Manifest (~2 min)

Output format:

# Phase 1A URL Manifest
DATE_RANGE: {start} to {end}
Generated: {date}

## URLs by Source

### VS Code
- v1_105: https://... (Oct 9)
- v1_106: https://... (Nov 12)

### Visual Studio 2022
- Base URL: https://... (Oct-Nov versions)

[etc.]

## Validation
- [x] Boundaries verified
- [x] No 0-entry months
- [x] Ready for Phase 1B

Success Criteria

All candidate URLs listed
Spot-checks pass
Earliest ≤ start, latest ≥ end
No month in DATE_RANGE has 0 entries

## Phase 1A: URL Manifest - Candidate Generation & Validation <token_budget> **Target: 10,000-20,000 tokens total** **Strategy**: Generate candidate URLs from known patterns, then spot-check validity - Generate candidates: ~1,000 tokens - Spot-check validation: 200-500 tokens per source - Manifest output: ~2,000 tokens </token_budget> <approach> **Key Insight**: We know URL architectures. Generate candidates FIRST, validate SECOND. 1. **Generate Candidate URLs** from patterns (no fetching yet) 2. **Minimal Validation**: Spot-check 1-2 URLs per source to confirm pattern 3. **Boundary Check**: Verify earliest/latest candidates span DATE_RANGE 4. **Output Manifest**: List of validated URLs for Phase 1B **NOT Phase 1A's job**: Extracting content, reading changelogs, parsing features </approach> ### Inputs - **DATE_RANGE**: YYYY-MM-DD to YYYY-MM-DD - **Reference Year**: Extracted from DATE_RANGE ### Execution Strategy **STEP 1: Generate Candidates** (~5 min, 1,000 tokens) For each source, generate candidate URLs using known patterns + DATE_RANGE months **STEP 2: Spot-Check** (~10 min, 2,000-5,000 tokens) Fetch 1-2 URLs per source to confirm: - URL exists (not 404) - Contains expected date/version info - Pattern is correct **STEP 3: Write Manifest** (~2 min, 2,000 tokens) Output validated candidate URLs for Phase 1B --- ## URL Pattern Reference & Candidate Generation ### 1. VS Code **Pattern**: `https://code.visualstudio.com/updates/v1_{VERSION}` **Candidate Generation**: ``` Start: v1_104 (Aug → Sept release) Range: v1_105 (Sept → Oct), v1_106 (Oct → Nov), v1_107 (Nov → Dec) ``` **Spot-Check**: Fetch updates index OR v1_105 to verify Oct release date ### 2. Visual Studio **Pattern**: `https://learn.microsoft.com/en-us/visualstudio/releases/{YEAR}/release-notes` **Candidate Generation**: ``` VS 2022: Base URL (has Oct/Nov/Dec versions) VS 2026: Base URL (GA Nov 24, 2025) ``` **Spot-Check**: Fetch both base URLs to confirm version lists ### 3. GitHub Changelog **Pattern**: `https://github.blog/changelog/{YEAR}/{MM}/` **Candidate Generation**: ``` /2025/10/ (Oct 6-31) /2025/11/ (full month) /2025/12/ (Dec 1-3) ``` **Spot-Check**: Sample one month URL to verify structure ### 4. GitHub Blog **Pattern**: `https://github.blog/latest/page/{N}/` **Candidate Generation**: ``` Page 1-5 (estimate based on ~20 posts/page, weekly cadence) ``` **Spot-Check**: Fetch page 1, estimate pagination depth ### 5. JetBrains **Pattern**: `https://plugins.jetbrains.com/api/plugins/17718/updates?page={N}&size=8` **Candidate Generation**: ``` Pages 1-3 (estimate ~2-3 releases/week = 16-24 versions in range) ``` **Spot-Check**: Fetch API page 1, parse JSON for date range ### 6. Copilot for Xcode **Pattern**: `https://github.com/github/CopilotForXcode/blob/main/CHANGELOG.md` **Candidate**: Single file **Spot-Check**: Not needed (single URL) --- ## Phase 1A Execution ### Step 1: Generate Candidates (~2 min) Based on DATE_RANGE, list candidate URLs for each source. ### Step 2: Spot-Check (~5-10 min, 2,000-5,000 tokens) **Minimum validation per source**: - VS Code: Check updates index OR one version page for date - Visual Studio: Confirm both 2022 and 2026 have releases - GitHub Changelog: Sample one month URL - GitHub Blog: Check page 1 date range - JetBrains: Fetch API page 1, check date range - Xcode: Confirm CHANGELOG.md exists **Key checks**: - URLs don't 404 - Dates align with expectations - Boundaries span DATE_RANGE ### Step 3: Write Manifest (~2 min) Output format: ```markdown # Phase 1A URL Manifest DATE_RANGE: {start} to {end} Generated: {date} ## URLs by Source ### VS Code - v1_105: https://... (Oct 9) - v1_106: https://... (Nov 12) ### Visual Studio 2022 - Base URL: https://... (Oct-Nov versions) [etc.] ## Validation - [x] Boundaries verified - [x] No 0-entry months - [x] Ready for Phase 1B ``` ### Success Criteria - All candidate URLs listed - Spot-checks pass - Earliest ≤ start, latest ≥ end - No month in DATE_RANGE has 0 entries ```

{ "prompt": "## Phase 1A: URL Manifest - Candidate Generation & Validation\n\n<token_budget>\n**Target: 10,000-20,000 tokens total**\n\n**Strategy**: Generate candidate URLs from known patterns, then spot-check validity\n- Generate candidates: ~1,000 tokens\n- Spot-check validation: 200-500 tokens per source\n- Manifest output: ~2,000 tokens\n</token_budget>\n\n<approach>\n**Key Insight**: We know URL architectures. Generate candidates FIRST, validate SECOND.\n\n1. **Generate Candidate URLs** from patterns (no fetching yet)\n2. **Minimal Validation**: Spot-check 1-2 URLs per source to confirm pattern\n3. **Boundary Check**: Verify earliest/latest candidates span DATE_RANGE\n4. **Output Manifest**: List of validated URLs for Phase 1B\n\n**NOT Phase 1A's job**: Extracting content, reading changelogs, parsing features\n</approach>\n\n### Inputs\n- **DATE_RANGE**: YYYY-MM-DD to YYYY-MM-DD\n- **Reference Year**: Extracted from DATE_RANGE\n\n### Execution Strategy\n\n**STEP 1: Generate Candidates** (~5 min, 1,000 tokens)\nFor each source, generate candidate URLs using known patterns + DATE_RANGE months\n\n**STEP 2: Spot-Check** (~10 min, 2,000-5,000 tokens) \nFetch 1-2 URLs per source to confirm:\n- URL exists (not 404)\n- Contains expected date/version info\n- Pattern is correct\n\n**STEP 3: Write Manifest** (~2 min, 2,000 tokens)\nOutput validated candidate URLs for Phase 1B\n\n---\n\n## URL Pattern Reference & Candidate Generation\n\n### 1. VS Code\n**Pattern**: `https://code.visualstudio.com/updates/v1_{VERSION}`\n**Candidate Generation**:\n```\nStart: v1_104 (Aug → Sept release)\nRange: v1_105 (Sept → Oct), v1_106 (Oct → Nov), v1_107 (Nov → Dec)\n```\n**Spot-Check**: Fetch updates index OR v1_105 to verify Oct release date\n\n### 2. Visual Studio\n**Pattern**: `https://learn.microsoft.com/en-us/visualstudio/releases/{YEAR}/release-notes`\n**Candidate Generation**:\n```\nVS 2022: Base URL (has Oct/Nov/Dec versions)\nVS 2026: Base URL (GA Nov 24, 2025)\n```\n**Spot-Check**: Fetch both base URLs to confirm version lists\n\n### 3. GitHub Changelog\n**Pattern**: `https://github.blog/changelog/{YEAR}/{MM}/`\n**Candidate Generation**:\n```\n/2025/10/ (Oct 6-31)\n/2025/11/ (full month)\n/2025/12/ (Dec 1-3)\n```\n**Spot-Check**: Sample one month URL to verify structure\n\n### 4. GitHub Blog\n**Pattern**: `https://github.blog/latest/page/{N}/`\n**Candidate Generation**:\n```\nPage 1-5 (estimate based on ~20 posts/page, weekly cadence)\n```\n**Spot-Check**: Fetch page 1, estimate pagination depth\n\n### 5. JetBrains\n**Pattern**: `https://plugins.jetbrains.com/api/plugins/17718/updates?page={N}&size=8`\n**Candidate Generation**:\n```\nPages 1-3 (estimate ~2-3 releases/week = 16-24 versions in range)\n```\n**Spot-Check**: Fetch API page 1, parse JSON for date range\n\n### 6. Copilot for Xcode\n**Pattern**: `https://github.com/github/CopilotForXcode/blob/main/CHANGELOG.md`\n**Candidate**: Single file\n**Spot-Check**: Not needed (single URL)\n\n---\n\n## Phase 1A Execution\n\n### Step 1: Generate Candidates (~2 min)\nBased on DATE_RANGE, list candidate URLs for each source.\n\n### Step 2: Spot-Check (~5-10 min, 2,000-5,000 tokens)\n**Minimum validation per source**:\n- VS Code: Check updates index OR one version page for date\n- Visual Studio: Confirm both 2022 and 2026 have releases\n- GitHub Changelog: Sample one month URL\n- GitHub Blog: Check page 1 date range\n- JetBrains: Fetch API page 1, check date range \n- Xcode: Confirm CHANGELOG.md exists\n\n**Key checks**:\n- URLs don't 404\n- Dates align with expectations\n- Boundaries span DATE_RANGE\n\n### Step 3: Write Manifest (~2 min)\nOutput format:\n```markdown\n# Phase 1A URL Manifest\nDATE_RANGE: {start} to {end}\nGenerated: {date}\n\n## URLs by Source\n\n### VS Code\n- v1_105: https://... (Oct 9)\n- v1_106: https://... (Nov 12)\n\n### Visual Studio 2022\n- Base URL: https://... (Oct-Nov versions)\n\n[etc.]\n\n## Validation\n- [x] Boundaries verified\n- [x] No 0-entry months\n- [x] Ready for Phase 1B\n```\n\n### Success Criteria\n- All candidate URLs listed\n- Spot-checks pass\n- Earliest ≤ start, latest ≥ end\n- No month in DATE_RANGE has 0 entries\n```", "variables": [], "notes": "1. **Generate Candidate URLs** from patterns (no fetching yet) 2. **Minimal Validation**: Spot-check 1-2 URLs per source to confirm pattern 3. **Boundary Check**: Verify earliest/latest candidates span DATE_RANGE 4. **Output Manifest**: List of validated URLs for Phase 1B", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/briancl2/CustomerNewsletter", "path": ".github/prompts/phase_1a_url_manifest.prompt.md", "ref": "8b2071921db06729c44662d34823843d79ff7bc9", "url": "https://github.com/briancl2/CustomerNewsletter/blob/8b2071921db06729c44662d34823843d79ff7bc9/.github/prompts/phase_1a_url_manifest.prompt.md", "key": "briancl2/CustomerNewsletter/.github/prompts/phase_1a_url_manifest.prompt.md" } } }

phase_1a_url_manifest

About