refactor!: rename to @codemcp/workflows with ade-workflows binary

.beads/issues.jsonl

@@ -67,6 +67,10 @@
 {"id":"responsible-vibe-13.4.1","title":"Code cleanup and review","description":"Review code for debug statements, TODOs, and cleanup any temporary code","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-02-22T00:27:14.118357+01:00","created_by":"Oliver Jägle","updated_at":"2026-02-22T00:27:41.595119+01:00","closed_at":"2026-02-22T00:27:41.595119+01:00","close_reason":"Closed","dependencies":[{"issue_id":"responsible-vibe-13.4.1","depends_on_id":"responsible-vibe-13.4","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"responsible-vibe-13.4.2","title":"Test the build process","description":"Run full build to ensure skill generation works correctly in the complete build process","status":"closed","priority":1,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-02-22T00:27:18.826688+01:00","created_by":"Oliver Jägle","updated_at":"2026-02-22T00:28:08.897095+01:00","closed_at":"2026-02-22T00:28:08.897095+01:00","close_reason":"Closed","dependencies":[{"issue_id":"responsible-vibe-13.4.2","depends_on_id":"responsible-vibe-13.4","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"responsible-vibe-13.4.3","title":"Update documentation","description":"Update plan file with final implementation details and ensure documentation is accurate","status":"closed","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-02-22T00:27:23.009363+01:00","created_by":"Oliver Jägle","updated_at":"2026-02-22T00:28:41.527524+01:00","closed_at":"2026-02-22T00:28:41.527524+01:00","close_reason":"Closed","dependencies":[{"issue_id":"responsible-vibe-13.4.3","depends_on_id":"responsible-vibe-13.4","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"responsible-vibe-14","title":"responsible-vibe: minor (development-plan-claude-permanent-workflow-instructions-5CkXj.md)","description":"Responsible vibe engineering session using minor workflow for responsible-vibe","status":"open","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-06T08:59:44.301985+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-06T08:59:44.301985+01:00"}
+{"id":"responsible-vibe-14.1","title":"Explore","description":"Understand the problem, analyze existing patterns, and design your approach. Consider the scope and impact of the change. **STEP 1: Analyze Requirements** - If  exists: Use it to understand the required changes - Otherwise: Document requirements in your task management system **STEP 2: Review Design Approach** - If  exists: Respect the design approach documented in  - Otherwise: Design your approach based on the problem analysis **STEP 3: Document Decisions** - Document your analysis and design decisions - Create tasks to guide implementation - Focus on analysis and design only - do not write any code yet","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-06T08:59:44.469588+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-06T08:59:44.469588+01:00","dependencies":[{"issue_id":"responsible-vibe-14.1","depends_on_id":"responsible-vibe-14","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"responsible-vibe-14.2","title":"Implement","description":"Write clean, focused code for the minor enhancement, test your changes, and prepare for commit. **STEP 1: Review Design and Requirements** - If  exists: Follow your design from  - Otherwise: Elaborate design options and present them to the user - If  exists: Ensure the relevant requirements from  are met - Otherwise: Ensure existing requirements are met based on your task context **STEP 2: Implement Changes** - Write clean, focused code for the minor enhancement - Test your changes to ensure they work correctly and don't break existing functionality **STEP 3: Prepare for Finalization** - Update task progress as needed - Prepare documentation and commit when ready","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-06T08:59:44.647558+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-06T08:59:44.647558+01:00","dependencies":[{"issue_id":"responsible-vibe-14.2","depends_on_id":"responsible-vibe-14","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"responsible-vibe-14.2","depends_on_id":"responsible-vibe-14.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"responsible-vibe-14.3","title":"Finalize","description":"Ensure code quality and documentation accuracy through systematic cleanup and review. **STEP 1: Code Cleanup** Systematically clean up development artifacts: - **Remove Debug Output**: Search for and remove all temporary debug output statements used during development.   Look for language-specific debug output methods (console logging, print statements, debug output functions).   Remove any debugging statements that were added for development purposes.  - **Review TODO/FIXME Comments**:   - Address each TODO/FIXME comment by either implementing the solution or documenting why it's deferred   - Remove completed TODOs   - Convert remaining TODOs to proper issue tracking if needed  - **Remove Debugging Code Blocks**:   - Remove temporary debugging code, test code blocks, and commented-out code   - Clean up any experimental code that's no longer needed   - Ensure proper error handling replaces temporary debug logging  **STEP 2: Documentation Review** Review and update documentation to reflect final implementation: - **Update Long-Term Memory Documents**: Based on what was actually implemented:   - If  exists: Update  if requirements changed during development   - If  exists: Update  if design details were refined or changed - **Compare Against Implementation**: Review documentation against actual implemented functionality - **Update Changed Sections**: Only modify documentation sections that have functional changes - **Remove Development Progress**: Remove references to development iterations, progress notes, and temporary decisions - **Focus on Final State**: Ensure documentation describes the final implemented state, not the development process - **Ask User to Review Document Updates** **STEP 3: Final Validation** - Run existing tests to ensure cleanup didn't break functionality - Verify documentation accuracy with a final review - Ensure minor enhancement is ready for delivery - Update task progress and mark completed work as you finalize the minor enhancement","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-06T08:59:44.842853+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-06T08:59:44.842853+01:00","dependencies":[{"issue_id":"responsible-vibe-14.3","depends_on_id":"responsible-vibe-14","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"responsible-vibe-14.3","depends_on_id":"responsible-vibe-14.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"responsible-vibe-2","title":"Responsible-Vibe Development: responsible-vibe","description":"Development session using epcc workflow for responsible-vibe","status":"open","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-01-18T02:16:58.742079+01:00","created_by":"Oliver Jägle","updated_at":"2026-01-18T02:16:58.742079+01:00"}
 {"id":"responsible-vibe-2.1","title":"Explore","description":"epcc workflow explore phase tasks","status":"closed","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-01-18T02:16:58.967896+01:00","created_by":"Oliver Jägle","updated_at":"2026-01-18T10:10:34.63295+01:00","closed_at":"2026-01-18T10:10:34.63295+01:00","close_reason":"Closed","dependencies":[{"issue_id":"responsible-vibe-2.1","depends_on_id":"responsible-vibe-2","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
 {"id":"responsible-vibe-2.1.1","title":"Examine current proceed_to_phase implementation","status":"closed","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-01-18T02:17:43.747866+01:00","created_by":"Oliver Jägle","updated_at":"2026-01-18T02:18:38.69261+01:00","closed_at":"2026-01-18T02:18:38.69261+01:00","close_reason":"Closed","dependencies":[{"issue_id":"responsible-vibe-2.1.1","depends_on_id":"responsible-vibe-2.1","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}

.beads/last-touched

@@ -1 +1 @@
-responsible-vibe-13.4.3
+responsible-vibe-14.3

.github/agents/Vibe.agent.md

@@ -1,5 +1,5 @@
 ---
-description: AI assistant that helps users develop software features using the responsible-vibe-mcp server.'
+description: AI assistant that helps users develop software features using the workflows server.'
 tools:
   [
     'edit',
@@ -8,7 +8,7 @@ tools:
     'new',
     'runCommands',
     'runTasks',
-    'responsible-vibe-mcp/*',
+    'workflows/*',
     'usages',
     'vscodeAPI',
     'problems',
@@ -22,7 +22,7 @@ tools:
   ]
 ---
 
-You are an AI assistant that helps users develop software features using the responsible-vibe-mcp server.
+You are an AI assistant that helps users develop software features using the workflows server.
 
 IMPORTANT: Call whats_next() after each user message to get phase-specific instructions and maintain the development workflow.
 

.github/workflows/build-cli.yml

@@ -26,7 +26,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-          version: 9.15.9
+          version: 10.32.1
 
       - name: Setup Node.js
         uses: actions/setup-node@v6

.github/workflows/deploy-pages.yml

@@ -28,7 +28,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-          version: 9.15.9
+          version: 10.32.1
 
       - name: Setup Node.js
         uses: actions/setup-node@v6

.github/workflows/pr.yml

@@ -14,7 +14,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-          version: 9.15.9
+          version: 10.32.1
 
       - name: Setup Node.js
         uses: actions/setup-node@v6
@@ -52,7 +52,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-          version: 9.15.9
+          version: 10.32.1
 
       - name: Setup Node.js ${{ matrix.node-version }}
         uses: actions/setup-node@v6

.github/workflows/release.yml

@@ -37,7 +37,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-          version: 9.15.9
+          version: 10.32.1
 
       - name: Setup Node.js
         uses: actions/setup-node@v6
@@ -93,7 +93,7 @@ jobs:
       - name: Setup pnpm
         uses: pnpm/action-setup@v4
         with:
-          version: 9.15.9
+          version: 10.32.1
 
       - name: Setup Node.js
         uses: actions/setup-node@v6

.gitignore

@@ -139,3 +139,5 @@ dist
 # Mac
 .DS_Store
 **/.DS_Store
+packages/mcp-server/resources
+packages/cli/resources

.vibe/beads-state-external-project-AXJv9y-default-p423k1.json

@@ -0,0 +1,24 @@
+{
+  "conversationId": "external-project-AXJv9y-default-p423k1",
+  "projectPath": "/Users/oliverjaegle/projects/privat/mcp-server/responsible-vibe",
+  "epicId": "external-project-AXJv9y-1",
+  "phaseTasks": [
+    {
+      "phaseId": "explore",
+      "phaseName": "Explore",
+      "taskId": "external-project-AXJv9y-1.1"
+    },
+    {
+      "phaseId": "implement",
+      "phaseName": "Implement",
+      "taskId": "external-project-AXJv9y-1.2"
+    },
+    {
+      "phaseId": "finalize",
+      "phaseName": "Finalize",
+      "taskId": "external-project-AXJv9y-1.3"
+    }
+  ],
+  "createdAt": "2026-03-06T07:59:43.483Z",
+  "updatedAt": "2026-03-06T07:59:43.483Z"
+}

.vibe/beads-state-responsible-vibe-claude-permanent-workflow-instructions-5CkXj-p423k1.json

@@ -0,0 +1,24 @@
+{
+  "conversationId": "responsible-vibe-claude-permanent-workflow-instructions-5CkXj-p423k1",
+  "projectPath": "/Users/oliverjaegle/projects/privat/mcp-server/responsible-vibe",
+  "epicId": "responsible-vibe-14",
+  "phaseTasks": [
+    {
+      "phaseId": "explore",
+      "phaseName": "Explore",
+      "taskId": "responsible-vibe-14.1"
+    },
+    {
+      "phaseId": "implement",
+      "phaseName": "Implement",
+      "taskId": "responsible-vibe-14.2"
+    },
+    {
+      "phaseId": "finalize",
+      "phaseName": "Finalize",
+      "taskId": "responsible-vibe-14.3"
+    }
+  ],
+  "createdAt": "2026-03-06T07:59:45.079Z",
+  "updatedAt": "2026-03-06T07:59:45.079Z"
+}

.vibe/beads-state-test-direct-aCxxFE-default-p423k1.json

@@ -0,0 +1,24 @@
+{
+  "conversationId": "test-direct-aCxxFE-default-p423k1",
+  "projectPath": "/Users/oliverjaegle/projects/privat/mcp-server/responsible-vibe",
+  "epicId": "test-direct-aCxxFE-1",
+  "phaseTasks": [
+    {
+      "phaseId": "explore",
+      "phaseName": "Explore",
+      "taskId": "test-direct-aCxxFE-1.1"
+    },
+    {
+      "phaseId": "implement",
+      "phaseName": "Implement",
+      "taskId": "test-direct-aCxxFE-1.2"
+    },
+    {
+      "phaseId": "finalize",
+      "phaseName": "Finalize",
+      "taskId": "test-direct-aCxxFE-1.3"
+    }
+  ],
+  "createdAt": "2026-03-06T07:59:42.142Z",
+  "updatedAt": "2026-03-06T07:59:42.142Z"
+}

.vibe/beads-state-test-normalize-Ay1iWh-default-p423k1.json

@@ -0,0 +1,24 @@
+{
+  "conversationId": "test-normalize-Ay1iWh-default-p423k1",
+  "projectPath": "/Users/oliverjaegle/projects/privat/mcp-server/responsible-vibe",
+  "epicId": "test-normalize-Ay1iWh-1",
+  "phaseTasks": [
+    {
+      "phaseId": "explore",
+      "phaseName": "Explore",
+      "taskId": "test-normalize-Ay1iWh-1.1"
+    },
+    {
+      "phaseId": "implement",
+      "phaseName": "Implement",
+      "taskId": "test-normalize-Ay1iWh-1.2"
+    },
+    {
+      "phaseId": "finalize",
+      "phaseName": "Finalize",
+      "taskId": "test-normalize-Ay1iWh-1.3"
+    }
+  ],
+  "createdAt": "2026-03-06T07:59:40.837Z",
+  "updatedAt": "2026-03-06T07:59:40.837Z"
+}

.vibe/development-plan-claude-permanent-workflow-instructions-5CkXj.md

@@ -0,0 +1,34 @@
+# Development Plan: responsible-vibe (claude/permanent-workflow-instructions-5CkXj branch)
+
+*Generated on 2026-03-06 by Vibe Feature MCP*
+*Workflow: [minor](https://mrsimpson.github.io/responsible-vibe-mcp/workflows/minor)*
+
+## Goal
+*Define what you're building or fixing - this will be updated as requirements are gathered*
+
+## Explore
+<!-- beads-phase-id: responsible-vibe-14.1 -->
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Implement
+<!-- beads-phase-id: responsible-vibe-14.2 -->
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Finalize
+<!-- beads-phase-id: responsible-vibe-14.3 -->
+### Tasks
+
+*Tasks managed via `bd` CLI*
+
+## Key Decisions
+*Important decisions will be documented here as they are made*
+
+## Notes
+*Additional context and observations*
+
+---
+*This plan is maintained by the LLM and uses beads CLI for task management. Tool responses provide guidance on which bd commands to use for task management.*

.windsurf/rules/vibe.md

@@ -2,9 +2,9 @@
 trigger: always_on
 ---
 
-You are an AI assistant that helps users develop software features through a structured development process guided by the responsible-vibe-mcp server.
+You are an AI assistant that helps users develop software features through a structured development process guided by the workflows server.
 
-IMPORTANT: Always follow these instructions when working with responsible-vibe-mcp!
+IMPORTANT: Always follow these instructions when working with the workflows server!
 
 Use the start_development() whenever you are starting a conversation! Chose the workflow that fits the user's request.
 
@@ -13,7 +13,7 @@ Use the start_development() whenever you are starting a conversation! Chose the
 Each tool call will return a JSON formatted response with an "instructions" field in it. Follow these instructions immediately after you received them.
 
 1. **Call whats_next() after each user interaction** to get phase-specific instructions
-2. **Follow the instructions** provided by responsible-vibe-mcp exactly
+2. **Follow the instructions** provided by the workflows server exactly
 3. **Update the plan file** as directed to maintain project memory
 4. **Mark completed tasks** with [x] when instructed
 5. **Provide conversation context** in each whats_next() call
@@ -69,10 +69,10 @@ proceed_to_phase({
 
 ## Conversation Context Guidelines
 
-Since responsible-vibe-mcp operates statelessly, provide:
+Since the workflows server operates statelessly, provide:
 
 - **conversation_summary**: What the user wants, key decisions, progress
 - **recent_messages**: Last 3-5 relevant exchanges
 - **context**: Current situation and what you're trying to determine
 
-Remember: responsible-vibe-mcp guides the development process but relies on you to provide conversation context and follow its instructions precisely.
+Remember: The workflows server guides the development process but relies on you to provide conversation context and follow its instructions precisely.

CLAUDE.md

@@ -1,7 +1,7 @@
 You are an AI assistant that helps users develop software features.
-You do this by following a structured development process guided by the responsible-vibe-mcp server.
+You do this by following a structured development process guided by the workflows server.
 
-IMPORTANT: Use responsible-vibe-mcp tools after each user message!
+IMPORTANT: Use workflows tools after each user message!
 
 Use the start_development() to start a new development.
 
@@ -10,14 +10,14 @@ Use the start_development() to start a new development.
 Each tool call will return a JSON formatted response with an "instructions" field in it. Follow these instructions immediately after you received them.
 
 1. **Call whats_next() after each user interaction** to get phase-specific instructions
-2. **Follow the instructions** provided by responsible-vibe-mcp exactly
+2. **Follow the instructions** provided by the workflows server exactly
 3. **Update the plan file** as directed to maintain project memory
 4. **Mark completed tasks** with [x] when instructed
 5. **Provide conversation context** in each whats_next() call
 
 ## Development Workflow
 
-The responsible-vibe-mcp server will guide you through development phases specific to the chosen workflow. The available phases and their descriptions will be provided in the tool responses from start_development() and resume_workflow().
+The workflows server will guide you through development phases specific to the chosen workflow. The available phases and their descriptions will be provided in the tool responses from start_development() and resume_workflow().
 
 ## Using whats_next()
 
@@ -63,10 +63,10 @@ proceed_to_phase({
 
 ## Conversation Context Guidelines
 
-Since responsible-vibe-mcp operates statelessly, provide:
+Since the workflows server operates statelessly, provide:
 
 - **conversation_summary**: What the user wants, key decisions, progress
 - **recent_messages**: Last 3-5 relevant exchanges
 - **context**: Current situation and what you're trying to determine
 
-Remember: responsible-vibe-mcp guides the development process but relies on you to provide conversation context and follow its instructions precisely.
+Remember: The workflows server guides the development process but relies on you to provide conversation context and follow its instructions precisely.