fix(workflows): remove abandon-triggers

.vibe/workflows/my-posts.yaml

@@ -46,14 +46,6 @@ states:
           Update the plan file with story development tasks and mark completed discovery work.
         transition_reason: 'Topic researched and format decided, ready for story structure development'
 
-      - trigger: abandon_post
-        to: discovery
-        instructions: |
-          Post development abandoned. Clean up any discovery work and prepare for new post topics.
-          The plan file will remain for future reference if needed.
-        additional_instructions: 'Post development abandoned. Prepare for new post topics.'
-        transition_reason: 'User decided to abandon current post development'
-
   story:
     description: 'Create narrative structure and story outline'
     default_instructions: |
@@ -84,14 +76,6 @@ states:
         additional_instructions: 'Story development revealed gaps in research or format clarity. Focus on clarifying these foundational aspects.'
         transition_reason: 'Story work revealed need for additional discovery or research'
 
-      - trigger: abandon_post
-        to: discovery
-        instructions: |
-          Post development abandoned 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: 'Post abandoned during story phase. 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: |
@@ -123,14 +107,6 @@ states:
         additional_instructions: 'Writing revealed issues with story structure or narrative flow. Focus on refining the story foundation.'
         transition_reason: 'Content creation revealed need for story structure refinement'
 
-      - trigger: abandon_post
-        to: discovery
-        instructions: |
-          Post development abandoned during writing. Clean up writing work and return to discovery.
-          The plan file and any completed work will remain for future reference.
-        additional_instructions: 'Post abandoned during writing phase. 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: |
@@ -162,14 +138,6 @@ states:
         additional_instructions: 'Illustration work revealed gaps in written content. Focus on completing the content foundation.'
         transition_reason: 'Visual work revealed need for additional written content'
 
-      - trigger: abandon_post
-        to: discovery
-        instructions: |
-          Post development abandoned during illustration. Clean up illustration work and return to discovery.
-          The plan file and any completed work will remain for future reference.
-        additional_instructions: 'Post abandoned during illustration phase. 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: |
@@ -197,11 +165,3 @@ states:
         to: illustration
         additional_instructions: 'Distribution preparation revealed issues with visuals or content presentation. Focus on final refinements.'
         transition_reason: 'Publishing preparation identified issues requiring visual or content refinement'
-
-      - trigger: abandon_post
-        to: discovery
-        instructions: |
-          Post development abandoned before distribution. Clean up distribution preparation and return to discovery.
-          The plan file and completed work will remain for future reference.
-        additional_instructions: 'Post abandoned before distribution. Clean up and prepare for new topics.'
-        transition_reason: 'User decided to abandon post before distribution'

.vibe/workflows/tdd.yaml

@@ -39,14 +39,6 @@ states:
         additional_instructions: 'Mark completed exploration tasks.'
         transition_reason: 'Sufficient understanding gained, ready to start TDD cycle with failing test'
 
-      - trigger: 'abandon_feature'
-        to: 'explore'
-        instructions: >
-          Feature development abandoned. Return to exploration state for new tasks.
-          The plan file will remain for future reference if needed.
-        additional_instructions: 'Clean up any work in progress and prepare for new tasks.'
-        transition_reason: 'User decided to abandon current feature development'
-
   red:
     description: 'RED phase - Write a failing test that defines the expected behavior'
     default_instructions: |
@@ -73,11 +65,6 @@ states:
         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: |
@@ -111,11 +98,6 @@ states:
         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: |
@@ -150,8 +132,3 @@ states:
         to: 'explore'
         additional_instructions: 'Mark feature as complete in plan file.'
         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'

resources/workflows/bugfix.yaml

@@ -67,11 +67,6 @@ states:
           - perspective: 'security_expert'
             prompt: "Evaluate if the bug has security implications and ensure the fix doesn't introduce new vulnerabilities. Review the security aspects of the proposed solution."
 
-      - trigger: 'abandon_bug'
-        to: 'reproduce'
-        additional_instructions: 'Bug analysis abandoned. Clean up any analysis work and prepare for new bug reports.'
-        transition_reason: 'Bug analysis abandoned'
-
   fix:
     description: 'Implement the bug fix'
     allowed_file_patterns:
@@ -103,11 +98,6 @@ states:
           - perspective: 'performance_engineer'
             prompt: "Verify that the fix doesn't introduce performance regressions or new bottlenecks. Assess the performance impact of the implemented solution."
 
-      - trigger: 'abandon_bug'
-        to: 'reproduce'
-        additional_instructions: 'Bug fix abandoned. Clean up any fix work and prepare for new bug reports.'
-        transition_reason: 'Bug fix abandoned'
-
   verify:
     description: 'Verify the fix and ensure no regressions'
     allowed_file_patterns:
@@ -128,11 +118,6 @@ states:
         to: 'finalize'
         transition_reason: 'Bug fix complete and verified, ready for next issue'
 
-      - trigger: 'abandon_bug'
-        to: 'reproduce'
-        additional_instructions: 'Bug verification abandoned. Clean up any verification work and prepare for new bug reports.'
-        transition_reason: 'Bug verification abandoned'
-
   finalize:
     description: 'Code cleanup and documentation finalization'
     allowed_file_patterns:

resources/workflows/epcc.yaml

@@ -82,14 +82,6 @@ states:
           - perspective: 'security_expert'
             prompt: 'Assess security considerations and potential risks in the planned implementation approach. Review data handling, authentication, and potential vulnerabilities.'
 
-      - trigger: 'abandon_feature'
-        to: 'explore'
-        instructions: >
-          Feature development abandoned during planning. Return to exploration state for new tasks.
-          Task history will remain for future reference.
-        additional_instructions: 'Feature development abandoned during planning. Clean up any planning work and prepare for new tasks.'
-        transition_reason: 'User decided to abandon feature during planning phase'
-
   code:
     description: 'Implementation phase - writing and building the solution'
     allowed_file_patterns:
@@ -125,14 +117,6 @@ states:
           - perspective: 'performance_engineer'
             prompt: 'Evaluate performance impact, resource efficiency, and scalability of the implemented solution. Check for potential bottlenecks or optimization opportunities.'
 
-      - trigger: 'abandon_feature'
-        to: 'explore'
-        instructions: >
-          Feature development 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 feature during implementation'
-
   commit:
     description: 'Code cleanup and documentation finalization'
     allowed_file_patterns:

resources/workflows/greenfield.yaml

@@ -80,14 +80,6 @@ states:
           - 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'
     allowed_file_patterns:
@@ -120,14 +112,6 @@ states:
         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'
     allowed_file_patterns:
@@ -155,14 +139,6 @@ states:
         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'
     allowed_file_patterns:

resources/workflows/minor.yaml

@@ -81,14 +81,6 @@ states:
         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'
     allowed_file_patterns:

resources/workflows/posts.yaml

@@ -75,14 +75,6 @@ states:
         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: |
@@ -115,14 +107,6 @@ states:
         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: |
@@ -153,14 +137,6 @@ states:
         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: |

resources/workflows/qrspi.yaml

@@ -47,11 +47,6 @@ states:
         to: 'research'
         transition_reason: 'Intent clarified, ready to gather facts'
 
-      - trigger: 'abandon_feature'
-        to: 'questions'
-        instructions: 'Feature abandoned. Reset for new tasks.'
-        transition_reason: 'User abandoned feature during questions'
-
   research:
     description: 'Gather facts without forming conclusions or proposing solutions'
     allowed_file_patterns:
@@ -74,11 +69,6 @@ states:
         additional_instructions: 'Focus on the specific areas where intent is still unclear.'
         transition_reason: 'Research revealed gaps in understanding'
 
-      - trigger: 'abandon_feature'
-        to: 'questions'
-        instructions: 'Feature abandoned. Reset for new tasks.'
-        transition_reason: 'User abandoned feature during research'
-
   design:
     description: 'Explore options and reach consensus on WHAT and high-level HOW'
     allowed_file_patterns:
@@ -107,11 +97,6 @@ states:
         additional_instructions: 'Focus on the specific gaps that block design consensus.'
         transition_reason: 'Design discussion revealed need for more research'
 
-      - trigger: 'abandon_feature'
-        to: 'questions'
-        instructions: 'Feature abandoned. Reset for new tasks.'
-        transition_reason: 'User abandoned feature during design'
-
   structure:
     description: 'Decompose the approved design into end-to-end vertical slices'
     allowed_file_patterns:
@@ -136,11 +121,6 @@ states:
         additional_instructions: 'The design approach makes slicing difficult. Revisit the high-level approach with the user.'
         transition_reason: 'Structure work revealed design gaps'
 
-      - trigger: 'abandon_feature'
-        to: 'questions'
-        instructions: 'Feature abandoned. Reset for new tasks.'
-        transition_reason: 'User abandoned feature during structure'
-
   plan:
     description: 'Create a detailed implementation plan per vertical slice'
     allowed_file_patterns:
@@ -175,11 +155,6 @@ states:
         additional_instructions: 'The slice boundaries are wrong. Redefine the vertical slices.'
         transition_reason: 'Planning revealed flaws in slice boundaries'
 
-      - trigger: 'abandon_feature'
-        to: 'questions'
-        instructions: 'Feature abandoned. Reset for new tasks.'
-        transition_reason: 'User abandoned feature during planning'
-
   implement:
     description: 'Build the solution slice by slice'
     allowed_file_patterns:
@@ -217,11 +192,6 @@ states:
         additional_instructions: 'Focus on the specific areas blocking implementation progress.'
         transition_reason: 'Implementation revealed need for more research'
 
-      - trigger: 'abandon_feature'
-        to: 'questions'
-        instructions: 'Feature abandoned. Clean up incomplete code and reset for new tasks.'
-        transition_reason: 'User abandoned feature during implementation'
-
   commit:
     description: 'Cleanup, documentation finalization, and delivery'
     allowed_file_patterns:

resources/workflows/sdd-bugfix-crowd.yaml

@@ -601,8 +601,3 @@ states:
 
 # Global transitions
 global_transitions:
-  - trigger: 'abandon_bugfix'
-    to: 'reproduce'
-    transition_reason: 'Bug fix abandoned, restart from beginning'
-    additional_instructions: |
-      Bug fix abandoned. If you want to restart, begin again with reproducing and understanding the bug.

resources/workflows/sdd-bugfix.yaml

@@ -374,8 +374,3 @@ states:
 
 # Global transitions available from any state
 global_transitions:
-  - trigger: 'abandon_bugfix'
-    to: 'reproduce'
-    instructions: >
-      If you want to restart, you'll begin again with reproducing and understanding the bug.
-    transition_reason: 'Bug fix abandoned, restart from beginning'

resources/workflows/sdd-feature-crowd.yaml

@@ -706,8 +706,3 @@ states:
 
 # Global transitions available from any state
 global_transitions:
-  - trigger: 'abandon_feature'
-    to: 'analyze'
-    transition_reason: 'Feature abandoned, restart from beginning'
-    additional_instructions: |
-      If you want to restart, begin again by analyzing the requirements and current state.

resources/workflows/sdd-feature.yaml

@@ -463,9 +463,3 @@ states:
 
 # Global transitions available from any state
 global_transitions:
-  - trigger: 'abandon_feature'
-    to: 'analyze'
-    instructions: >
-      Feature development abandoned. If you want to restart, you'll begin again with
-      analyzing the requirements and current state.
-    transition_reason: 'Feature abandoned, restart from beginning'