npm - @codemcp/workflows - Versions diffs - 5.3.0 → 6.0.1 - Mend

@codemcp/workflows 5.3.0 → 6.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (451) hide show

package/packages/docs/.vitepress/dist/workflows/sdd-feature.html ADDED Viewed

@@ -0,0 +1,26 @@
+<!DOCTYPE html>
+<html lang="en-US" dir="ltr">
+  <head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width,initial-scale=1">
+    <title>Responsible Vibe MCP</title>
+    <meta name="description" content="Model Context Protocol server for intelligent conversation state management and development guidance">
+    <meta name="generator" content="VitePress v1.6.4">
+    <link rel="preload stylesheet" href="/responsible-vibe-mcp/assets/style.CAgdBzOq.css" as="style">
+    <link rel="preload stylesheet" href="/responsible-vibe-mcp/vp-icons.css" as="style">
+    <script type="module" src="/responsible-vibe-mcp/assets/app.Dz3lZH3M.js"></script>
+    <link rel="preload" href="/responsible-vibe-mcp/assets/inter-roman-latin.Di8DUHzh.woff2" as="font" type="font/woff2" crossorigin="">
+    <link rel="modulepreload" href="/responsible-vibe-mcp/assets/chunks/theme.q5Ewb3F1.js">
+    <link rel="modulepreload" href="/responsible-vibe-mcp/assets/chunks/framework.DZS7lpav.js">
+    <link rel="modulepreload" href="/responsible-vibe-mcp/assets/workflows_sdd-feature.md.Ce3-H_g3.lean.js">
+    <link rel="icon" href="/responsible-vibe-mcp/favicon.ico">
+    <script id="check-dark-mode">(()=>{const e=localStorage.getItem("vitepress-theme-appearance")||"auto",a=window.matchMedia("(prefers-color-scheme: dark)").matches;(!e||e==="auto"?a:e==="dark")&&document.documentElement.classList.add("dark")})();</script>
+    <script id="check-mac-os">document.documentElement.classList.toggle("mac",/Mac|iPhone|iPod|iPad/i.test(navigator.platform));</script>
+  </head>
+  <body>
+    <div id="app"><div style="position:relative;" data-v-c1df4d5c><div><div id="workflow-visualizer-app" class="" data-v-b5ec7de4><!----><main class="app-main"><div class="diagram-container"><div id="diagram-canvas" class="diagram-canvas"><div class="loading-message">Loading workflow...</div></div></div><aside class="side-panel"><div class="side-panel-header"><h2>Details</h2></div><div class="side-panel-content"><div class="empty-state"> Click on a state or transition to see details </div></div></aside></main><div id="error-container" class="error-container hidden"><div class="error-message"><span class="error-text"></span><button class="error-close">×</button></div></div></div></div></div></div>
+    <script>window.__VP_HASH_MAP__=JSON.parse("{\"dev_architecture.md\":\"da_vFDwM\",\"dev_development.md\":\"DWl9cccE\",\"dev_logging.md\":\"BebvbW7z\",\"dev_publishing.md\":\"CQqbiIOF\",\"index.md\":\"D6ROLohf\",\"user_advanced-engineering.md\":\"MkETYNtq\",\"user_agent-setup.md\":\"B54OLL2H\",\"user_beads-integration.md\":\"BzdR5Fif\",\"user_crowd-mcp-integration.md\":\"C15kSdIJ\",\"user_custom-workflows.md\":\"Cz4IYCXa\",\"user_git-commit-feature.md\":\"UcTvDR-O\",\"user_how-it-works.md\":\"DiOXNgaL\",\"user_long-term-memory.md\":\"DZh0tjNa\",\"user_packaged-workflows.md\":\"s1HT89ZU\",\"user_tutorial.md\":\"Dmj8zLB2\",\"user_workflow-selection.md\":\"CrPGw9Hr\",\"workflows.md\":\"Bm5sGt3u\",\"workflows_adr.md\":\"DEaXkbRp\",\"workflows_big-bang-conversion.md\":\"BA5R1LxZ\",\"workflows_boundary-testing.md\":\"DBcYnMhx\",\"workflows_bugfix.md\":\"CZRCL0Hp\",\"workflows_business-analysis.md\":\"fGLml8Hw\",\"workflows_c4-analysis.md\":\"Dnssqzuf\",\"workflows_epcc.md\":\"M6DnIhpp\",\"workflows_game-beginner.md\":\"CNxzWLtd\",\"workflows_greenfield.md\":\"vx_g-WOe\",\"workflows_minor.md\":\"DdnfwMf4\",\"workflows_posts.md\":\"SOldXvq7\",\"workflows_sdd-bugfix-crowd.md\":\"-lSf42gJ\",\"workflows_sdd-bugfix.md\":\"oRAsEVbc\",\"workflows_sdd-feature-crowd.md\":\"DAtnfCAd\",\"workflows_sdd-feature.md\":\"Ce3-H_g3\",\"workflows_sdd-greenfield-crowd.md\":\"8DUvcmLe\",\"workflows_sdd-greenfield.md\":\"eEN6U0J4\",\"workflows_slides.md\":\"Cqt-19_1\",\"workflows_tdd.md\":\"BjVC69tu\",\"workflows_waterfall.md\":\"CL6jTZP9\"}");window.__VP_SITE_DATA__=JSON.parse("{\"lang\":\"en-US\",\"dir\":\"ltr\",\"title\":\"Responsible Vibe MCP\",\"description\":\"Model Context Protocol server for intelligent conversation state management and development guidance\",\"base\":\"/responsible-vibe-mcp/\",\"head\":[],\"router\":{\"prefetchLinks\":true},\"appearance\":true,\"themeConfig\":{\"nav\":[{\"text\":\"Documentation\",\"link\":\"/\"},{\"text\":\"Workflows\",\"link\":\"/workflows\"},{\"text\":\"Github\",\"link\":\"https://github.com/mrsimpson/responsible-vibe-mcp\"}],\"sidebar\":[{\"text\":\"User Guide\",\"items\":[{\"text\":\"Overview\",\"link\":\"/\"},{\"text\":\"How It Works\",\"link\":\"/user/how-it-works\"},{\"text\":\"Agent Setup\",\"link\":\"/user/agent-setup\"},{\"text\":\"Vibe Engineering\",\"link\":\"/user/advanced-engineering\"},{\"text\":\"Long-Term Memory\",\"link\":\"/user/long-term-memory\"},{\"text\":\"Beads-Integration\",\"link\":\"/user/beads-integration\"},{\"text\":\"Tutorial\",\"link\":\"/user/tutorial\"}]},{\"text\":\"Workflows\",\"items\":[{\"text\":\"Workflow-Selection\",\"link\":\"/user/workflow-selection\"},{\"text\":\"Packaged Workflows\",\"link\":\"/user/packaged-workflows\"},{\"text\":\"Custom Workflows\",\"link\":\"/user/custom-workflows\"},{\"text\":\"Explore All Workflows\",\"link\":\"/workflows\"},{\"text\":\"Crowd MCP Integration\",\"link\":\"/user/crowd-mcp-integration\"}]}]},\"locales\":{},\"scrollOffset\":134,\"cleanUrls\":false}");</script>
+  </body>
+</html>

package/packages/docs/.vitepress/dist/workflows/sdd-feature.yaml ADDED Viewed

@@ -0,0 +1,471 @@
+# yaml-language-server: $schema=../state-machine-schema.json
+---
+name: 'sdd-feature'
+description: 'Unified specification-driven feature development and enhancement: Analyze → Specify → Clarify → Plan → Tasks → Implement'
+initial_state: 'analyze'
+# Enhanced metadata for better discoverability
+metadata:
+  domain: 'sdd'
+  complexity: 'medium'
+  bestFor:
+    - 'Adding new features'
+    - 'Enhancing existing features'
+    - 'Iterative development'
+    - 'Feature improvements'
+  useCases:
+    - 'Add new functionality to existing project'
+    - 'Improve existing feature capabilities'
+    - 'Extend system functionality'
+  examples:
+    - 'Add user profile management'
+    - 'Enhance search functionality'
+    - 'Improve reporting capabilities'
+# States with default instructions and transitions
+states:
+  analyze:
+    description: 'Analyze current state and requirements (optional for new features)'
+    default_instructions: |
+      Analyze the current state to understand the context for this feature development.
+      **Analysis Tasks:**
+      **For New Features**: This phase can be brief. Focus on understanding:
+      - How this feature fits into the existing system
+      - Integration points with current functionality
+      - Existing patterns and conventions to follow
+      **For Enhancements**: Conduct thorough analysis:
+      - Current implementation and its limitations
+      - User pain points and feedback
+      - Performance or usability issues
+      - Technical debt that should be addressed
+      **Context Gathering**:
+      - Review existing codebase and architecture
+      - Understand current user workflows
+      - Identify constraints and dependencies
+      - Document assumptions about the current state
+      **Output**: Create `$VIBE_DIR/specs/$BRANCH_NAME/current-state-analysis.md` documenting your findings. For simple new features, this can be brief. For enhancements, be comprehensive.
+      **Skip Option**: If this is a straightforward new feature with clear requirements, you can proceed directly to specification.
+    transitions:
+      - trigger: 'analysis_complete'
+        to: 'specify'
+        transition_reason: 'Analysis completed, ready to create feature specification'
+      - trigger: 'skip_analysis'
+        to: 'specify'
+        instructions: >
+          Skipping analysis phase for straightforward new feature. Proceed directly to specification
+          creation using the provided requirements.
+        transition_reason: 'Analysis not needed for this feature, proceeding to specification'
+  specify:
+    description: 'Create feature specification'
+    default_instructions: |
+      Create the feature specification that will guide all development decisions.
+      **Specification Process:**
+      **STEP 1: Parse Requirements**
+      - Extract key concepts from the user's description
+      - Identify: actors, actions, data, constraints
+      - Consider existing system context (from analysis if performed)
+      - Focus on WHAT users need and WHY, not HOW to implement
+      **STEP 2: Interactive Requirements Gathering**
+      Ask clarifying questions about:
+      - **Integration Points**: How should this integrate with existing features?
+      - **User Impact**: Which existing users will be affected?
+      - **Data Dependencies**: What existing data does this feature need?
+      - **Performance**: Any specific performance requirements for this feature?
+      - **Compatibility**: Any backward compatibility concerns?
+      **STEP 3: Handle Ambiguities Systematically**
+      - Make informed guesses based on context, existing patterns, and industry standards
+      - Only use `[NEEDS CLARIFICATION: specific question]` for critical decisions that:
+        - Significantly impact feature scope or user experience
+        - Have multiple reasonable interpretations with different implications
+        - Lack any reasonable default
+      - **LIMIT: Maximum 3** `[NEEDS CLARIFICATION]` markers total
+      - Prioritize: scope > security/privacy > user experience > technical details
+      **STEP 4: Quality Validation**
+      - Ensure no implementation details (languages, frameworks, APIs)
+      - Ensure written for non-technical stakeholders
+      - Verify all requirements are testable
+      - Ensure success criteria are measurable and technology-agnostic
+      - Consider existing system constraints
+      Create `$VIBE_DIR/specs/$BRANCH_NAME/spec.md` using the template provided below.
+    additional_instructions: |
+      **Feature Specification Template:**
+      Use this template to create your `spec.md` file:
+      ```markdown
+      # Feature Specification: [FEATURE NAME]
+      **Created**: [DATE]
+      **Status**: Draft
+      ## User Scenarios & Testing *(mandatory)*
+      ### User Story 1 - [Brief Title] (Priority: P1)
+      [Describe this user journey in plain language]
+      **Why this priority**: [Explain the value and why it has this priority level]
+      **Independent Test**: [Describe how this can be tested independently]
+      **Acceptance Scenarios**:
+      1. **Given** [initial state], **When** [action], **Then** [expected outcome]
+      2. **Given** [initial state], **When** [action], **Then** [expected outcome]
+      ---
+      ### User Story 2 - [Brief Title] (Priority: P2)
+      [Describe this user journey in plain language]
+      **Why this priority**: [Explain the value and why it has this priority level]
+      **Independent Test**: [Describe how this can be tested independently]
+      **Acceptance Scenarios**:
+      1. **Given** [initial state], **When** [action], **Then** [expected outcome]
+      ---
+      [Add more user stories as needed, each with an assigned priority]
+      ### Edge Cases
+      - What happens when [boundary condition]?
+      - How does system handle [error scenario]?
+      ## Requirements *(mandatory)*
+      ### Functional Requirements
+      - **FR-001**: System MUST [specific capability]
+      - **FR-002**: System MUST [specific capability]
+      - **FR-003**: Users MUST be able to [key interaction]
+      - **FR-004**: System MUST [data requirement]
+      - **FR-005**: System MUST [behavior]
+      ### Key Entities *(include if feature involves data)*
+      - **[Entity 1]**: [What it represents, key attributes without implementation]
+      - **[Entity 2]**: [What it represents, relationships to other entities]
+      ## Success Criteria *(mandatory)*
+      ### Measurable Outcomes
+      - **SC-001**: [Measurable metric, e.g., "Users can complete task in under 2 minutes"]
+      - **SC-002**: [Measurable metric, e.g., "System handles 1000 concurrent users"]
+      - **SC-003**: [User satisfaction metric, e.g., "90% task completion rate"]
+      - **SC-004**: [Business metric, e.g., "Reduce support tickets by 50%"]
+      ## Integration Points
+      - [How this connects with existing functionality]
+      - [Dependencies on existing components]
+      ## Assumptions
+      - [Document any assumptions made during specification]
+      - [Include reasonable defaults chosen]
+      ## Dependencies
+      - [External systems or prerequisites]
+      - [Integration requirements]
+      ```
+      Fill in all sections with specific details for your feature. Consider how this integrates with the existing system.
+    transitions:
+      - trigger: 'specification_complete'
+        to: 'clarify'
+        transition_reason: 'Feature specification completed, ready for clarification review'
+      - trigger: 'needs_clarification'
+        to: 'specify'
+        instructions: >
+          Specification has unresolved clarifications. Present structured questions to the user,
+          wait for their responses, then update the specification accordingly.
+        transition_reason: 'Specification needs user clarification before proceeding'
+  clarify:
+    description: 'Review and clarify specification details'
+    default_instructions: |
+      Review the specification for completeness and clarity.
+      **Clarification Process:**
+      **STEP 1: Specification Review**
+      - Check for any remaining `[NEEDS CLARIFICATION]` markers
+      - Verify all functional requirements are testable
+      - Ensure success criteria are measurable
+      - Validate user scenarios are complete
+      **STEP 2: Handle Remaining Clarifications**
+      If `[NEEDS CLARIFICATION]` markers exist:
+      - Extract all markers from the spec
+      - For each clarification (max 3), present options in structured format:
+        ```
+        ## Question [N]: [Topic]
+        **Context**: [Quote relevant spec section]
+        **What we need to know**: [Specific question]
+        **Suggested Answers**:
+        | Option | Answer | Implications |
+        |--------|--------|--------------|
+        | A      | [First option] | [Impact on feature] |
+        | B      | [Second option] | [Impact on feature] |
+        | C      | [Third option] | [Impact on feature] |
+        ```
+      - Wait for user responses
+      - Update specification with chosen answers
+      **STEP 3: Final Validation**
+      - Ensure no implementation details leaked in
+      - Verify requirements align with existing system
+      - Confirm specification is ready for planning
+      **Output**: Updated `$VIBE_DIR/specs/$BRANCH_NAME/spec.md` with all clarifications resolved and ready for implementation planning.
+    transitions:
+      - trigger: 'clarification_complete'
+        to: 'plan'
+        transition_reason: 'All clarifications resolved, specification ready for implementation planning'
+      - trigger: 'needs_user_input'
+        to: 'clarify'
+        instructions: >
+          Waiting for user responses to clarification questions. Present the questions clearly
+          and wait for user input before proceeding.
+        transition_reason: 'Waiting for user input on clarification questions'
+  plan:
+    description: 'Generate implementation plan with constitutional compliance'
+    default_instructions: |
+      Create the implementation plan, considering existing system architecture.
+      **Planning Process:**
+      **STEP 1: Load Context**
+      - Read the feature specification (`$VIBE_DIR/specs/$BRANCH_NAME/spec.md`)
+      - Read analysis findings (`$VIBE_DIR/specs/$BRANCH_NAME/current-state-analysis.md` if exists)
+      - Review existing project constitution or architectural principles
+      - Understand current system architecture and patterns
+      **STEP 2: Interactive Integration Planning**
+      Ask the user about:
+      - **Technology Consistency**: Should this use the same tech stack as existing features?
+      - **Architecture Alignment**: How should this fit into the current architecture?
+      - **Database Changes**: Any new data models or schema changes needed?
+      **STEP 3: Technical Context Analysis**
+      - Identify how this feature integrates with existing system
+      - Map dependencies and integration points
+      - Choose appropriate technology stack (consistent with existing)
+      - Mark unknowns as "NEEDS CLARIFICATION" for research
+      **STEP 4: Constitutional/Architectural Compliance**
+      - Evaluate approach against existing architectural principles
+      - Ensure consistency with current patterns and conventions
+      - Identify any violations and justify or resolve them
+      **STEP 5: Phase 0 - Research & Decisions**
+      - For each unknown → research task
+      - For each integration point → compatibility analysis
+      - Generate `$VIBE_DIR/specs/$BRANCH_NAME/technology-research.md` with decisions and rationale
+      **STEP 6: Phase 1 - High-Level Integration Design**
+      - Document how this feature integrates with existing architecture
+      - Identify integration points and dependencies
+      - Plan compatibility and migration requirements
+      **STEP 7: Integration Strategy**
+      - Plan how to integrate with existing codebase
+      - Identify migration or compatibility requirements
+      - Document rollout strategy if needed
+      Create `$VIBE_DIR/specs/$BRANCH_NAME/plan.md` with complete implementation strategy that respects existing system architecture.
+    transitions:
+      - trigger: 'plan_complete'
+        to: 'tasks'
+        transition_reason: 'Implementation plan completed, ready to generate actionable tasks'
+      - trigger: 'architectural_conflict'
+        to: 'plan'
+        instructions: >
+          Implementation plan conflicts with existing architecture or principles.
+          Review and revise the approach to ensure proper integration.
+        transition_reason: 'Plan conflicts with existing architecture, needs revision'
+  tasks:
+    description: 'Generate actionable, dependency-ordered tasks organized by user stories'
+    default_instructions: |
+      Generate actionable tasks organized by user stories for independent implementation.
+      **Task Generation Process:**
+      **STEP 1: Load Design Documents**
+      - **Required**: `$VIBE_DIR/specs/$BRANCH_NAME/plan.md`, `$VIBE_DIR/specs/$BRANCH_NAME/spec.md` (user stories with priorities)
+      - **Optional**: `$VIBE_DIR/specs/$BRANCH_NAME/technology-research.md`, `$VIBE_DIR/specs/$BRANCH_NAME/current-state-analysis.md`
+      **STEP 2: Extract User Stories**
+      Load `$VIBE_DIR/specs/$BRANCH_NAME/spec.md` and extract user stories with priorities (P1, P2, P3...)
+      **STEP 3: Generate Tasks Organized by User Story**
+      - **Setup Phase**: Integration setup and shared infrastructure
+      - **Foundational Phase**: Prerequisites for this feature (database changes, etc.)
+      - **User Story Phases** (P1, P2, P3...): One phase per story in priority order
+        - Group all tasks needed to complete JUST that story
+        - Include models, services, endpoints, UI components specific to that story
+        - Consider integration with existing components
+        - Mark parallelizable tasks with `[P]`
+        - Each story should be independently testable
+      **STEP 4: Integration Tasks**
+      - Tasks for connecting with existing system
+      - Migration or compatibility tasks if needed
+      - Testing integration points
+      **STEP 5: Apply Task Rules**
+      - Different files/components = mark `[P]` for parallel execution
+      - Same file = sequential (no `[P]`)
+      - Number tasks sequentially (T001, T002...)
+      - Ensure each task is specific enough for LLM to complete
+      **STEP 6: Rollout Strategy**
+      Plan for gradual feature rollout if applicable
+    additional_instructions: |
+      **Document Creation Instructions:**
+      Create these documents in the following order:
+      **1. Data Model** (`$VIBE_DIR/specs/$BRANCH_NAME/data-model.md`)
+      - Extract entities from the specification
+      - Design data models that integrate with existing system
+      - Document relationships with existing entities
+      - Include migration requirements if needed
+      **2. API Contracts** (`$VIBE_DIR/specs/$BRANCH_NAME/contracts/`)
+      - Design API contracts that integrate with existing system
+      - Ensure compatibility with existing data models and APIs
+      - Include versioning strategy if needed
+      - Document integration points
+      **3. Development Setup** (`$VIBE_DIR/specs/$BRANCH_NAME/quickstart.md`)
+      - Feature development setup instructions
+      - Integration testing setup
+      - Local development environment for this feature
+      - Testing instructions specific to this feature
+      **4. Task Breakdown** (`$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`)
+      Use this structure for the tasks file:
+      ```markdown
+      # Feature Implementation Tasks: [FEATURE NAME]
+      ## Setup Phase
+      - T001: [Integration setup] [P]
+      - T002: [Shared infrastructure]
+      ## Foundational Phase
+      - T003: [Database changes for feature]
+      - T004: [Dependencies setup] [P]
+      ## User Story 1 (P1): [Story Title]
+      **Goal**: [What this story achieves]
+      **Independent Test**: [How to test this story alone]
+      **Integration Points**: [How this connects to existing system]
+      - T005: [Model for this story] [P]
+      - T006: [Service integration] [P]
+      - T007: [API endpoint with existing system]
+      - T008: [UI component integration] [P]
+      ## User Story 2 (P2): [Story Title]
+      [Continue pattern...]
+      ## Integration Tasks
+      - T0XX: [Connect with existing system]
+      - T0XX: [Migration tasks if needed]
+      - T0XX: [Integration testing]
+      ## Dependencies
+      - Story 1 → Story 2 (if applicable)
+      - Integration dependencies with existing features
+      ## Rollout Strategy
+      [Plan for gradual feature rollout if applicable]
+      ```
+    transitions:
+      - trigger: 'tasks_generated'
+        to: 'implement'
+        transition_reason: 'Tasks generated and organized, ready for implementation'
+  implement:
+    description: 'Execute implementation following the task breakdown'
+    default_instructions: |
+      Execute the feature implementation by following the tasks defined in `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`, ensuring proper integration with the existing system.
+      **Implementation Guidelines:**
+      - Follow task order respecting dependencies and integration requirements
+      - Ensure new code follows existing patterns and conventions
+      - Complete one user story at a time for incremental delivery
+      - Verify each user story meets success criteria from specification
+      - Test both new functionality and integration with existing features
+      - Update existing documentation as needed
+      **Integration Considerations:**
+      - Follow existing code style and patterns
+      - Respect current architectural decisions
+      - Test integration points thoroughly
+      - Consider backward compatibility
+      - Update relevant configuration or setup
+      **Progress Tracking:**
+      - Mark completed tasks with `[x]` in `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`
+      - Document any integration challenges or decisions
+      - Update specification if requirements evolve
+      Focus on delivering working, tested increments that integrate seamlessly with the existing system.
+    transitions:
+      - trigger: 'implementation_blocked'
+        to: 'plan'
+        instructions: >
+          Implementation is blocked by integration issues or technical challenges.
+          Return to planning to resolve the blockers and update the approach.
+        transition_reason: 'Implementation blocked, need to revise plan'
+      - trigger: 'integration_issues'
+        to: 'analyze'
+        instructions: >
+          Significant integration issues discovered that require better understanding
+          of the existing system. Return to analysis to gather more context.
+        transition_reason: 'Integration issues require deeper system analysis'
+# Global transitions available from any state
+global_transitions:
+  - trigger: 'abandon_feature'
+    to: 'analyze'
+    instructions: >
+      Feature development abandoned. If you want to restart, you'll begin again with
+      analyzing the requirements and current state.
+    transition_reason: 'Feature abandoned, restart from beginning'

package/packages/docs/.vitepress/dist/workflows/sdd-greenfield-crowd.html ADDED Viewed

@@ -0,0 +1,26 @@
+<!DOCTYPE html>
+<html lang="en-US" dir="ltr">
+  <head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width,initial-scale=1">
+    <title>Responsible Vibe MCP</title>
+    <meta name="description" content="Model Context Protocol server for intelligent conversation state management and development guidance">
+    <meta name="generator" content="VitePress v1.6.4">
+    <link rel="preload stylesheet" href="/responsible-vibe-mcp/assets/style.CAgdBzOq.css" as="style">
+    <link rel="preload stylesheet" href="/responsible-vibe-mcp/vp-icons.css" as="style">
+    <script type="module" src="/responsible-vibe-mcp/assets/app.Dz3lZH3M.js"></script>
+    <link rel="preload" href="/responsible-vibe-mcp/assets/inter-roman-latin.Di8DUHzh.woff2" as="font" type="font/woff2" crossorigin="">
+    <link rel="modulepreload" href="/responsible-vibe-mcp/assets/chunks/theme.q5Ewb3F1.js">
+    <link rel="modulepreload" href="/responsible-vibe-mcp/assets/chunks/framework.DZS7lpav.js">
+    <link rel="modulepreload" href="/responsible-vibe-mcp/assets/workflows_sdd-greenfield-crowd.md.8DUvcmLe.lean.js">
+    <link rel="icon" href="/responsible-vibe-mcp/favicon.ico">
+    <script id="check-dark-mode">(()=>{const e=localStorage.getItem("vitepress-theme-appearance")||"auto",a=window.matchMedia("(prefers-color-scheme: dark)").matches;(!e||e==="auto"?a:e==="dark")&&document.documentElement.classList.add("dark")})();</script>
+    <script id="check-mac-os">document.documentElement.classList.toggle("mac",/Mac|iPhone|iPod|iPad/i.test(navigator.platform));</script>
+  </head>
+  <body>
+    <div id="app"><div style="position:relative;" data-v-c1df4d5c><div><div id="workflow-visualizer-app" class="" data-v-b5ec7de4><!----><main class="app-main"><div class="diagram-container"><div id="diagram-canvas" class="diagram-canvas"><div class="loading-message">Loading workflow...</div></div></div><aside class="side-panel"><div class="side-panel-header"><h2>Details</h2></div><div class="side-panel-content"><div class="empty-state"> Click on a state or transition to see details </div></div></aside></main><div id="error-container" class="error-container hidden"><div class="error-message"><span class="error-text"></span><button class="error-close">×</button></div></div></div></div></div></div>
+    <script>window.__VP_HASH_MAP__=JSON.parse("{\"dev_architecture.md\":\"da_vFDwM\",\"dev_development.md\":\"DWl9cccE\",\"dev_logging.md\":\"BebvbW7z\",\"dev_publishing.md\":\"CQqbiIOF\",\"index.md\":\"D6ROLohf\",\"user_advanced-engineering.md\":\"MkETYNtq\",\"user_agent-setup.md\":\"B54OLL2H\",\"user_beads-integration.md\":\"BzdR5Fif\",\"user_crowd-mcp-integration.md\":\"C15kSdIJ\",\"user_custom-workflows.md\":\"Cz4IYCXa\",\"user_git-commit-feature.md\":\"UcTvDR-O\",\"user_how-it-works.md\":\"DiOXNgaL\",\"user_long-term-memory.md\":\"DZh0tjNa\",\"user_packaged-workflows.md\":\"s1HT89ZU\",\"user_tutorial.md\":\"Dmj8zLB2\",\"user_workflow-selection.md\":\"CrPGw9Hr\",\"workflows.md\":\"Bm5sGt3u\",\"workflows_adr.md\":\"DEaXkbRp\",\"workflows_big-bang-conversion.md\":\"BA5R1LxZ\",\"workflows_boundary-testing.md\":\"DBcYnMhx\",\"workflows_bugfix.md\":\"CZRCL0Hp\",\"workflows_business-analysis.md\":\"fGLml8Hw\",\"workflows_c4-analysis.md\":\"Dnssqzuf\",\"workflows_epcc.md\":\"M6DnIhpp\",\"workflows_game-beginner.md\":\"CNxzWLtd\",\"workflows_greenfield.md\":\"vx_g-WOe\",\"workflows_minor.md\":\"DdnfwMf4\",\"workflows_posts.md\":\"SOldXvq7\",\"workflows_sdd-bugfix-crowd.md\":\"-lSf42gJ\",\"workflows_sdd-bugfix.md\":\"oRAsEVbc\",\"workflows_sdd-feature-crowd.md\":\"DAtnfCAd\",\"workflows_sdd-feature.md\":\"Ce3-H_g3\",\"workflows_sdd-greenfield-crowd.md\":\"8DUvcmLe\",\"workflows_sdd-greenfield.md\":\"eEN6U0J4\",\"workflows_slides.md\":\"Cqt-19_1\",\"workflows_tdd.md\":\"BjVC69tu\",\"workflows_waterfall.md\":\"CL6jTZP9\"}");window.__VP_SITE_DATA__=JSON.parse("{\"lang\":\"en-US\",\"dir\":\"ltr\",\"title\":\"Responsible Vibe MCP\",\"description\":\"Model Context Protocol server for intelligent conversation state management and development guidance\",\"base\":\"/responsible-vibe-mcp/\",\"head\":[],\"router\":{\"prefetchLinks\":true},\"appearance\":true,\"themeConfig\":{\"nav\":[{\"text\":\"Documentation\",\"link\":\"/\"},{\"text\":\"Workflows\",\"link\":\"/workflows\"},{\"text\":\"Github\",\"link\":\"https://github.com/mrsimpson/responsible-vibe-mcp\"}],\"sidebar\":[{\"text\":\"User Guide\",\"items\":[{\"text\":\"Overview\",\"link\":\"/\"},{\"text\":\"How It Works\",\"link\":\"/user/how-it-works\"},{\"text\":\"Agent Setup\",\"link\":\"/user/agent-setup\"},{\"text\":\"Vibe Engineering\",\"link\":\"/user/advanced-engineering\"},{\"text\":\"Long-Term Memory\",\"link\":\"/user/long-term-memory\"},{\"text\":\"Beads-Integration\",\"link\":\"/user/beads-integration\"},{\"text\":\"Tutorial\",\"link\":\"/user/tutorial\"}]},{\"text\":\"Workflows\",\"items\":[{\"text\":\"Workflow-Selection\",\"link\":\"/user/workflow-selection\"},{\"text\":\"Packaged Workflows\",\"link\":\"/user/packaged-workflows\"},{\"text\":\"Custom Workflows\",\"link\":\"/user/custom-workflows\"},{\"text\":\"Explore All Workflows\",\"link\":\"/workflows\"},{\"text\":\"Crowd MCP Integration\",\"link\":\"/user/crowd-mcp-integration\"}]}]},\"locales\":{},\"scrollOffset\":134,\"cleanUrls\":false}");</script>
+  </body>
+</html>