docs: Adapt badges

.vibe/development-plan-package-for-npmjs.md

@@ -18,7 +18,7 @@ Set up professional publishing workflow for the responsible-vibe MCP server to n
 ### Completed
 - [x] Created development plan file
 - [x] Analyzed current project structure
-- [x] Confirmed git repository setup (https://github.com/mrsimpson/vibe-feature-mcp.git)
+- [x] Confirmed git repository setup (https://github.com/codemcp/workflows.git)
 - [x] Verified no existing GitHub Actions workflows
 - [x] Confirmed no existing git tags (clean slate for versioning)
 - [x] Analyzed package.json structure and dependencies
@@ -180,7 +180,7 @@ Set up professional publishing workflow for the responsible-vibe MCP server to n
 *None yet*
 
 ## Key Decisions
-- **Repository**: Using existing GitHub repo (https://github.com/mrsimpson/vibe-feature-mcp.git)
+- **Repository**: Using existing GitHub repo (https://github.com/codemcp/workflows.git)
 - **Current State**: No existing tags or GitHub Actions (clean slate)
 - **Package Name**: @mrsimpson/responsible-vibe-mcp (scoped npm package)
 - **Versioning**: Conventional commits with automatic semantic versioning
@@ -215,7 +215,7 @@ Set up professional publishing workflow for the responsible-vibe MCP server to n
    - Copy the token (starts with `npm_`)
 
 2. **Add GitHub Secret:**
-   - Go to your repo: https://github.com/mrsimpson/vibe-feature-mcp/settings/secrets/actions
+   - Go to your repo: https://github.com/codemcp/workflows/settings/secrets/actions
    - Click "New repository secret"
    - Name: `NPM_TOKEN`
    - Value: Your npm token

README.md

@@ -2,8 +2,10 @@
 
 fka. "Responsible Vibe MCP"
 
-[![Tests](https://github.com/mrsimpson/vibe-feature-mcp/actions/workflows/pr.yml/badge.svg)](https://github.com/mrsimpson/vibe-feature-mcp/actions/workflows/pr.yml)
-[![Release](https://github.com/mrsimpson/vibe-feature-mcp/actions/workflows/release.yml/badge.svg)](https://github.com/mrsimpson/vibe-feature-mcp/actions/workflows/release.yml)
+Vibe coding is dead. Agentic Engineering is on the rise. Workflows have been here forever.
+
+[![Tests](https://github.com/codemcp/workflows/actions/workflows/pr.yml/badge.svg)](https://github.com/codemcp/workflows/actions/workflows/pr.yml)
+[![Release](https://github.com/codemcp/workflows/actions/workflows/release.yml/badge.svg)](https://github.com/codemcp/workflows/actions/workflows/release.yml)
 [![npm version](https://badge.fury.io/js/@codemcp%2Fworkflows.svg)](https://badge.fury.io/js/@codemcp%2Fworkflows)
 
 Transform any AI coding agent into a structured development partner with battle-tested engineering workflows.
@@ -88,4 +90,4 @@ See **[Crowd MCP Integration Guide →](packages/docs/user/crowd-mcp-integration
 
 ---
 
-**[Open Source](LICENSE.md)** | **[Issues](https://github.com/mrsimpson/vibe-feature-mcp/issues)**
+**[Open Source](LICENSE.md)** | **[Issues](https://github.com/codemcp/workflows/issues)**

packages/docs/dev/PUBLISHING.md

@@ -22,7 +22,7 @@ The project uses GitHub Actions to automatically:
    - Copy the token (starts with `npm_`)
 
 2. **Add GitHub Secret:**
-   - Go to your repo: https://github.com/mrsimpson/vibe-feature-mcp/settings/secrets/actions
+   - Go to your repo: https://github.com/codemcp/workflows/settings/secrets/actions
    - Click "New repository secret"
    - Name: `NPM_TOKEN`
    - Value: Your npm token
@@ -103,8 +103,8 @@ If needed, you can manually trigger releases:
 ### Checking Status:
 
 - **npm package**: https://www.npmjs.com/package/@codemcp/workflows
-- **GitHub releases**: https://github.com/mrsimpson/vibe-feature-mcp/releases
-- **Actions logs**: https://github.com/mrsimpson/vibe-feature-mcp/actions
+- **GitHub releases**: https://github.com/codemcp/workflows/releases
+- **Actions logs**: https://github.com/codemcp/workflows/actions
 
 ## Version History