@codemcp/workflows-core 4.5.0 → 4.6.0

package/resources/workflows/business-analysis.yaml

@@ -40,10 +40,10 @@ states:
       IMPORTANT: In this phase, do not read the documents yet!
 
       **Step 2: Create Document Processing Tasks**
-      For each gathered document, add task to plan file:
+      For each gathered document, create a processing task:
       "- [ ] Summarize [document-name] using structured chapter-by-chapter approach"
 
-      Update plan file with discovery progress and processing tasks.
+      Update task progress and create document processing tasks.
     transitions:
       - trigger: 'discovery_complete'
         to: 'documents_consolidation'
@@ -61,7 +61,7 @@ states:
       2. Maintain original hierarchical structure
       3. Condense content while preserving key information
       4. Create [document-name]-processed.md file
-      5. Mark task complete in plan file
+      5. Update task progress as complete
 
       **Summarization Guidelines:**
       - Create structured summary based exclusively on source document information
@@ -97,10 +97,10 @@ states:
       - Business rules and policies
 
       **Step 2: Create Business Analysis Tasks**
-      For each business-relevant chapter identified, add a task to the plan file:
-      "- [ ] Create detailed business analysis of [document-name] Chapter [X]: [chapter-title]"
+      For each business-relevant chapter identified, create a task:
+      "- [ ] Extract business capabilities from [chapter-name]"
 
-      IMPORTANT: You MUST add these tasks to the plan file before proceeding.
+      IMPORTANT: You MUST create these tasks before proceeding.
 
       **Step 3: Execute Business Analysis Tasks**
       For each business analysis task:
@@ -111,7 +111,7 @@ states:
          - Who (roles/actors) performs the work
          - Why (business value/purpose) it exists
       3. Create detailed business summary emphasizing WHAT, WHY, WHO (not HOW)
-      4. Mark task complete in plan file
+      4. Update task progress as complete
 
       **Step 4: Update Bibliography**
       Update BIBLIOGRAPHY.md with business terms found during detailed analysis:
@@ -252,7 +252,7 @@ states:
             - business-analysis/business-actors/ (folder for details)
 
           Begin analyzing processed documents to identify business capabilities and domains.
-          Mark completed business analysis tasks in plan file.
+          Update task progress as you complete business analysis work.
         transition_reason: 'Business content analysis complete, ready for capability identification'
 
   capability_identification:
@@ -299,7 +299,7 @@ states:
       - trigger: 'capabilities_identified'
         to: 'capability_decomposition'
         additional_instructions: >
-          For each identified capability, add decomposition tasks to plan file:
+          For each identified capability, create decomposition tasks:
           "- [ ] Decompose [capability-name] into sub-capabilities using document analysis"
 
           Begin systematic decomposition of capabilities one at a time.
@@ -362,11 +362,11 @@ states:
           <!-- Key organizational units and their responsibilities -->
           ```
 
-          For each capability, add actor analysis tasks to plan file:
+          For each capability, create actor analysis tasks:
           "- [ ] Analyze business actors for [capability-name] using document analysis"
 
           Begin systematic actor analysis one capability at a time.
-          Mark completed decomposition tasks in plan file.
+          Update task progress as you complete decomposition work.
         transition_reason: 'Capability decomposition complete, ready for actor analysis'
 
   actor_analysis:
@@ -375,7 +375,7 @@ states:
       You are in the actor analysis phase. Identify WHO performs each capability using Business Capability Modeling approach.
 
       **Step 1: Select Next Capability for Actor Analysis**
-      From plan file, select the next capability to analyze for business actors.
+      From current tasks, select the next capability to analyze for business actors.
 
       **Step 2: Analyze Documents for Business Actors**
       Review processed documents to identify:
@@ -403,7 +403,7 @@ states:
 
       **Step 5: Refine and Document**
       Update business-actors.md with capability-actor mappings.
-      Mark task complete in plan file.
+      Update task progress as complete.
 
       Focus on capability ownership and role accountability, not just organizational structure.
 
@@ -429,11 +429,11 @@ states:
           <!-- How processes relate to the actors identified -->
           ```
 
-          For each capability, add process analysis tasks to plan file:
+          For each capability, create process analysis tasks:
           "- [ ] Analyze business processes for [capability-name] using document analysis and actor context"
 
           Begin systematic process analysis one capability at a time.
-          Mark completed actor analysis tasks in plan file.
+          Update task progress as you complete actor analysis work.
         transition_reason: 'Actor analysis complete, ready for process analysis'
 
   process_analysis:
@@ -442,7 +442,7 @@ states:
       You are in the process analysis phase. Create process analysis tasks for systematic processing.
 
       **Step 1: Select Next Process Analysis Task**
-      From plan file process analysis tasks, select the next capability to process.
+      From current process analysis tasks, select the next capability to process.
 
       **Step 2: Analyze Documents for Process Information**
       Review processed documents for process information:
@@ -470,7 +470,7 @@ states:
 
       **Step 5: Refine and Document**
       Update business-processes-detailed.md and detail folder.
-      Mark task complete in plan file.
+      Update task progress as complete.
 
       Process one capability's processes at a time.
     transitions:
@@ -559,7 +559,7 @@ states:
           - All three formats (comprehensive)"
 
           Begin creating consolidated summaries and illustrations.
-          Mark completed consistency tasks in plan file.
+          Update task progress as you complete consistency work.
         transition_reason: 'Consistency validation complete, ready for final summary creation'
 
   summary:
@@ -620,7 +620,7 @@ states:
           - Navigation guides and cross-references
 
           The analysis provides complete business architecture understanding using Business Capability Modeling methodology.
-          Mark completed summary tasks in plan file.
+          Update task progress as you complete summary work.
         transition_reason: 'Summary creation complete, analysis finished'
 
   analysis_complete:

package/resources/workflows/epcc.yaml

@@ -29,24 +29,16 @@ states:
     default_instructions: |
       You are in the exploration phase. Research the codebase, understand existing patterns, and gather context about the problem space.
       If you are not certain about conventions or rules, ask the user about them.
-      Read relevant files and documentation. If $REQUIREMENTS_DOC exists, understand and document requirements there, otherwise document them in the plan file. Don't write code yet - focus on understanding. Document your findings in the plan file.
+      Read relevant files and documentation. If $REQUIREMENTS_DOC exists, understand and document requirements there, otherwise document them in your task management system. Don't write code yet - focus on understanding. Document your findings and create tasks as needed.
     transitions:
       - trigger: 'exploration_complete'
         to: 'plan'
         additional_instructions: 'Present the plan to the user, describing the impact of the changes.'
         transition_reason: 'Sufficient understanding gained, ready to create implementation plan'
 
-      - 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: 'Feature development abandoned. Clean up any work in progress and prepare for new tasks.'
-        transition_reason: 'User decided to abandon current feature development'
-
   plan:
     description: 'Planning phase - creating a detailed implementation strategy'
-    default_instructions: 'You are in the planning phase. Create a detailed implementation strategy based on your exploration. If $REQUIREMENTS_DOC exists, base your strategy on requirements from $REQUIREMENTS_DOC, otherwise use the plan file context. Break down the work into specific, actionable tasks. Consider edge cases, dependencies, and potential challenges. If it impacts the general architecture and $ARCHITECTURE_DOC exists, document this in $ARCHITECTURE_DOC, otherwise use the plan file. If $DESIGN_DOC exists, make sure to adhere to the design in $DESIGN_DOC. Document the plan thoroughly. Important: Tasks that you identify for the actual coding shall be in the Code section in the plan.'
+    default_instructions: 'You are in the planning phase. Create a detailed implementation strategy based on your exploration. If $REQUIREMENTS_DOC exists, base your strategy on requirements from $REQUIREMENTS_DOC, otherwise use existing task context. Break down the work into specific, actionable tasks. Consider edge cases, dependencies, and potential challenges. If it impacts the general architecture and $ARCHITECTURE_DOC exists, document this in $ARCHITECTURE_DOC, otherwise create tasks to track architectural decisions. If $DESIGN_DOC exists, make sure to adhere to the design in $DESIGN_DOC. Document the planning work thoroughly and create implementation tasks as needed.'
     transitions:
       - trigger: 'need_more_exploration'
         to: 'explore'
@@ -66,13 +58,13 @@ states:
         to: 'explore'
         instructions: >
           Feature development abandoned during planning. Return to exploration state for new tasks.
-          The plan file will remain for future reference.
+          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'
-    default_instructions: 'You are in the implementation phase. Follow your plan and if $DESIGN_DOC exists, follow the design from $DESIGN_DOC to build the solution. If $ARCHITECTURE_DOC exists, build according to the architecture in $ARCHITECTURE_DOC. If $REQUIREMENTS_DOC exists, ensure requirements from $REQUIREMENTS_DOC are met, otherwise ensure plan file requirements 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. Update progress in the plan file. Important: Tasks that you identify for the actual coding shall be in the Code section in the plan.'
+    default_instructions: 'Follow your plan and if $DESIGN_DOC exists, follow the design from $DESIGN_DOC to build the solution. If $ARCHITECTURE_DOC exists, build according to the architecture in $ARCHITECTURE_DOC. If $REQUIREMENTS_DOC exists, ensure requirements from $REQUIREMENTS_DOC are met, otherwise ensure existing requirements are met based on your task context. 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. Update task progress and create new tasks as needed for implementation work.'
     transitions:
       - trigger: 'need_replanning'
         to: 'plan'
@@ -97,7 +89,7 @@ states:
         to: 'explore'
         instructions: >
           Feature development abandoned during implementation. Clean up any incomplete code and return to exploration.
-          The plan file and any completed work will remain for future reference.
+          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'
 
@@ -141,7 +133,7 @@ states:
       - Verify documentation accuracy with a final review
       - Ensure code is ready for production/delivery
 
-      Update the plan file with commit progress and mark completed tasks.
+       Update task progress and mark completed work as you finalize the feature.
     transitions:
       - trigger: 'need_code_changes'
         to: 'code'

package/resources/workflows/greenfield.yaml

@@ -34,7 +34,7 @@ states:
       • 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 the plan file.
+       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'
@@ -49,7 +49,7 @@ states:
         to: 'ideation'
         instructions: >
           Project development abandoned. Return to ideation state for new projects.
-          The plan file will remain for future reference if needed.
+          Task history will remain for future reference if needed.
         additional_instructions: 'Project development abandoned. Clean up any ideation work and prepare for new projects.'
         transition_reason: 'User decided to abandon current project development'
 
@@ -76,13 +76,13 @@ states:
         to: 'ideation'
         instructions: >
           Project development abandoned during architecture phase. Return to ideation state for new projects.
-          The plan file and PRD will remain for future reference.
+          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: 'You are in the planning phase. Based on your completed architecture in $ARCHITECTURE_DOC and requirements from $REQUIREMENTS_DOC, create a detailed implementation strategy. Break down the work into specific, actionable tasks considering the chosen tech stack and architectural decisions. Plan the implementation order, identify dependencies, and consider potential risks. Document the detailed design in $DESIGN_DOC and the plan thoroughly with clear milestones. Important: Tasks for the actual coding should be organized in the Code section of the plan.'
+    default_instructions: 'You are in the planning phase. Based on your completed architecture in $ARCHITECTURE_DOC and requirements from $REQUIREMENTS_DOC, create a detailed implementation strategy. Break down the work into specific, actionable tasks considering the chosen tech stack and architectural decisions. Plan the implementation order, identify dependencies, and consider potential risks. Document the detailed design in $DESIGN_DOC and create tasks thoroughly with clear milestones for implementation work.'
     transitions:
       - trigger: 'need_architecture_changes'
         to: 'architecture'
@@ -91,20 +91,20 @@ states:
 
       - 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. Mark completed planning tasks."
+        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.
-          The plan file, PRD, and architecture documentation will remain for future reference.
+          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: 'You are in the implementation phase. Follow your plan and detailed design from $DESIGN_DOC to build the solution 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 progress in the plan file. Important: Focus on tasks in the Code section of your plan.'
+    default_instructions: 'Follow your plan and detailed design from $DESIGN_DOC to build the solution 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'
@@ -124,7 +124,7 @@ states:
         to: 'ideation'
         instructions: >
           Project development abandoned during implementation. Clean up any incomplete code and return to ideation.
-          The plan file, PRD, architecture documentation, and any completed work will remain for future reference.
+          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'
 
@@ -169,7 +169,7 @@ states:
       - Verify documentation accuracy with a final review
       - Ensure project is ready for users and contributors
 
-      Update the plan file with finalization progress and mark completed tasks.
+       Update task progress and mark completed work as you finalize the project.
     transitions:
       - trigger: 'need_code_changes'
         to: 'code'

package/resources/workflows/minor.yaml

@@ -30,8 +30,8 @@ states:
       You are in the exploration phase for minor enhancement.
       This phase should be efficient since it's a minor enhancement.
       Understand the problem, analyze existing patterns, and design your approach.
-      Consider the scope and impact of the change. If $REQUIREMENTS_DOC exists, document requirements there, otherwise document them in the plan file. If $DESIGN_DOC exists, respect the design approach in $DESIGN_DOC.
-      Document your analysis and design decisions in the plan file.
+       Consider the scope and impact of the change. If $REQUIREMENTS_DOC exists, document requirements there, otherwise document them in your task management system. If $DESIGN_DOC exists, respect the design approach in $DESIGN_DOC.
+       Document your analysis and design decisions and create tasks as needed.
       Focus on analysis and design only - do not write any code yet.
     transitions:
       - trigger: 'exploration_complete'
@@ -43,13 +43,13 @@ states:
         instructions: >
           Minor enhancement abandoned. Revert potentially made changes.
           Return to exploration state for new tasks.
-          The plan file will remain for future reference if needed.
+          Task history will remain for future reference if needed.
         additional_instructions: 'Minor enhancement development abandoned. Clean up any analysis work and prepare for new tasks.'
         transition_reason: 'User decided to abandon current minor enhancement'
 
   implement:
     description: 'Combined implementation phase - code, test, and commit'
-    default_instructions: "You are in the implementation phase for minor enhancement. This phase combines coding, testing, and commit preparation. If $DESIGN_DOC exists, follow your design from $DESIGN_DOC. If $REQUIREMENTS_DOC exists, ensure the relevant requirements from $REQUIREMENTS_DOC are met, otherwise ensure plan file requirements are met. Write clean, focused code for the minor enhancement. Test your changes to ensure they work correctly and don't break existing functionality. Prepare documentation and commit when ready. Update progress in the plan file."
+    default_instructions: "This phase combines coding, testing, and commit preparation. If $DESIGN_DOC exists, follow your design from $DESIGN_DOC. If $REQUIREMENTS_DOC exists, ensure the relevant requirements from $REQUIREMENTS_DOC are met, otherwise ensure existing requirements are met based on your task context. Write clean, focused code for the minor enhancement. Test your changes to ensure they work correctly and don't break existing functionality. Prepare documentation and commit when ready. Update task progress as needed."
     transitions:
       - trigger: 'need_more_analysis'
         to: 'explore'
@@ -64,7 +64,7 @@ states:
         to: 'explore'
         instructions: >
           Minor enhancement abandoned during implementation. Clean up any incomplete code and return to exploration.
-          The plan file and any completed work will remain for future reference.
+          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'
 
@@ -107,7 +107,7 @@ states:
       - Verify documentation accuracy with a final review
       - Ensure minor enhancement is ready for delivery
 
-      Update the plan file with finalization progress and mark completed tasks.
+       Update task progress and mark completed work as you finalize the minor enhancement.
     transitions:
       - trigger: 'need_implementation_changes'
         to: 'implement'

package/resources/workflows/tdd.yaml

@@ -31,19 +31,19 @@ states:
       Your main objective now is to gather context about what needs to be developed. Focus on the WHY and WHAT, not the HOW.
       Research the codebase, understand existing patterns,
       If you are not certain about conventions or rules, ask the user about them.
-      Read relevant files and documentation. If $REQUIREMENTS_DOC exists, understand and document requirements there, otherwise document them in the plan file.
-      Don't write code or tests yet - focus on understanding. Document your findings in the plan file.
+       Read relevant files and documentation. If $REQUIREMENTS_DOC exists, understand and document requirements there, otherwise document them in your task management system.
+       Don't write code or tests yet - focus on understanding. Document your findings and create tasks as needed.
     transitions:
       - trigger: 'exploration_complete'
         to: 'red'
-        additional_instructions: 'Mark completed exploration tasks.'
+        additional_instructions: 'Update task progress as you complete exploration work.'
         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.
+          Task history 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'
 
@@ -62,11 +62,11 @@ states:
       - Is specific and focused on one aspect of the functionality
       - Uses appropriate assertions (not assert(true) or similar meaningless checks)
 
-      Run the test to confirm it fails for the right reason. Document the test in the plan file.
+       Run the test to confirm it fails for the right reason. Document the test and update task progress as needed.
     transitions:
       - trigger: 'test_written_and_failing'
         to: 'green'
-        additional_instructions: 'Mark completed test tasks.'
+        additional_instructions: 'Update task progress as you complete test writing work.'
         transition_reason: 'Failing test successfully written and validated, ready to implement'
 
       - trigger: 'need_more_exploration'
@@ -96,11 +96,11 @@ states:
       - Implementing proper logic, not shortcuts
       - Running the test to confirm it passes
 
-      Document your implementation approach in the plan file.
+       Document your implementation approach and update task progress as needed.
     transitions:
       - trigger: 'test_passing'
         to: 'refactor'
-        additional_instructions: 'Mark completed implementation tasks.'
+        additional_instructions: 'Update task progress as you complete implementation work.'
         transition_reason: 'Test passes with proper implementation, ready for refactoring'
 
       - trigger: 'need_different_test'
@@ -135,11 +135,11 @@ states:
       - Make small, incremental improvements
       - Stop when code is clean and no obvious improvements remain
 
-      Document significant refactoring decisions in the plan file.
+       Document significant refactoring decisions and update task progress as needed.
     transitions:
       - trigger: 'refactoring_complete'
         to: 'red'
-        additional_instructions: 'Mark completed refactoring tasks.'
+        additional_instructions: 'Update task progress as you complete refactoring work.'
         transition_reason: 'Code cleanup complete, ready for next TDD cycle'
 
       - trigger: 'need_different_approach'
@@ -148,7 +148,7 @@ states:
 
       - trigger: 'feature_complete'
         to: 'explore'
-        additional_instructions: 'Mark feature as complete in plan file.'
+        additional_instructions: 'Update task progress to reflect feature completion.'
         transition_reason: 'Feature fully implemented and cleaned up, ready for new tasks'
 
       - trigger: 'abandon_feature'

package/resources/workflows/waterfall.yaml

@@ -35,7 +35,7 @@ states:
       • How will you measure success? What are the acceptance criteria?
       • What are your time, budget, technical, or regulatory constraints?
       • What existing systems must this integrate with?
-      Break down their needs into specific requirements in $REQUIREMENTS_DOC. Plan actionable tasks referencing those requirements in the plan file.
+       Break down their needs into specific requirements in $REQUIREMENTS_DOC. Create actionable tasks referencing those requirements.
     transitions:
       - trigger: 'requirements_complete'
         to: 'design'
@@ -53,7 +53,7 @@ states:
       Review requirements from $REQUIREMENTS_DOC and design the technical solution
       Focus on HOW to implement what's needed including architecture, technologies, data models, API design, and quality goals.
       Clarify performance expectations and technology preferences if not already obvious from the current analysis.
-      Document architectural decisions in $ARCHITECTURE_DOC and detailed design in $DESIGN_DOC. Update the plan file and ensure the approach is solid before implementation."
+       Document architectural decisions in $ARCHITECTURE_DOC and detailed design in $DESIGN_DOC. Create tasks and ensure the approach is solid before implementation."
     transitions:
       - trigger: 'need_more_requirements'
         to: 'requirements'
@@ -72,10 +72,10 @@ states:
   implementation:
     description: 'Building the solution according to design'
     default_instructions: |
-      You are in the implementation phase. Follow the architecture from $ARCHITECTURE_DOC and detailed design from $DESIGN_DOC to build the solution. Before starting, clarify the approach:
+      Follow the architecture from $ARCHITECTURE_DOC and detailed design from $DESIGN_DOC to build the solution. Before starting, clarify the approach:
       • Should this be implemented incrementally or all at once? Any specific order of implementation?
       • Are there high-risk parts that need extra validation or careful implementation?
-      Ensure requirements from $REQUIREMENTS_DOC are met. 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.
+       Ensure requirements from $REQUIREMENTS_DOC are met. Focus on code structure, error handling, security, and maintainability. Write clean, well-documented code and include basic testing. Update task progress during implementation work.
     transitions:
       - trigger: 'need_design_changes'
         to: 'design'
@@ -98,7 +98,7 @@ states:
 
   qa:
     description: 'Quality assurance and code review'
-    default_instructions: 'You are in the quality assurance phase. Take the following specific actions: 1) Syntax Check: Run syntax checking tools or validate syntax manually, 2) Build Project: Build the project to verify it compiles without errors, 3) Run Linter: Execute linting tools to ensure code style consistency, 4) Execute Tests: Run existing tests to verify functionality. Then conduct a multi-perspective code review from security, performance, UX, maintainability, and requirement compliance perspectives. Verify implementation matches $DESIGN_DOC specifications and fulfills the targeted requirements from $REQUIREMENTS_DOC. Update the plan file with QA progress and mark completed tasks.'
+    default_instructions: 'You are in the quality assurance phase. Take the following specific actions: 1) Syntax Check: Run syntax checking tools or validate syntax manually, 2) Build Project: Build the project to verify it compiles without errors, 3) Run Linter: Execute linting tools to ensure code style consistency, 4) Execute Tests: Run existing tests to verify functionality. Then conduct a multi-perspective code review from security, performance, UX, maintainability, and requirement compliance perspectives. Verify implementation matches $DESIGN_DOC specifications and fulfills the targeted requirements from $REQUIREMENTS_DOC. Update task progress and mark completed work during QA review.'
     transitions:
       - trigger: 'need_implementation_fixes'
         to: 'implementation'
@@ -177,7 +177,7 @@ states:
       - Verify documentation accuracy with a final review
       - Ensure code is ready for production/delivery
 
-      Update the plan file with finalization progress and mark completed tasks.
+       Update task progress and mark completed work as you finalize the feature.
     transitions:
       - trigger: 'need_final_changes'
         to: 'implementation'