snap-issue-chrome-extension

ARCHIVED

Build a Chrome extension (Manifest V3) called “Snap Issue” for personal/internal use. Primary goal: Let me press a keyboard shortcut or click the extension icon, draw a rectangle over the current page, capture only that selected area, and immediately create a lightweight GitHub issue from it.

STAGES

  1. proposal05-19
  2. requirements05-19
  3. design05-19predates the Figma as-is + proposed pair
  4. tasks05-19
  5. build—
  6. archived—

CAPABILITIES — 2 IN ONE CHANGE

  • snap-issue-github-config2 requirements
  • snap-issue-viewport-capture3 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1User can start capture from the extension icon (Scenario: Start capture from the extension icon)not stated
  • ✓1.2User can start capture from the keyboard command (Scenario: Start capture from the keyboard command)not stated
  • ✓1.3User can draw a rectangle with dimmed outside region (Scenario: Draw a rectangle with dimmed outside region)not stated
  • ✓1.4User can confirm selection with Enter (Scenario: Confirm selection with Enter)not stated
  • ✓1.5User can cancel selection with Escape (Scenario: Cancel selection with Escape)not stated
  • ✓1.6User can capture again in the same browser session (Scenario: Capture again in the same browser session)not stated
  • ✓1.7User gets a crop that aligns with selection on high-DPI (Scenario: Crop aligns with selection on high-DPI)not stated
  • ✓1.8User sees blocked flow when selection is invalid (Scenario: Invalid selection is blocked)not stated
  • ✓1.9User sees an actionable error when visible-tab capture fails (Scenario: Visible-tab capture failure is surfaced)not stated
  • ✓1.10User can persist GitHub settings in sync storage (Scenario: Persist settings in sync storage)not stated
  • ✓1.11User is blocked from submit with a clear path to Options when GitHub settings are missing (Scenario: Missing required GitHub settings block submit)not stated
  • ✓1.12User can create an issue with structured title and body (Scenario: Create issue with structured title and body)not stated
  • ✓1.13User gets a locally saved screenshot artifact referenced in the issue for MVP (Scenario: MVP screenshot is saved locally and referenced in the issue)not stated
  • ✓1.14User sees a readable GitHub error when issue creation fails (Scenario: Failed issue creation surfaces GitHub error)not stated

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-05-19
    • chore(openspec): archive snap-issue-chrome-extension

History read from a manifest built at 2026-09-30 (09e7bcc).

0 pull requests, found by commits touching the change folder · 1 commit(s) carry no pull request number