+
+ 
+ 
+ 
+
` block after the existing badges section (line 15), creating a distinct row for OpenSpec-specific badges.
+
+**Rationale:** Keeps OpenSpec metrics visually grouped and separate from standard project badges (CI, npm, license, Discord).
+
+**Alternative considered:** Inline with existing badges - would make the line too long and mix different badge categories.
+
+### 3. Workflow Trigger
+
+**Decision:** Trigger badge generation on push to main branch only.
+
+**Rationale:** Badges should reflect the current state of the main branch. Running on PRs would be wasteful since those badges wouldn't be used.
+
+### 4. Badge Style
+
+**Decision:** Use `classic` style with `show_label: true`
+
+**Rationale:** Classic style provides gradient appearance matching the shield.io badges used elsewhere. Labels provide context for what each metric represents.
+
+## Risks / Trade-offs
+
+**[gh-pages branch required]** → The action publishes to gh-pages branch. If the branch doesn't exist, the action will create it. This is expected behavior.
+
+**[Badge URLs depend on repository path]** → Badge image URLs are hardcoded to the repository path. If the repo is forked, badge URLs would point to the original repo. → This is acceptable for the main repository; forks can update URLs if needed.
+
+**[Action permissions]** → Workflow requires `contents: write` permission. → Standard for actions that commit to branches.
diff --git a/openspec/changes/add-openspec-badges/proposal.md b/openspec/changes/add-openspec-badges/proposal.md
new file mode 100644
index 000000000..c235cb532
--- /dev/null
+++ b/openspec/changes/add-openspec-badges/proposal.md
@@ -0,0 +1,37 @@
+## Why
+
+The README currently displays CI, npm, license, and Discord badges but lacks visibility into OpenSpec-specific project health metrics. Adding OpenSpec badges will showcase the framework's own capabilities and provide at-a-glance insight into the project's specification coverage and change activity.
+
+## What Changes
+
+- Add a new row of OpenSpec badges to the README header section
+- Configure the openspec-badge-action GitHub Action to generate badges
+- Display three metrics: number of specs, open changes, and open tasks
+- Use classic style with labels for consistency and clarity
+
+## Capabilities
+
+### New Capabilities
+
+- `readme-badges`: Configuration and display of OpenSpec metric badges in project README
+
+### Modified Capabilities
+
+None - this change adds new content to the README without modifying existing OpenSpec behavior.
+
+## Impact
+
+- **README.md**: New badge row added after the existing badges section
+- **.github/workflows/**: New workflow file for badge generation
+- **gh-pages branch**: Will store generated SVG badge files (created automatically by the action)
+- **Repository settings**: Requires `contents: write` permission for the workflow
+
+## Prerequisites for Project Owner
+
+Before the badges will display correctly, the project owner must complete these steps after merging:
+
+1. **Enable GitHub Pages**: Go to repository Settings → Pages → Set source to "Deploy from a branch" and select the `gh-pages` branch (root folder)
+2. **Run the workflow**: The badge workflow must run at least once to generate the initial SVG files and create the gh-pages branch
+3. **Verify permissions**: Ensure GitHub Actions has write access to the repository (Settings → Actions → General → Workflow permissions → "Read and write permissions")
+
+Until these steps are completed, the badge images in the README will show as broken/missing.
diff --git a/openspec/changes/add-openspec-badges/specs/readme-badges/spec.md b/openspec/changes/add-openspec-badges/specs/readme-badges/spec.md
new file mode 100644
index 000000000..43508332b
--- /dev/null
+++ b/openspec/changes/add-openspec-badges/specs/readme-badges/spec.md
@@ -0,0 +1,41 @@
+## ADDED Requirements
+
+### Requirement: OpenSpec badges displayed in README
+
+The README SHALL display OpenSpec metric badges in a new row after the existing badges section, showing project health metrics generated by the openspec-badge-action.
+
+#### Scenario: Badges visible in README
+- **WHEN** a user views the README.md file
+- **THEN** a row of three OpenSpec badges SHALL be visible below the existing CI/npm/license/Discord badges
+
+#### Scenario: Badge row contains correct metrics
+- **WHEN** the OpenSpec badge row is displayed
+- **THEN** it SHALL contain badges for: number_of_specs, open_changes, and tasks_status metrics
+
+### Requirement: Badge generation workflow
+
+The repository SHALL include a GitHub Actions workflow that generates OpenSpec metric badges using the weAretechnative/openspec-badge-action.
+
+#### Scenario: Workflow triggers on main branch push
+- **WHEN** code is pushed to the main branch
+- **THEN** the badge generation workflow SHALL execute
+
+#### Scenario: Workflow generates specified metrics
+- **WHEN** the badge workflow executes
+- **THEN** it SHALL generate badges for: number_of_specs, open_changes, and tasks_status
+
+#### Scenario: Workflow uses classic style with labels
+- **WHEN** the badge workflow executes
+- **THEN** it SHALL use `badge_style: classic` and `show_label: true` configuration
+
+### Requirement: Badge images accessible via gh-pages
+
+The generated badge SVG files SHALL be published to the gh-pages branch and accessible via raw.githubusercontent.com URLs.
+
+#### Scenario: Badges published to gh-pages
+- **WHEN** the badge workflow completes successfully
+- **THEN** SVG badge files SHALL exist in the gh-pages branch under the badges/ directory
+
+#### Scenario: README references correct badge URLs
+- **WHEN** the README displays OpenSpec badges
+- **THEN** each badge image URL SHALL follow the pattern: `https://raw.githubusercontent.com/Fission-AI/OpenSpec/gh-pages/badges/