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/greenfield.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_greenfield.md.vx_g-WOe.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/greenfield.yaml ADDED Viewed

@@ -0,0 +1,201 @@
+# yaml-language-server: $schema=../state-machine-schema.json
+---
+name: 'greenfield'
+description: 'A comprehensive workflow for starting new projects from scratch: Ideation, Architecture, Plan, Code, Document - ideal for greenfield projects requiring thorough upfront planning'
+initial_state: 'ideation'
+# Enhanced metadata for better discoverability
+metadata:
+  domain: 'code'
+  complexity: 'high'
+  bestFor:
+    - 'New projects from scratch'
+    - 'Greenfield development'
+    - 'Complex system design'
+    - 'Comprehensive planning needed'
+  useCases:
+    - 'Starting a new application'
+    - 'Building a new service'
+    - 'Creating a new library'
+  examples:
+    - 'Build a new web application'
+    - 'Create a microservice architecture'
+    - 'Develop a new CLI tool'
+  requiresDocumentation: true
+# States with default instructions and transitions
+states:
+  ideation:
+    description: 'Deep requirements discovery and PRD creation phase'
+    default_instructions: |
+      Understand WHAT the system should do, WHO will use it, WHY it's needed, and WHAT'S in/out of scope by exploring:
+      - Are there existing solutions? What gaps do they have?
+      - What technologies must/cannot be used? Why?
+      - How will you measure product success?
+      - Have you validated this need with potential users?
+      Don't discuss technical implementation yet - focus purely on understanding the problem space and requirements. Document all findings in `$REQUIREMENTS_DOC` and create tasks as needed.
+    transitions:
+      - trigger: 'ideation_complete'
+        to: 'architecture'
+        transition_reason: 'PRD is complete with clear requirements, ready for technical architecture design'
+        review_perspectives:
+          - perspective: 'business_analyst'
+            prompt: 'Review the Product Requirements Document for completeness, clarity, and business value. Ensure all stakeholder needs are captured, requirements are testable, and scope is well-defined.'
+          - perspective: 'ux_expert'
+            prompt: 'Evaluate user experience requirements and usability considerations. Ensure user personas, workflows, and interaction patterns are properly defined for the greenfield project.'
+  architecture:
+    description: 'Tech stack selection and architecture design phase'
+    default_instructions: |
+      Design the technical solution based on requirements from `$REQUIREMENTS_DOC`.
+      - Ask about the user's technical preferences and experience
+      - Challenge their choices by presenting alternatives
+      - Evaluate pros and cons of different tech stacks, frameworks, and architectural patterns
+      - Consider non-functional requirements like scalability, performance, maintainability, and deployment
+      Create a comprehensive architecture document in `$ARCHITECTURE_DOC`. Don't start coding yet - focus on technical design decisions.
+    transitions:
+      - trigger: 'need_more_ideation'
+        to: 'ideation'
+        additional_instructions: 'Architecture work revealed gaps in requirements understanding. Focus on the specific requirements areas that need clarification before continuing with technical design.'
+        transition_reason: 'Architecture work revealed need for more requirements clarification'
+      - trigger: 'architecture_complete'
+        to: 'plan'
+        additional_instructions: 'Present the implementation plan to the user and document it thoroughly.'
+        transition_reason: 'Technical architecture is complete, ready for implementation planning'
+        review_perspectives:
+          - perspective: 'architect'
+            prompt: 'Review the technical architecture for completeness, scalability, and maintainability. Ensure technology choices are appropriate and architectural patterns are sound for a greenfield project.'
+          - perspective: 'security_expert'
+            prompt: 'Evaluate security architecture, data protection strategies, and potential vulnerabilities. Ensure security is built into the foundation of the greenfield project from the start.'
+      - trigger: 'abandon_project'
+        to: 'ideation'
+        instructions: >
+          Project development abandoned during architecture phase. Return to ideation state for new projects.
+          Task history and PRD will remain for future reference.
+        additional_instructions: 'Project development abandoned during architecture phase. Clean up any architecture work and prepare for new projects.'
+        transition_reason: 'User decided to abandon project during architecture phase'
+  plan:
+    description: 'Implementation planning phase based on established architecture'
+    default_instructions: |
+      Create a detailed implementation strategy based on your completed architecture in `$ARCHITECTURE_DOC` and requirements from `$REQUIREMENTS_DOC`.
+      **STEP 1: Break Down Work**
+      - Break down the work into specific, actionable tasks
+      - Consider the chosen tech stack and architectural decisions
+      - Plan the implementation order and identify dependencies
+      **STEP 2: Assess Risks**
+      - Consider potential risks and mitigation strategies
+      - Document the detailed design in `$DESIGN_DOC`
+      **STEP 3: Create Tasks**
+      - Create tasks thoroughly with clear milestones for implementation work
+      - Ensure each task is actionable and has clear acceptance criteria
+    transitions:
+      - trigger: 'need_architecture_changes'
+        to: 'architecture'
+        additional_instructions: "Planning revealed issues with the current architecture. Consider what you've learned during planning and adjust the technical design accordingly. Document the changes and reasons."
+        transition_reason: 'Planning work revealed need to revise the architecture'
+      - trigger: 'plan_complete'
+        to: 'code'
+        additional_instructions: "Implementation plan is complete! ✅ Now transition to coding phase. Read specific documentation before using the chosen libraries and frameworks. Follow the architectural patterns and tech stack decisions you've made. Modularize your code according to best practices. Stay focused on the current project scope defined in your PRD. Update task progress as you complete planning work."
+        transition_reason: 'Implementation plan is complete and ready for coding'
+      - trigger: 'abandon_project'
+        to: 'ideation'
+        instructions: >
+          Project development abandoned during planning. Return to ideation state for new projects.
+          Task history, PRD, and architecture documentation will remain for future reference.
+        additional_instructions: 'Project development abandoned during planning. Clean up any planning work and prepare for new projects.'
+        transition_reason: 'User decided to abandon project during planning phase'
+  code:
+    description: 'Implementation phase following the established plan and architecture'
+    default_instructions: |
+      Build the solution following your plan and detailed design from `$DESIGN_DOC` using the architecture from `$ARCHITECTURE_DOC`.
+      - Ensure all requirements from `$REQUIREMENTS_DOC` you are currently working on are met
+      - Write clean, well-structured code with proper error handling
+      - Prevent regression by building, linting, and executing existing tests
+      - Stay flexible and adapt the plan as you learn more during implementation, but maintain alignment with your architecture decisions
+      - Update task progress and create new tasks as needed for current phase work
+    transitions:
+      - trigger: 'need_replanning'
+        to: 'plan'
+        additional_instructions: "Implementation revealed issues with the current plan. Consider what you've learned during coding and adjust the implementation strategy accordingly while maintaining architectural consistency. Document the changes and reasons."
+        transition_reason: 'Implementation work revealed need to revise the plan'
+      - trigger: 'need_architecture_changes'
+        to: 'architecture'
+        additional_instructions: 'Implementation revealed fundamental issues with the architecture that require design changes. Focus on the specific architectural problems that are blocking implementation progress.'
+        transition_reason: 'Implementation work revealed need for architectural changes'
+      - trigger: 'code_complete'
+        to: 'finalize'
+        transition_reason: 'Core implementation is complete, ready for comprehensive documentation'
+      - trigger: 'abandon_project'
+        to: 'ideation'
+        instructions: >
+          Project development abandoned during implementation. Clean up any incomplete code and return to ideation.
+          Task history, PRD, architecture documentation, and any completed work will remain for future reference.
+        additional_instructions: 'Project development abandoned during implementation. Clean up any incomplete code and prepare for new projects.'
+        transition_reason: 'User decided to abandon project during implementation'
+  finalize:
+    description: 'Code cleanup and documentation finalization'
+    default_instructions: |
+      This phase ensures code quality and documentation accuracy through systematic cleanup and review.
+      **STEP 1: Code Cleanup**
+      Systematically clean up development artifacts:
+      1. Remove all temporary debug output statements used during development (console logging, print statements, debug functions)
+      2. 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
+      3. Remove debugging code blocks, temporary test code, and commented-out code
+         - Ensure proper error handling replaces temporary debug logging
+      **STEP 2: Documentation Review**
+      Update documentation to reflect final implementation:
+      1. Update long-term memory documents based on what was actually implemented:
+         - Update `$REQUIREMENTS_DOC` if requirements changed during development
+         - Update `$ARCHITECTURE_DOC` if architectural decisions evolved
+         - Update `$DESIGN_DOC` if design details were refined or changed
+      2. Review documentation against actual implemented functionality
+      3. Only modify documentation sections that have functional changes
+      4. Remove references to development iterations, progress notes, and temporary decisions
+      5. Ensure documentation describes the final implemented state, not the development process
+      6. Ask user to review document updates
+      **STEP 3: Comprehensive Documentation**
+      Ensure project has complete documentation for newcomers including setup, usage, architecture overview, and contribution guidelines.
+      **STEP 4: Final Validation**
+      - Run existing tests to ensure cleanup didn't break functionality
+      - Verify documentation accuracy with a final review
+      - Ensure project is ready for users and contributors
+      - Update task progress and mark completed work as you finalize the project
+    transitions:
+      - trigger: 'need_code_changes'
+        to: 'code'
+        additional_instructions: 'Finalization revealed issues that require code changes. Focus on the problems identified during final review that affect usability or functionality.'
+        transition_reason: 'Finalization revealed issues requiring code changes'
+      - trigger: 'finalization_complete'
+        to: 'ideation'
+        transition_reason: 'Project delivery complete with finalized code and documentation, ready for next greenfield project'
+      - trigger: 'abandon_project'
+        to: 'ideation'
+        additional_instructions: 'Project development abandoned during finalization. Clean up any finalization artifacts and prepare for new projects.'
+        transition_reason: 'User decided to abandon project during finalization phase'

package/packages/docs/.vitepress/dist/workflows/minor.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_minor.md.DdnfwMf4.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/minor.yaml ADDED Viewed

@@ -0,0 +1,138 @@
+# yaml-language-server: $schema=../state-machine-schema.json
+---
+name: 'minor'
+description: 'A streamlined workflow for small-impact changes: Explore (analysis + design) → Implement (code + test + commit) - optimized for minor enhancements'
+initial_state: 'explore'
+# Enhanced metadata for better discoverability
+metadata:
+  domain: 'code'
+  complexity: 'low'
+  bestFor:
+    - 'Small bug fixes'
+    - 'Minor feature enhancements'
+    - 'Code refactoring'
+    - 'Documentation updates'
+  useCases:
+    - 'Adding a new parameter to an existing function'
+    - 'Improving error messages'
+    - 'Small UI adjustments'
+  examples:
+    - 'Fix a typo in user interface text'
+    - 'Add validation to an input field'
+    - 'Enhance logging in a specific module'
+# States with default instructions and transitions
+states:
+  explore:
+    description: 'Analysis and design phase - understanding and planning without implementation'
+    default_instructions: >
+      Understand the problem, analyze existing patterns, and design your approach.
+      Consider the scope and impact of the change.
+      **STEP 1: Analyze Requirements**
+      - If `$REQUIREMENTS_DOC` exists: Use it to understand the required changes
+      - Otherwise: Document requirements in your task management system
+      **STEP 2: Review Design Approach**
+      - If `$DESIGN_DOC` exists: Respect the design approach documented in `$DESIGN_DOC`
+      - 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
+    transitions:
+      - trigger: 'exploration_complete'
+        to: 'implement'
+        transition_reason: 'Analysis and design complete, ready for streamlined implementation'
+  implement:
+    description: 'Combined implementation phase - code, test, and commit'
+    default_instructions: >
+      Write clean, focused code for the minor enhancement, test your changes, and prepare for commit.
+      **STEP 1: Review Design and Requirements**
+      - If `$DESIGN_DOC` exists: Follow your design from `$DESIGN_DOC`
+      - Otherwise: Elaborate design options and present them to the user
+      - If `$REQUIREMENTS_DOC` exists: Ensure the relevant requirements from `$REQUIREMENTS_DOC` 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
+    transitions:
+      - trigger: 'need_more_analysis'
+        to: 'explore'
+        additional_instructions: 'Implementation revealed gaps in analysis or design. Focus on the specific areas that need clarification before continuing with implementation.'
+        transition_reason: 'Implementation work revealed need for more analysis or design'
+      - trigger: 'implementation_complete'
+        to: 'finalize'
+        transition_reason: 'Implementation complete, ready for finalization'
+      - trigger: 'abandon_feature'
+        to: 'explore'
+        instructions: >
+          Minor enhancement abandoned during implementation. Clean up any incomplete code and return to exploration.
+          Task history and any completed work will remain for future reference.
+        additional_instructions: 'Clean up any incomplete code and prepare for new tasks.'
+        transition_reason: 'User decided to abandon minor enhancement during implementation'
+  finalize:
+    description: 'Code cleanup and documentation finalization'
+    default_instructions: >
+      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 `$REQUIREMENTS_DOC` exists: Update `$REQUIREMENTS_DOC` if requirements changed during development
+        - If `$DESIGN_DOC` exists: Update `$DESIGN_DOC` 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
+    transitions:
+      - trigger: 'need_implementation_changes'
+        to: 'implement'
+        additional_instructions: 'Finalization revealed issues that require implementation changes. Focus on the specific problems identified during final review.'
+        transition_reason: 'Finalization revealed issues requiring implementation changes'
+      - trigger: 'finalization_complete'
+        to: 'explore'
+        transition_reason: 'Minor enhancement delivery complete, ready for next task'
+      - trigger: 'abandon_feature'
+        to: 'explore'
+        additional_instructions: 'Clean up any finalization artifacts and prepare for new tasks.'
+        transition_reason: 'User decided to abandon minor enhancement during finalization'

package/packages/docs/.vitepress/dist/workflows/posts.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_posts.md.SOldXvq7.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/posts.yaml ADDED Viewed

@@ -0,0 +1,193 @@
+name: posts
+description: 'A comprehensive workflow for writing posts - from blog posts to short-form content, with research, story development, and multi-platform publishing'
+initial_state: discovery
+# Enhanced metadata for better discoverability
+metadata:
+  domain: 'office'
+  complexity: 'medium'
+  bestFor:
+    - 'Blog post writing'
+    - 'Content creation'
+    - 'Article development'
+    - 'Social media content'
+  useCases:
+    - 'Writing technical blog posts'
+    - 'Creating marketing content'
+    - 'Developing thought leadership articles'
+  examples:
+    - 'Write a tutorial blog post'
+    - 'Create a product announcement'
+    - 'Develop a technical deep-dive article'
+states:
+  discovery:
+    description: 'Research topic, decide format, and analyze competitive landscape'
+    default_instructions: |
+      Define the foundation of your post by establishing topic understanding and format.
+      Determine post format by asking about:
+      - Goal (quick insight vs deep exploration)
+      - Topic complexity level
+      - Available time for development
+      - Research existing content on this topic to identify gaps and opportunities
+      - Guide user to articulate personal motivation and unique angle
+      - Conduct competitive landscape analysis to avoid duplication
+      - Define target audience and platform considerations
+      - Gather initial sources and reference materials
+      Establish clear direction before moving to story development.
+      Update `$PLAN_FILE` with discovery progress and key decisions.
+    transitions:
+      - trigger: discovery_complete
+        to: story
+        transition_reason: 'Topic researched and format decided, ready for story structure development'
+  story:
+    description: 'Create narrative structure and story outline'
+    default_instructions: |
+      Create a compelling narrative structure for your post.
+      - Create detailed story outline with clear beginning, middle, end
+      - Identify key messages and memorable metaphors/examples
+      - Define content scope boundaries to maintain focus and avoid adjacent topics
+      - Plan how content will adapt across different platforms
+      - Ensure narrative arc matches chosen format (concise for short posts, comprehensive for long-form)
+      - Structure content to maintain user's personal voice and conversational style
+      Build a solid story foundation before moving to writing.
+      Update `$PLAN_FILE` with story decisions and structural progress.
+    transitions:
+      - trigger: story_complete
+        to: writing
+        additional_instructions: |
+          Story complete! ✅ You have a clear narrative structure and content outline.
+          Update `$PLAN_FILE` with writing tasks and mark completed story work.
+        transition_reason: 'Story structure and outline complete, ready for content creation'
+      - trigger: need_more_discovery
+        to: discovery
+        additional_instructions: 'Resolve gaps in research or format clarity by focusing on foundational aspects.'
+        transition_reason: 'Story work revealed need for additional discovery or research'
+      - trigger: abandon_post
+        to: discovery
+        instructions: |
+          Abandon post development during story phase. Clean up story work and return to discovery.
+          The `$PLAN_FILE` and any completed work will remain for future reference.
+        additional_instructions: 'Clean up and prepare for new topics.'
+        transition_reason: 'User decided to abandon post during story phase'
+  writing:
+    description: 'Create the actual post content following story outline'
+    default_instructions: |
+      Create engaging content following the established story outline.
+      - Write content following the established story outline
+      - Maintain consistent narrative flow and personal voice
+      - Create engaging, conversational content in user's style
+      - Ensure content length matches chosen format (3-10 lines for short, 2000-5000+ words for long)
+      - Stay within defined content scope to avoid adjacent topics
+      - Include concrete examples and metaphors as planned
+      - Create clear section structure with appropriate headings (for long-form)
+      Focus on high-quality content creation without visual elements.
+      Update `$PLAN_FILE` with writing progress and content decisions.
+    transitions:
+      - trigger: writing_complete
+        to: illustration
+        additional_instructions: |
+          Writing complete! ✅ You have solid content that follows your story outline.
+          Update `$PLAN_FILE` with illustration tasks and mark completed writing work.
+        transition_reason: 'Content creation complete, ready for visual enhancement'
+      - trigger: need_story_revision
+        to: story
+        additional_instructions: 'Refine the story foundation to address issues with structure or narrative flow.'
+        transition_reason: 'Content creation revealed need for story structure refinement'
+      - trigger: abandon_post
+        to: discovery
+        instructions: |
+          Abandon post development during writing. Clean up writing work and return to discovery.
+          The `$PLAN_FILE` and any completed work will remain for future reference.
+        additional_instructions: 'Clean up and prepare for new topics.'
+        transition_reason: 'User decided to abandon post during writing phase'
+  illustration:
+    description: 'Create and integrate visual elements'
+    default_instructions: |
+      Enhance your content with visual elements.
+      - Identify strategic locations for visual elements
+      - Create or source appropriate visuals (screenshots, diagrams, metaphorical images)
+      - Ensure visual density matches format (minimal for short posts, comprehensive for long-form)
+      - Maintain visual consistency and professional appearance
+      - Ensure visuals support and enhance the written content
+      - Consider accessibility and platform compatibility
+      - Plan visual integration and placement
+      Create visuals that enhance rather than distract from the content.
+      Update `$PLAN_FILE` with illustration progress and visual decisions.
+    transitions:
+      - trigger: illustration_complete
+        to: distribution
+        additional_instructions: |
+          Illustration complete! ✅ You have visually enhanced content ready for publishing.
+          Update `$PLAN_FILE` with distribution tasks and mark completed illustration work.
+        transition_reason: 'Visual elements complete, ready for SEO optimization and publishing'
+      - trigger: need_more_content
+        to: writing
+        additional_instructions: 'Complete the content foundation to address gaps revealed during visual work.'
+        transition_reason: 'Visual work revealed need for additional written content'
+      - trigger: abandon_post
+        to: discovery
+        instructions: |
+          Abandon post development during illustration. Clean up illustration work and return to discovery.
+          The `$PLAN_FILE` and any completed work will remain for future reference.
+        additional_instructions: 'Clean up and prepare for new topics.'
+        transition_reason: 'User decided to abandon post during illustration phase'
+  distribution:
+    description: 'Optimize for SEO and publish across platforms'
+    default_instructions: |
+      Optimize content and publish across multiple platforms.
+      - Create compelling, SEO-optimized titles and descriptions
+      - Add appropriate tags and metadata for discoverability
+      - Adapt content formatting for different platforms (LinkedIn, Medium, HN)
+      - Maintain core message while adjusting for platform-specific requirements
+      - Conduct final quality review and polish
+      - Prepare publishing materials and schedule
+      - Execute multi-platform publishing strategy
+      Maximize reach while maintaining content quality and consistency.
+      Update `$PLAN_FILE` with distribution progress and publishing decisions.
+    transitions:
+      - trigger: distribution_complete
+        to: discovery
+        transition_reason: 'Post publishing completed successfully, ready for new projects'
+      - trigger: need_final_review
+        to: illustration
+        additional_instructions: 'Refine visuals or content presentation based on issues identified during publishing preparation.'
+        transition_reason: 'Publishing preparation identified issues requiring visual or content refinement'
+      - trigger: abandon_post
+        to: discovery
+        instructions: |
+          Abandon post development before distribution. Clean up distribution preparation and return to discovery.
+          The `$PLAN_FILE` and completed work will remain for future reference.
+        additional_instructions: 'Clean up and prepare for new topics.'
+        transition_reason: 'User decided to abandon post before distribution'