@codemcp/workflows 6.19.2 → 6.20.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows",
-  "version": "6.19.2",
+  "version": "6.20.0",
   "description": "A Model Context Protocol server that acts as an intelligent conversation state manager and development guide for LLMs, featuring comprehensive long-term memory with persistent project artifacts",
   "type": "module",
   "main": "packages/cli/dist/index.js",
@@ -51,7 +51,7 @@
     "typescript": "^5.9.3",
     "vitepress": "^1.6.4",
     "vitest": "4.0.18",
-    "@codemcp/workflows-core": "6.19.2"
+    "@codemcp/workflows-core": "6.20.0"
   },
   "lint-staged": {
     "*.{ts,js,mts,cts,tsx,jsx}": [

package/packages/cli/dist/{chunk-4TXLRBGW.js → chunk-4N42FFJE.js}

@@ -2,227 +2,6 @@ import {
   __require
 } from "./chunk-R5U7XKVJ.js";
 
-// ../core/dist/state-machine.js
-var STATE_TRANSITIONS = [
-  // FROM IDLE
-  {
-    from: "idle",
-    to: "requirements",
-    trigger: "new_feature_request",
-    isModeled: true,
-    instructions: "New feature request detected! Start requirements analysis by asking the user clarifying questions about WHAT they need. Focus on understanding their goals, scope, and constraints. Break down their needs into specific, actionable tasks and document them in the plan file. Mark completed requirements tasks as you progress.",
-    transitionReason: "New feature request detected, starting requirements analysis"
-  },
-  // FROM REQUIREMENTS
-  {
-    from: "requirements",
-    to: "requirements",
-    trigger: "refine_requirements",
-    isModeled: true,
-    instructions: "Continue refining requirements. Ask more detailed questions to clarify scope, constraints, and user needs. Add any new requirements to the plan file and mark completed tasks. Ensure you have a complete understanding of WHAT needs to be built before moving to design.",
-    transitionReason: "Requirements need further refinement and clarification"
-  },
-  {
-    from: "requirements",
-    to: "design",
-    trigger: "requirements_complete",
-    isModeled: true,
-    instructions: "Requirements are complete! \u2705 Now transition to design phase. Help the user design the technical solution by asking about architecture, technologies, quality goals, and implementation approach. Focus on HOW to build what was defined in requirements. Document design decisions in the plan file and mark completed requirements tasks.",
-    transitionReason: "All requirements tasks completed, moving to technical design"
-  },
-  {
-    from: "requirements",
-    to: "idle",
-    trigger: "abandon_feature",
-    isModeled: true,
-    instructions: "Feature development abandoned. Clean up any temporary work and return to idle state. The plan file will remain for future reference if the user wants to resume this feature later.",
-    transitionReason: "User decided to abandon this feature development"
-  },
-  // FROM DESIGN
-  {
-    from: "design",
-    to: "design",
-    trigger: "refine_design",
-    isModeled: true,
-    instructions: "Continue refining the technical design. Ask about architecture details, technology choices, data models, API design, and quality considerations. Update the plan file with design decisions and mark completed design tasks. Ensure the design is solid before implementation.",
-    transitionReason: "Design needs further refinement and detail"
-  },
-  {
-    from: "design",
-    to: "requirements",
-    trigger: "requirements_unclear",
-    isModeled: true,
-    instructions: "Design phase revealed unclear requirements. Return to requirements analysis to clarify the WHAT before continuing with HOW. Ask specific questions about the unclear aspects and update the plan file with refined requirements.",
-    transitionReason: "Design work revealed gaps or ambiguities in requirements"
-  },
-  {
-    from: "design",
-    to: "implementation",
-    trigger: "design_complete",
-    isModeled: true,
-    instructions: "Design is complete! \u2705 Now transition to implementation. Guide the user through building the solution following the design. Focus on coding best practices, proper structure, error handling, and basic testing. Update the plan file with implementation progress and mark completed design tasks.",
-    transitionReason: "Technical design is complete, ready to start building"
-  },
-  {
-    from: "design",
-    to: "idle",
-    trigger: "abandon_feature",
-    isModeled: true,
-    instructions: "Feature development abandoned during design phase. Clean up any design artifacts and return to idle state. The plan file will remain for future reference.",
-    transitionReason: "User decided to abandon feature during design phase"
-  },
-  // FROM IMPLEMENTATION
-  {
-    from: "implementation",
-    to: "implementation",
-    trigger: "refine_implementation",
-    isModeled: true,
-    instructions: "Continue implementation work. Help with coding, debugging, structure improvements, and adding functionality. Follow best practices and ensure code quality. Update the plan file with progress and mark completed implementation tasks.",
-    transitionReason: "Implementation work continues, adding features or improving code"
-  },
-  {
-    from: "implementation",
-    to: "design",
-    trigger: "design_issues",
-    isModeled: true,
-    instructions: "Implementation revealed issues with the design. Return to design phase to address architectural problems or design gaps. Analyze what's not working and revise the technical approach. Update the plan file with design changes.",
-    transitionReason: "Implementation work revealed problems with the current design"
-  },
-  {
-    from: "implementation",
-    to: "qa",
-    trigger: "implementation_complete",
-    isModeled: true,
-    instructions: "Implementation is complete! \u2705 Now transition to quality assurance. Take these specific actions:\n\n1. **Syntax Check**: Run syntax checking tools or validate syntax manually\n2. **Build Project**: Build the project to verify it compiles without errors\n3. **Run Linter**: Execute linting tools to ensure code style consistency\n4. **Execute Tests**: Run existing tests to verify functionality\n\nThen conduct a multi-perspective code review:\n- **Security Perspective**: Check for vulnerabilities, input validation, authentication issues\n- **Performance Perspective**: Identify bottlenecks, inefficient algorithms, resource usage\n- **UX Perspective**: Evaluate from the end-user's viewpoint\n- **Maintainability Perspective**: Assess code readability, documentation, future maintenance\n- **Requirement Compliance**: Verify all requirements are properly implemented\n\nUpdate the plan file and mark completed implementation tasks.",
-    transitionReason: "Core implementation is complete, ready for quality review"
-  },
-  {
-    from: "implementation",
-    to: "idle",
-    trigger: "abandon_feature",
-    isModeled: true,
-    instructions: "Feature development abandoned during implementation. Clean up any incomplete code and return to idle state. The plan file and any completed work will remain for future reference.",
-    transitionReason: "User decided to abandon feature during implementation"
-  },
-  // FROM QA (Quality Assurance)
-  {
-    from: "qa",
-    to: "qa",
-    trigger: "refine_qa",
-    isModeled: true,
-    instructions: "Continue quality assurance work. Take these specific actions if not already completed:\n\n1. **Syntax Check**: Run syntax checking tools or validate syntax manually\n2. **Build Project**: Build the project to verify it compiles without errors\n3. **Run Linter**: Execute linting tools to ensure code style consistency\n4. **Execute Tests**: Run existing tests to verify functionality\n\nContinue multi-perspective code review:\n- **Security Perspective**: Check for vulnerabilities, input validation, authentication issues\n- **Performance Perspective**: Identify bottlenecks, inefficient algorithms, resource usage\n- **UX Perspective**: Evaluate from the end-user's viewpoint\n- **Maintainability Perspective**: Assess code readability, documentation, future maintenance\n- **Requirement Compliance**: Verify all requirements are properly implemented\n\nUpdate the plan file with QA progress and mark completed tasks.",
-    transitionReason: "Quality assurance work continues, improving code quality"
-  },
-  {
-    from: "qa",
-    to: "implementation",
-    trigger: "implementation_issues",
-    isModeled: true,
-    instructions: "Quality assurance revealed implementation issues. Return to implementation phase to fix bugs, improve code quality, or add missing functionality. Focus on addressing the specific issues identified during QA review.",
-    transitionReason: "QA review found issues that require implementation changes"
-  },
-  {
-    from: "qa",
-    to: "testing",
-    trigger: "qa_complete",
-    isModeled: true,
-    instructions: "Quality assurance is complete! \u2705 Now transition to testing phase. Create comprehensive test plans, write and execute tests, validate feature completeness, and ensure everything works as expected. Update the plan file and mark completed QA tasks.",
-    transitionReason: "Quality assurance is complete, ready for comprehensive testing"
-  },
-  {
-    from: "qa",
-    to: "idle",
-    trigger: "abandon_feature",
-    isModeled: true,
-    instructions: "Feature development abandoned during QA phase. Clean up any QA artifacts and return to idle state. The plan file and completed work will remain for future reference.",
-    transitionReason: "User decided to abandon feature during quality assurance"
-  },
-  // FROM TESTING
-  {
-    from: "testing",
-    to: "testing",
-    trigger: "refine_testing",
-    isModeled: true,
-    instructions: "Continue testing work. Create more test cases, improve test coverage, run integration tests, and validate edge cases. Update the plan file with testing progress and mark completed testing tasks.",
-    transitionReason: "Testing work continues, improving coverage and validation"
-  },
-  {
-    from: "testing",
-    to: "qa",
-    trigger: "qa_issues",
-    isModeled: true,
-    instructions: "Testing revealed quality issues. Return to QA phase to address code quality problems, documentation gaps, or requirement compliance issues identified during testing. Focus on the specific QA issues found.",
-    transitionReason: "Testing found issues that require quality assurance attention"
-  },
-  {
-    from: "testing",
-    to: "complete",
-    trigger: "testing_complete",
-    isModeled: true,
-    instructions: "Testing is complete! \u2705 The feature is fully implemented, tested, and ready for delivery. Transition to complete state. Summarize what was accomplished and prepare final documentation. Mark all testing tasks as complete.",
-    transitionReason: "All testing is complete, feature is ready for delivery"
-  },
-  {
-    from: "testing",
-    to: "idle",
-    trigger: "abandon_feature",
-    isModeled: true,
-    instructions: "Feature development abandoned during testing phase. Clean up any testing artifacts and return to idle state. The plan file and completed work will remain for future reference.",
-    transitionReason: "User decided to abandon feature during testing phase"
-  },
-  // FROM COMPLETE
-  {
-    from: "complete",
-    to: "idle",
-    trigger: "feature_delivered",
-    isModeled: true,
-    instructions: "Feature has been delivered successfully! Return to idle state, ready for the next development task. The completed plan file serves as documentation of what was accomplished.",
-    transitionReason: "Feature delivery complete, returning to idle state"
-  },
-  {
-    from: "complete",
-    to: "requirements",
-    trigger: "new_feature_request",
-    isModeled: true,
-    instructions: "New feature request while previous feature is complete. Start fresh requirements analysis for the new feature. Ask clarifying questions about what they need and create a new development plan.",
-    transitionReason: "New feature request received, starting new development cycle"
-  }
-];
-var DIRECT_PHASE_INSTRUCTIONS = {
-  idle: "Returned to idle state. Ready to help with new feature development or other tasks.",
-  requirements: "Starting requirements analysis. Ask the user clarifying questions about WHAT they need. Focus on understanding their goals, scope, constraints, and success criteria. Break down their needs into specific, actionable tasks and document them in the plan file. Mark completed requirements tasks as you progress.",
-  design: "Starting design phase. Help the user design the technical solution by asking about architecture, technologies, data models, API design, and quality goals. Focus on HOW to implement what's needed. Document design decisions in the plan file and ensure the approach is solid before implementation.",
-  implementation: "Starting implementation phase. Guide the user through building the solution following best practices. Focus on code structure, error handling, security, and maintainability. Write clean, well-documented code and include basic testing. Update the plan file with implementation progress.",
-  qa: "Starting quality assurance phase. Take the following specific actions:\n\n1. **Syntax Check**: Run syntax checking tools or validate syntax manually\n2. **Build Project**: Build the project to verify it compiles without errors\n3. **Run Linter**: Execute linting tools to ensure code style consistency\n4. **Execute Tests**: Run existing tests to verify functionality\n\nThen conduct a multi-perspective code review:\n- **Security Perspective**: Check for vulnerabilities, input validation, authentication issues\n- **Performance Perspective**: Identify bottlenecks, inefficient algorithms, resource usage\n- **UX Perspective**: Evaluate from the end-user's viewpoint\n- **Maintainability Perspective**: Assess code readability, documentation, future maintenance\n- **Requirement Compliance**: Verify all requirements are properly implemented\n\nUpdate the plan file with QA progress and mark completed tasks.",
-  testing: "Starting testing phase. Create comprehensive test plans, write and execute tests, validate feature completeness, and ensure everything works as expected. Focus on test coverage, edge cases, integration testing, and user acceptance validation.",
-  complete: "Feature development is complete! All phases have been finished successfully. The feature is implemented, tested, and ready for delivery. Summarize what was accomplished and ensure all documentation is finalized."
-};
-function getTransitionInstructions(fromState, toState, trigger) {
-  const modeledTransition = STATE_TRANSITIONS.find((t) => t.from === fromState && t.to === toState && (trigger ? t.trigger === trigger : true));
-  if (modeledTransition) {
-    return {
-      instructions: modeledTransition.instructions,
-      transitionReason: modeledTransition.transitionReason,
-      isModeled: true
-    };
-  }
-  return {
-    instructions: DIRECT_PHASE_INSTRUCTIONS[toState],
-    transitionReason: `Direct transition to ${toState} phase`,
-    isModeled: false
-  };
-}
-function getPossibleTransitions(fromState) {
-  return STATE_TRANSITIONS.filter((t) => t.from === fromState);
-}
-function isModeledTransition(fromState, toState) {
-  return STATE_TRANSITIONS.some((t) => t.from === fromState && t.to === toState && t.isModeled);
-}
-function getContinuePhaseInstructions(phase) {
-  const continueTransition = STATE_TRANSITIONS.find((t) => t.from === phase && t.to === phase);
-  return continueTransition?.instructions || DIRECT_PHASE_INSTRUCTIONS[phase];
-}
-
 // ../core/dist/state-machine-loader.js
 import fs from "fs";
 
@@ -5441,7 +5220,8 @@ var ProjectDocsManager = class {
       $DESIGN_DOC: paths.design,
       $VIBE_DIR: vibeDir,
       $BRANCH_NAME: branchDirName,
-      $VIBE_ROLE: agentRole
+      $VIBE_ROLE: agentRole,
+      $DONE_DEFAULT: "Feature work is complete. Do NOT transition to any other state \u2014 this is a terminal state. If this is a GitHub repository: create a PR. Always: present the final result to the user."
     };
   }
   /**
@@ -6640,12 +6420,6 @@ Do not use your own task management tools.`;
 }
 
 export {
-  STATE_TRANSITIONS,
-  DIRECT_PHASE_INSTRUCTIONS,
-  getTransitionInstructions,
-  getPossibleTransitions,
-  isModeledTransition,
-  getContinuePhaseInstructions,
   LogLevel,
   registerLogSink,
   clearLogSink,

package/packages/cli/dist/{cli-MNJS4MGX.js → cli-MFHC7UWY.js}

@@ -2,7 +2,7 @@ import {
   StateMachineLoader,
   WorkflowManager,
   generateSystemPrompt
-} from "./chunk-4TXLRBGW.js";
+} from "./chunk-4N42FFJE.js";
 import "./chunk-R5U7XKVJ.js";
 
 // src/cli.ts
@@ -998,11 +998,11 @@ var isLocal = existsSync3(join5(__dirname3, "../../core/dist/index.js"));
 var generateSystemPrompt2;
 var StateMachineLoader2;
 if (isLocal) {
-  const coreModule = await import("./dist-WS5DFBKD.js");
+  const coreModule = await import("./dist-TDV3DJ2J.js");
   generateSystemPrompt2 = coreModule.generateSystemPrompt;
   StateMachineLoader2 = coreModule.StateMachineLoader;
 } else {
-  const coreModule = await import("./dist-WS5DFBKD.js");
+  const coreModule = await import("./dist-TDV3DJ2J.js");
   generateSystemPrompt2 = coreModule.generateSystemPrompt;
   StateMachineLoader2 = coreModule.StateMachineLoader;
 }

package/packages/cli/dist/{dist-T6Q2II5X.js → dist-ISN3FRV4.js}

@@ -9261,7 +9261,8 @@ var ProjectDocsManager = class {
       $DESIGN_DOC: paths.design,
       $VIBE_DIR: vibeDir,
       $BRANCH_NAME: branchDirName,
-      $VIBE_ROLE: agentRole
+      $VIBE_ROLE: agentRole,
+      $DONE_DEFAULT: "Feature work is complete. Do NOT transition to any other state \u2014 this is a terminal state. If this is a GitHub repository: create a PR. Always: present the final result to the user."
     };
   }
   /**

package/packages/cli/dist/{dist-WS5DFBKD.js → dist-TDV3DJ2J.js}

@@ -3,7 +3,6 @@ import {
   BeadsStateManager,
   ConfigManager,
   ConversationManager,
-  DIRECT_PHASE_INSTRUCTIONS,
   FileDetectionManager,
   FileStorage,
   GitManager,
@@ -13,7 +12,6 @@ import {
   PathValidationUtils,
   PlanManager,
   ProjectDocsManager,
-  STATE_TRANSITIONS,
   StateMachineLoader,
   TaskBackendManager,
   TemplateManager,
@@ -23,23 +21,18 @@ import {
   clearLogSink,
   createLogger,
   generateSystemPrompt,
-  getContinuePhaseInstructions,
   getPathBasename,
-  getPossibleTransitions,
-  getTransitionInstructions,
-  isModeledTransition,
   logger,
   registerLogSink,
   setLoggingLevel,
   setLoggingLevelFromString
-} from "./chunk-4TXLRBGW.js";
+} from "./chunk-4N42FFJE.js";
 import "./chunk-R5U7XKVJ.js";
 export {
   BeadsIntegration,
   BeadsStateManager,
   ConfigManager,
   ConversationManager,
-  DIRECT_PHASE_INSTRUCTIONS,
   FileDetectionManager,
   FileStorage,
   GitManager,
@@ -49,7 +42,6 @@ export {
   PathValidationUtils,
   PlanManager,
   ProjectDocsManager,
-  STATE_TRANSITIONS,
   StateMachineLoader,
   TaskBackendManager,
   TemplateManager,
@@ -59,11 +51,7 @@ export {
   clearLogSink,
   createLogger,
   generateSystemPrompt,
-  getContinuePhaseInstructions,
   getPathBasename,
-  getPossibleTransitions,
-  getTransitionInstructions,
-  isModeledTransition,
   logger,
   registerLogSink,
   setLoggingLevel,

package/packages/cli/dist/index.js

@@ -10,7 +10,7 @@ var args = process.argv.slice(2);
 if (args.length === 0) {
   const isLocal = existsSync(join(__dirname, "../../mcp-server/dist/index.js"));
   if (isLocal) {
-    const { startMcpServer } = await import("./dist-T6Q2II5X.js");
+    const { startMcpServer } = await import("./dist-ISN3FRV4.js");
     await startMcpServer();
   } else {
     const mcpServerModule = "@codemcp/workflows-server";
@@ -18,6 +18,6 @@ if (args.length === 0) {
     await startMcpServer();
   }
 } else {
-  const { runCli } = await import("./cli-MNJS4MGX.js");
+  const { runCli } = await import("./cli-MFHC7UWY.js");
   await runCli();
 }

package/packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-cli",
-  "version": "6.19.2",
+  "version": "6.20.0",
   "description": "CLI tools for responsible-vibe development workflows",
   "type": "module",
   "scripts": {

package/packages/cli/resources/workflows/adr.yaml

@@ -151,7 +151,5 @@ states:
 
       Complete final validation and cleanup before the ADR is finalized.
 
-    transitions:
-      - trigger: need_decision_changes
-        to: decide
-        transition_reason: 'Final review found problems with the decision documentation'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/boundary-testing.yaml

@@ -364,13 +364,6 @@ states:
       - Ensure test suite is ready for ongoing use and maintenance
 
       Update the plan file with finalization progress and mark completed tasks.
-    transitions:
-      - trigger: 'need_test_changes'
-        to: 'test_suite_implementation'
-        additional_instructions: 'Finalization revealed issues with the test suite. Focus on addressing the specific problems identified during final review.'
-        transition_reason: 'Finalization revealed issues requiring test implementation changes'
 
-      - trigger: 'finalization_complete'
-        to: 'architecture_analysis'
-        additional_instructions: 'Boundary testing workflow complete! Test suite is ready for ongoing use and maintenance. Prepare for next boundary testing project.'
-        transition_reason: 'Test suite finalization complete, ready for production use'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/bugfix.yaml

@@ -162,17 +162,6 @@ states:
       - Verify documentation accuracy with a final review
       - Ensure bug fix is ready for production
       - Update task progress and mark completed work as you finalize the bug fix
-    transitions:
-      - trigger: 'need_fix_changes'
-        to: 'fix'
-        additional_instructions: 'Finalization revealed issues with the bug fix. Focus on addressing the specific problems identified during final review.'
-        transition_reason: 'Finalization revealed issues requiring fix changes'
-
-      - trigger: 'finalization_complete'
-        to: 'reproduce'
-        transition_reason: 'Bug fix complete and finalized, ready for next issue'
 
-      - trigger: 'abandon_bug'
-        to: 'reproduce'
-        additional_instructions: 'Bug finalization abandoned. Clean up any finalization work and prepare for new bug reports.'
-        transition_reason: 'Bug finalization abandoned'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/c4-analysis.yaml

@@ -464,8 +464,6 @@ states:
       - Modernization roadmap
 
       The analysis provides a foundation for future development. Consider using other workflows (waterfall, epcc, etc.) with the comprehensive understanding gained.
-    transitions:
-      - trigger: 'refine_analysis'
-        to: 'component_analysis'
-        additional_instructions: 'Refine specific aspects of analysis. Focus on areas that need additional investigation.'
-        transition_reason: 'Analysis review revealed need for additional component analysis'
+
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/epcc.yaml

@@ -180,17 +180,6 @@ states:
       - Ensure code is ready for production/delivery
 
       Update task progress and mark completed work as you finalize the feature.
-    transitions:
-      - trigger: 'need_code_changes'
-        to: 'code'
-        additional_instructions: 'Focus on the problems identified during final review.'
-        transition_reason: 'Final review found issues requiring code changes'
-
-      - trigger: 'commit_complete'
-        to: 'explore'
-        transition_reason: 'Feature 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 feature during finalization'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/greenfield.yaml

@@ -201,17 +201,6 @@ states:
       - 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'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/minor.yaml

@@ -130,17 +130,6 @@ states:
       - 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'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/posts.yaml

@@ -178,20 +178,5 @@ states:
       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'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/pr-review.yaml

@@ -171,7 +171,5 @@ states:
       Once confirmed, deliver accordingly. For inline comments, attach each finding to the
       specific file and line it refers to. For cross-cutting findings, use a top-level comment.
 
-    transitions:
-      - trigger: 'review_published'
-        to: 'determine_intent'
-        transition_reason: 'Review delivered, ready for next PR'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/qrspi.yaml

@@ -8,7 +8,7 @@ metadata:
   domain: 'code'
   complexity: 'high'
   bestFor:
-    - 'Creative and complex challenges'
+    - 'Creative or complex challenges'
     - 'Deep alignment before execution'
     - 'Unconventional problems'
     - 'Architecture-heavy features'
@@ -34,7 +34,11 @@ states:
       - '**/*.adoc'
     default_instructions: |
       **Principle**: Clarify intent before exploring solutions.
-
+      This is the most important phase: You need to really deeply understand what makes the user want to introduce a change.
+      Ask questions about everything you can't determine straight from the existing codebase.
+      - Ask about the context
+      - follow up on explanations
+      - Ask about rejected alternatives or workarounds
       Document in the development plan: the problem being solved, success criteria, constraints, and any clarifying questions asked. Use `$REQUIREMENTS_DOC` as context only — do not modify it.
 
       Do not research, design, plan, or write code.
@@ -83,8 +87,9 @@ states:
       - '**/*.adoc'
     default_instructions: |
       **Principle**: Align on WHAT and WHY before deciding detailed HOW.
-
+      This is the phase when the we imagening a suitable solution given the boundary conditions.
       Propose 2-3 viable high-level approaches with trade-offs. Reference `$DESIGN_DOC` and `$ARCHITECTURE_DOC` if they exist. Reach consensus with the user on the direction. On loop-back from `need_design_changes`, update those docs if they exist.
+      It's crucial that the user gets actively involved to take an educated decision.
 
       Document the agreed direction in the development plan.
 
@@ -231,17 +236,6 @@ states:
       **Validation**: Run tests to ensure no regressions. Verify the development plan is accurate.
 
       Do not add new features.
-    transitions:
-      - trigger: 'commit_complete'
-        to: 'questions'
-        transition_reason: 'Feature delivered, ready for next task'
 
-      - trigger: 'need_code_changes'
-        to: 'implement'
-        additional_instructions: 'Fix the problems identified during final review.'
-        transition_reason: 'Final review found issues requiring code changes'
-
-      - trigger: 'abandon_feature'
-        to: 'questions'
-        instructions: 'Feature abandoned. Clean up artifacts and reset for new tasks.'
-        transition_reason: 'User abandoned feature during finalization'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/skilled-bugfix.yaml

@@ -158,17 +158,6 @@ states:
       - Verify documentation accuracy with a final review
       - Ensure bug fix is ready for production
       - Update task progress and mark completed work as you finalize the bug fix
-    transitions:
-      - trigger: 'need_fix_changes'
-        to: 'fix'
-        additional_instructions: 'Finalization revealed issues with the bug fix. Focus on addressing the specific problems identified during final review.'
-        transition_reason: 'Finalization revealed issues requiring fix changes'
-
-      - trigger: 'finalization_complete'
-        to: 'reproduce'
-        transition_reason: 'Bug fix complete and finalized, ready for next issue'
 
-      - trigger: 'abandon_bug'
-        to: 'reproduce'
-        additional_instructions: 'Bug finalization abandoned. Clean up any finalization work and prepare for new bug reports.'
-        transition_reason: 'Bug finalization abandoned'
+      $DONE_DEFAULT
+    transitions: []

package/packages/cli/resources/workflows/skilled-epcc.yaml

@@ -155,17 +155,6 @@ states:
       - Ensure code is ready for production/delivery
 
       Update task progress and mark completed work as you finalize the feature.
-    transitions:
-      - trigger: 'need_code_changes'
-        to: 'code'
-        additional_instructions: 'Focus on the problems identified during final review.'
-        transition_reason: 'Final review found issues requiring code changes'
-
-      - trigger: 'commit_complete'
-        to: 'explore'
-        transition_reason: 'Feature 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 feature during finalization'
+      $DONE_DEFAULT
+    transitions: []