@codemcp/workflows 5.3.0 → 6.0.2

package/packages/docs/.vitepress/dist/workflows/slides.yaml

@@ -0,0 +1,237 @@
+name: slides
+description: 'A comprehensive workflow for creating presentations - tool-agnostic approach that works with Slidev, PowerPoint, Google Slides, or any presentation platform'
+initial_state: ideate
+
+# Enhanced metadata for better discoverability
+metadata:
+  domain: 'office'
+  complexity: 'medium'
+  bestFor:
+    - 'Presentation creation'
+    - 'Slide deck development'
+    - 'Conference talks'
+    - 'Training materials'
+  useCases:
+    - 'Creating a technical presentation'
+    - 'Building training slides'
+    - 'Preparing a conference talk'
+  examples:
+    - 'Create a product demo presentation'
+    - 'Build onboarding slides'
+    - 'Develop a technical workshop'
+
+states:
+  ideate:
+    description: 'Brainstorm presentation concept and define strategic foundation'
+    default_instructions: |
+      **Clarify the presentation foundation** with the user by gathering essential information:
+
+      - Brainstorm presentation topic and key messages
+      - Define target audience and their knowledge level
+      - Set presentation goals and success criteria
+      - Research topic and gather reference materials
+      - Define scope, time constraints, and context
+
+      **Update** the plan file with ideation progress and key decisions before proceeding to structure.
+
+    transitions:
+      - trigger: ideation_complete
+        to: structure
+        transition_reason: 'Presentation concept and goals clearly defined, ready for content structuring'
+
+  structure:
+    description: 'Organize content flow and logical progression'
+    default_instructions: |
+      **Create a detailed presentation structure** by organizing your content logically and effectively:
+
+      - Create detailed presentation outline with main sections
+      - Define slide sequence and narrative flow
+      - Plan smooth transitions between topics
+      - Identify key examples, case studies, or demonstrations needed
+      - Estimate timing for each section and overall presentation
+      - Consider audience engagement points and interaction opportunities
+
+      **Update** the plan file with structural decisions and progress before moving to content drafting.
+
+    transitions:
+      - trigger: structure_complete
+        to: draft
+        additional_instructions: |
+          **Structure phase complete!** You have a well-organized outline and clear content flow.
+
+          Update the plan file with drafting tasks and mark completed structural work.
+        transition_reason: 'Content structure and flow established, ready for content creation'
+
+      - trigger: need_more_ideation
+        to: ideate
+        additional_instructions: 'Structural work revealed gaps in the initial concept or goals. Focus on clarifying these fundamental aspects.'
+        transition_reason: 'Structure work revealed need for more ideation or concept refinement'
+
+      - trigger: abandon_presentation
+        to: ideate
+        instructions: |
+          **Abandon structural work** - Clean up structural work and return to ideation.
+
+          The plan file and any completed work will remain for future reference.
+        additional_instructions: 'Presentation abandoned during structure phase. Clean up and prepare for new topics.'
+        transition_reason: 'User decided to abandon presentation during structure phase'
+
+  draft:
+    description: 'Create content, speaker notes, and visual planning'
+    default_instructions: |
+      **Create content and speaker notes** to establish the presentation material and delivery guide:
+
+      - Write clear, engaging content for each slide/section
+      - Create comprehensive speaker notes as a main deliverable
+      - Make strategic decisions about visual vs. spoken content split
+      - Identify concepts that can be effectively visualized
+      - Define what each visualization should communicate
+      - Create placeholders and specifications for visual content
+      - Ensure content aligns with timing and audience needs
+
+      **Update** the plan file with drafting progress and content decisions before moving to styling.
+
+    transitions:
+      - trigger: draft_complete
+        to: style
+        additional_instructions: |
+          **Draft phase complete!** You have solid content, speaker notes, and visual planning.
+
+          Update the plan file with styling tasks and mark completed drafting work.
+        transition_reason: 'Content and speaker notes complete, ready for visual design and styling'
+
+      - trigger: need_more_structure
+        to: structure
+        additional_instructions: 'Drafting revealed issues with content organization or flow. Focus on refining the structural foundation.'
+        transition_reason: 'Content creation revealed need for better structure or organization'
+
+      - trigger: abandon_presentation
+        to: ideate
+        instructions: |
+          **Abandon drafting work** - Clean up content work and return to ideation.
+
+          The plan file and any completed work will remain for future reference.
+        additional_instructions: 'Presentation abandoned during draft phase. Clean up and prepare for new topics.'
+        transition_reason: 'User decided to abandon presentation during draft phase'
+
+  style:
+    description: 'Apply design, create visuals, and enhance presentation aesthetics'
+    default_instructions: |
+      **Apply visual design and create presentation aesthetics** to bring professional appeal and consistency:
+
+      - Evaluate presentation requirements and choose appropriate tool/platform
+      - Select themes, templates, and establish visual design approach
+      - Source existing visuals, images, and graphic elements
+      - Create detailed AI image generation prompts for missing visuals
+      - Generate or create required visual content using AI tools or other methods
+      - Apply consistent visual design, colors, and branding
+      - Ensure visual elements effectively support and enhance the content
+      - Test visual consistency across all slides/sections
+
+      **Update** the plan file with styling progress and design decisions before moving to review.
+
+    transitions:
+      - trigger: style_complete
+        to: review
+        additional_instructions: |
+          **Style phase complete!** You have a visually appealing presentation with consistent design.
+
+          Update the plan file with review tasks and mark completed styling work.
+        transition_reason: 'Visual design and styling complete, ready for content and delivery review'
+
+      - trigger: need_more_content
+        to: draft
+        additional_instructions: 'Styling work revealed gaps in content or speaker notes. Focus on completing the content foundation.'
+        transition_reason: 'Visual design revealed need for additional content or speaker note refinement'
+
+      - trigger: abandon_presentation
+        to: ideate
+        instructions: |
+          **Abandon styling work** - Clean up design work and return to ideation.
+
+          The plan file and any completed work will remain for future reference.
+        additional_instructions: 'Presentation abandoned during style phase. Clean up and prepare for new topics.'
+        transition_reason: 'User decided to abandon presentation during style phase'
+
+  review:
+    description: 'Validate content quality and presentation effectiveness'
+    default_instructions: |
+      **Validate presentation quality** by reviewing content, timing, visuals, and delivery readiness:
+
+      - Review content flow, narrative coherence, and logical progression
+      - Test presentation timing and pacing for your allocated time
+      - Verify visual quality, consistency, and professional appearance
+      - Practice delivery to identify potential issues or improvements
+      - Gather feedback from test audience, colleagues, or stakeholders
+      - Check technical setup, compatibility, and backup plans
+      - Ensure all interactive elements and visuals work correctly
+      - Refine speaker notes and delivery preparation
+
+      **Update** the plan file with review progress and refinements before moving to delivery preparation.
+
+    transitions:
+      - trigger: review_complete
+        to: deliver
+        additional_instructions: |
+          **Review phase complete!** Your presentation has been validated and refined for delivery.
+
+          Update the plan file with delivery preparation tasks and mark completed review work.
+        transition_reason: 'Presentation reviewed and validated, ready for final delivery preparation'
+
+      - trigger: need_style_changes
+        to: style
+        additional_instructions: 'Review revealed visual or design issues that need attention. Focus on addressing these styling concerns.'
+        transition_reason: 'Review process identified visual or design issues requiring style phase work'
+
+      - trigger: need_content_changes
+        to: draft
+        additional_instructions: 'Review revealed content gaps or issues that need addressing. Focus on refining the content and speaker notes.'
+        transition_reason: 'Review process identified content issues requiring draft phase work'
+
+      - trigger: abandon_presentation
+        to: ideate
+        instructions: |
+          **Abandon review work** - Clean up review work and return to ideation.
+
+          The plan file and any completed work will remain for future reference.
+        additional_instructions: 'Presentation abandoned during review phase. Clean up and prepare for new topics.'
+        transition_reason: 'User decided to abandon presentation during review phase'
+
+  deliver:
+    description: 'Prepare final presentation for delivery'
+    default_instructions: |
+      **Prepare final delivery** by exporting formats, testing setup, and ensuring flawless execution:
+
+      - Export presentation to all required formats (native, PDF, backup formats)
+      - Finalize speaker setup, notes, and delivery materials
+      - Configure and test presentation environment and technical setup
+      - Create comprehensive contingency plans for potential technical issues
+      - Conduct final rehearsal in actual delivery environment if possible
+      - Prepare handouts, follow-up materials, or additional resources
+      - Ensure all backup plans and alternatives are ready
+      - Final check of timing, flow, and delivery readiness
+
+      **Update** the plan file with delivery preparation progress to ensure successful delivery.
+
+    transitions:
+      - trigger: delivery_complete
+        to: ideate
+        additional_instructions: |
+          **Delivery phase complete!** Your presentation has been successfully delivered.
+
+          Mark all delivery tasks as complete in the plan file and prepare for new work.
+        transition_reason: 'Presentation delivery completed successfully, ready for new projects'
+
+      - trigger: need_final_review
+        to: review
+        additional_instructions: 'Final preparation revealed issues requiring additional review. Focus on addressing these concerns before delivery.'
+        transition_reason: 'Delivery preparation identified issues requiring additional review'
+
+      - trigger: abandon_presentation
+        to: ideate
+        instructions: |
+          **Abandon delivery preparation** - Clean up delivery preparation and return to ideation.
+
+          The plan file and completed work will remain for future reference.
+        additional_instructions: 'Presentation abandoned before delivery. Clean up and prepare for new topics.'
+        transition_reason: 'User decided to abandon presentation before delivery'

package/packages/docs/.vitepress/dist/workflows/tdd.html

@@ -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_tdd.md.BjVC69tu.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/tdd.yaml

@@ -0,0 +1,160 @@
+# yaml-language-server: $schema=../state-machine-schema.json
+---
+name: 'tdd'
+description: 'Test-Driven Development workflow: Explore → Red → Green → Refactor cycle for quality-focused development'
+initial_state: 'explore'
+
+# Enhanced metadata for better discoverability
+metadata:
+  domain: 'code'
+  complexity: 'medium'
+  bestFor:
+    - 'TDD development'
+    - 'Test-first coding'
+    - 'Quality-focused development'
+    - 'Refactoring existing code'
+  useCases:
+    - 'Adding new features with comprehensive tests'
+    - 'Refactoring legacy code safely'
+    - 'Building robust, well-tested components'
+  examples:
+    - 'Add new API endpoint with full test coverage'
+    - 'Refactor existing function with safety net of tests'
+    - 'Build new feature following TDD principles'
+
+# States with default instructions and transitions
+states:
+  explore:
+    description: 'Research and exploration phase - understanding the problem space and codebase'
+    default_instructions: |
+      **STEP 1:** Gather context about what needs to be developed. Focus on the WHY and WHAT, not the HOW.
+
+      **STEP 2:** Research the codebase and understand existing patterns.
+      - Ask the user about conventions or rules if uncertain
+      - Read relevant files and documentation
+      - If `$REQUIREMENTS_DOC` exists, understand and document requirements there, otherwise document in your task management system
+
+      **STEP 3:** Document your findings and create tasks as needed.
+      - Don't write code or tests yet
+      - Focus on understanding the problem space
+      - Prepare for the RED phase of the TDD cycle
+    transitions:
+      - trigger: 'exploration_complete'
+        to: 'red'
+        additional_instructions: 'Update task progress as you complete exploration work.'
+        transition_reason: 'Sufficient understanding gained, ready to start TDD cycle with failing test'
+
+  red:
+    description: 'RED phase - Write a failing test that defines the expected behavior'
+    default_instructions: |
+      Write a failing test that defines the expected behavior for the feature.
+
+      **STEP 1:** Validate test approach with the user before writing.
+      - Determine what type of test is appropriate (unit, integration, acceptance, etc.)
+      - Confirm your test will validate the actual requirements
+      - Ensure alignment with the feature specification
+
+      **STEP 2:** Write a focused, meaningful test.
+      - Clearly define the expected behavior
+      - Will fail initially since functionality doesn't exist yet
+      - Focus on one specific aspect of the functionality
+      - Use appropriate assertions (not meaningless checks like assert(true))
+
+      **STEP 3:** Validate test failure.
+      - Run the test to confirm it fails for the right reason
+      - Document the test and expected failure mode
+      - Update task progress
+    transitions:
+      - trigger: 'test_written_and_failing'
+        to: 'green'
+        additional_instructions: 'Update task progress as you complete test writing work.'
+        transition_reason: 'Failing test successfully written and validated, ready to implement'
+
+      - trigger: 'need_more_exploration'
+        to: 'explore'
+        transition_reason: 'Test writing revealed need for more exploration'
+
+      - trigger: 'abandon_feature'
+        to: 'explore'
+        additional_instructions: 'Clean up any test artifacts and prepare for new tasks.'
+        transition_reason: 'User decided to abandon feature during test phase'
+
+  green:
+    description: 'GREEN phase - Write only the necessary code to make the test pass'
+    default_instructions: |
+      Implement the necessary code to make the failing test pass with proper functionality.
+
+      **STEP 1:** Write real, working implementation.
+      - Make the test pass with actual logic, not shortcuts
+      - Write only what's necessary (no over-engineering)
+      - Avoid dirty hacks such as hardcoded return values or meaningless assertions
+      - Focus on solving the actual problem
+
+      **STEP 2:** Validate implementation quality.
+      - Run the test to confirm it passes
+      - Verify no shortcuts or copy-paste code without understanding
+      - Ensure the solution actually solves the problem
+      - Check that logic is proper, not a bypass
+
+      **STEP 3:** Document and track progress.
+      - Document your implementation approach
+      - Update task progress
+    transitions:
+      - trigger: 'test_passing'
+        to: 'refactor'
+        additional_instructions: 'Update task progress as you complete implementation work.'
+        transition_reason: 'Test passes with proper implementation, ready for refactoring'
+
+      - trigger: 'need_different_test'
+        to: 'red'
+        transition_reason: 'Implementation work revealed need to revise the test'
+
+      - trigger: 'need_more_exploration'
+        to: 'explore'
+        transition_reason: 'Implementation work revealed need for more exploration'
+
+      - trigger: 'abandon_feature'
+        to: 'explore'
+        additional_instructions: 'Clean up any incomplete code and prepare for new tasks.'
+        transition_reason: 'User decided to abandon feature during implementation'
+
+  refactor:
+    description: 'REFACTOR phase - Improve code quality while keeping tests green (cleanup phase)'
+    default_instructions: |
+      Improve code quality while keeping all tests green. This is the cleanup phase where you enhance readability and maintainability.
+
+      **STEP 1:** Identify improvement opportunities.
+      - Remove code duplication
+      - Improve variable and function names
+      - Extract methods for better organization
+      - Simplify complex logic
+      - Apply appropriate design patterns
+
+      **STEP 2:** Make incremental improvements safely.
+      - Run tests after each refactoring change
+      - Immediately revert any change that breaks tests
+      - Make small, focused improvements
+      - Stop when code is clean with no obvious improvements remaining
+
+      **STEP 3:** Document and complete.
+      - Document significant refactoring decisions
+      - Update task progress
+    transitions:
+      - trigger: 'refactoring_complete'
+        to: 'red'
+        additional_instructions: 'Update task progress as you complete refactoring work.'
+        transition_reason: 'Code cleanup complete, ready for next TDD cycle'
+
+      - trigger: 'need_different_approach'
+        to: 'green'
+        transition_reason: 'Refactoring revealed need to revise implementation'
+
+      - trigger: 'feature_complete'
+        to: 'explore'
+        additional_instructions: 'Update task progress to reflect feature completion.'
+        transition_reason: 'Feature fully implemented and cleaned up, ready for new tasks'
+
+      - trigger: 'abandon_feature'
+        to: 'explore'
+        additional_instructions: 'Clean up any refactoring work and prepare for new tasks.'
+        transition_reason: 'User decided to abandon feature during refactoring'

package/packages/docs/.vitepress/dist/workflows/waterfall.html

@@ -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_waterfall.md.CL6jTZP9.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>