@codemcp/workflows 6.18.4 → 6.20.0

package/packages/visualizer/dist/services/workflow-list.ts

@@ -12,6 +12,7 @@ export const workflowList = [
   'minor',
   'posts',
   'pr-review',
+  'qrspi',
   'sdd-bugfix',
   'sdd-bugfix-crowd',
   'sdd-feature',

package/packages/visualizer/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemcp/workflows-visualizer",
-  "version": "6.18.4",
+  "version": "6.20.0",
   "type": "module",
   "main": "dist/index.ts",
   "module": "dist/index.ts",

package/resources/state-machine-schema.json

@@ -51,6 +51,10 @@
           "type": "boolean",
           "description": "Whether this workflow requires project documentation (architecture, requirements, design) to be set up before starting. Defaults to false for backwards compatibility.",
           "default": false
+        },
+        "domain": {
+          "type": "string",
+          "description": "Domain or category of the workflow (e.g., code, architecture, office, skilled)"
         }
       }
     },
@@ -71,6 +75,13 @@
           "type": "string",
           "description": "Description of this state"
         },
+        "allowed_file_patterns": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "description": "Glob patterns for files that can be edited in this state. Use '**/*' to allow all files."
+        },
         "default_instructions": {
           "type": "string",
           "description": "Default instructions when entering this state"
@@ -107,6 +118,24 @@
         "transition_reason": {
           "type": "string",
           "description": "Reason for this transition"
+        },
+        "review_perspectives": {
+          "type": "array",
+          "description": "Optional review perspectives to apply when this transition is taken",
+          "items": {
+            "type": "object",
+            "required": ["perspective", "prompt"],
+            "properties": {
+              "perspective": {
+                "type": "string",
+                "description": "Name of the review perspective (e.g., architect, security_expert)"
+              },
+              "prompt": {
+                "type": "string",
+                "description": "Prompt or instructions for the review perspective"
+              }
+            }
+          }
         }
       }
     }

package/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/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/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/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/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/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/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/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/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/resources/workflows/qrspi.yaml

@@ -0,0 +1,241 @@
+# yaml-language-server: $schema=../state-machine-schema.json
+---
+name: 'qrspi'
+description: 'Questions, Research, Design, Structure, Plan, Implement — for creative, complex challenges requiring deep alignment before execution'
+initial_state: 'questions'
+
+metadata:
+  domain: 'code'
+  complexity: 'high'
+  bestFor:
+    - 'Creative or complex challenges'
+    - 'Deep alignment before execution'
+    - 'Unconventional problems'
+    - 'Architecture-heavy features'
+    - 'High-stakes changes'
+  useCases:
+    - 'Designing a novel system architecture'
+    - 'Implementing complex multi-domain features'
+    - 'Solving problems with unclear requirements'
+    - 'Building features requiring extensive stakeholder alignment'
+    - 'Refactoring core infrastructure'
+  examples:
+    - 'Design and implement a new plugin architecture'
+    - 'Create a custom workflow engine with validation'
+    - 'Refactor monolith to modular services'
+    - 'Build a creative AI-powered feature with novel UX'
+
+states:
+  questions:
+    description: 'Clarify intent, scope, and success criteria before any exploration'
+    allowed_file_patterns:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.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.
+    transitions:
+      - trigger: 'questions_answered'
+        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:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
+    default_instructions: |
+      **Principle**: Gather facts before forming opinions.
+
+      Explore the codebase, patterns, and relevant documentation. Document findings as facts (not opinions) in the development plan. Highlight what requires design decisions. Use `$REQUIREMENTS_DOC` as context only — do not modify it.
+
+      Do not propose solutions, make design decisions, or write code.
+    transitions:
+      - trigger: 'research_complete'
+        to: 'design'
+        transition_reason: 'Facts gathered, ready for design discussion'
+
+      - trigger: 'need_more_questions'
+        to: 'questions'
+        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:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.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.
+
+      Do not plan detailed implementation or write code.
+    transitions:
+      - trigger: 'design_approved'
+        to: 'structure'
+        transition_reason: 'Design direction approved, ready to decompose'
+        review_perspectives:
+          - perspective: 'product_owner'
+            prompt: 'Review whether the proposed design aligns with user goals, business value, and intended outcomes. Ensure the solution direction serves the actual need.'
+
+      - trigger: 'need_research'
+        to: 'research'
+        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:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
+    default_instructions: |
+      **Principle**: Decompose into end-to-end, testable units before planning implementation details.
+
+      Define 1-5 vertical slices that each deliver user-visible behavior independently. Describe what each slice delivers, which components it touches, and how it will be tested end-to-end. Reference `$ARCHITECTURE_DOC` if it exists.
+
+      Document slice definitions in the development plan.
+
+      Do not plan implementation tasks or write code.
+    transitions:
+      - trigger: 'structure_defined'
+        to: 'plan'
+        transition_reason: 'Slices defined, ready for detailed planning'
+
+      - trigger: 'need_design_changes'
+        to: 'design'
+        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:
+      - '**/*.md'
+      - '**/*.txt'
+      - '**/*.adoc'
+    default_instructions: |
+      **Principle**: Define detailed HOW per slice without changing the design direction.
+
+      For each vertical slice, define actionable tasks, dependencies, and risks. If any existing document contradicts what is needed, document the contradiction in the development plan and use `need_design_changes`.
+
+      Document the plan in the development plan.
+
+      Do not change the design direction or write code.
+    transitions:
+      - trigger: 'plan_complete'
+        to: 'implement'
+        transition_reason: 'Plan complete, ready for coding'
+        review_perspectives:
+          - perspective: 'architect'
+            prompt: 'Review implementation strategy, design decisions, and integration approach for soundness and maintainability. Ensure the plan aligns with existing system architecture and follows best practices.'
+          - perspective: 'security_expert'
+            prompt: 'Assess security considerations and potential risks in the planned implementation approach. Review data handling, authentication, and potential vulnerabilities.'
+
+      - trigger: 'need_design_changes'
+        to: 'design'
+        additional_instructions: 'The approved design direction is unworkable for the planned slices. Revisit the high-level approach with the user.'
+        transition_reason: 'Planning revealed fundamental flaws in design direction'
+
+      - trigger: 'need_restructuring'
+        to: 'structure'
+        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:
+      - '**/*'
+    default_instructions: |
+      **Principle**: Execute the plan one slice at a time; delegate each slice to a fresh context.
+
+      Build each vertical slice end-to-end before moving to the next. Delegate each slice to a fresh agent session with focused context. Reference `$DESIGN_DOC`, `$ARCHITECTURE_DOC`, and `$REQUIREMENTS_DOC` if they exist. Prevent regressions via build, lint, and tests.
+
+      Adapt tactics within slices. Loop back via `need_design_changes` only if the high-level approach is fundamentally flawed.
+
+      Document progress in the development plan.
+    transitions:
+      - trigger: 'implementation_complete'
+        to: 'commit'
+        transition_reason: 'Implementation complete, ready for finalization'
+        review_perspectives:
+          - perspective: 'senior_software_developer'
+            prompt: 'Review code quality, best practices, testing coverage, and readiness for production deployment. Ensure the implementation follows coding standards and is maintainable.'
+          - perspective: 'performance_engineer'
+            prompt: 'Evaluate performance impact, resource efficiency, and scalability of the implemented solution. Check for potential bottlenecks or optimization opportunities.'
+
+      - trigger: 'need_replanning'
+        to: 'plan'
+        additional_instructions: 'Adjust the plan based on what you learned during coding. Document changes and reasons.'
+        transition_reason: 'Implementation revealed need to revise the plan'
+
+      - trigger: 'need_design_changes'
+        to: 'design'
+        additional_instructions: 'The high-level design approach is fundamentally flawed. Revisit design decisions with the user.'
+        transition_reason: 'Implementation revealed the approved design is unworkable'
+
+      - trigger: 'need_more_research'
+        to: 'research'
+        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:
+      - '**/*'
+    default_instructions: |
+      **Principle**: Leave the codebase cleaner than you found it.
+
+      **Cleanup**: Remove debug output, temporary code, test code blocks, and completed TODOs. Address or document any remaining FIXMEs.
+
+      **Documentation**: Update `$REQUIREMENTS_DOC`, `$ARCHITECTURE_DOC`, and `$DESIGN_DOC` if they exist and changed during implementation. Otherwise, document changes in the development plan. Ensure docs reflect the final implemented state, not the development process.
+
+      **Validation**: Run tests to ensure no regressions. Verify the development plan is accurate.
+
+      Do not add new features.
+
+      $DONE_DEFAULT
+    transitions: []

package/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/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: []

package/resources/workflows/skilled-greenfield.yaml

@@ -191,17 +191,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/resources/workflows/slides.yaml

@@ -213,25 +213,5 @@ states:
 
       **Update** the plan file with delivery preparation progress to ensure successful delivery.
 
-    transitions:
-      - trigger: delivery_complete
-        to: ideate
-        additional_instructions: |
-          **Delivery phase complete!** Your presentation has been successfully delivered.
-
-          Mark all delivery tasks as complete in the plan file and prepare for new work.
-        transition_reason: 'Presentation delivery completed successfully, ready for new projects'
-
-      - trigger: need_final_review
-        to: review
-        additional_instructions: 'Final preparation revealed issues requiring additional review. Focus on addressing these concerns before delivery.'
-        transition_reason: 'Delivery preparation identified issues requiring additional review'
-
-      - trigger: abandon_presentation
-        to: ideate
-        instructions: |
-          **Abandon delivery preparation** - Clean up delivery preparation and return to ideation.
-
-          The plan file and completed work will remain for future reference.
-        additional_instructions: 'Presentation abandoned before delivery. Clean up and prepare for new topics.'
-        transition_reason: 'User decided to abandon presentation before delivery'
+      $DONE_DEFAULT
+    transitions: []

package/resources/workflows/tdd.yaml

@@ -160,11 +160,21 @@ states:
         transition_reason: 'Refactoring revealed need to revise implementation'
 
       - trigger: 'feature_complete'
-        to: 'explore'
+        to: 'done'
         additional_instructions: 'Update task progress to reflect feature completion.'
-        transition_reason: 'Feature fully implemented and cleaned up, ready for new tasks'
+        transition_reason: 'Feature fully implemented and cleaned up, ready to exit TDD cycle'
 
       - 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'
+
+  done:
+    description: 'TDD cycle complete - feature fully implemented and cleaned up'
+    allowed_file_patterns:
+      - '**/*'
+    default_instructions: |
+      The TDD cycle is complete. All aspects of the feature have been implemented and refactored.
+
+      $DONE_DEFAULT
+    transitions: []

package/resources/workflows/waterfall.yaml

@@ -214,12 +214,6 @@ states:
       - Ensure code is ready for production/delivery
 
       Update task progress and mark completed work as you finalize the feature.
-    transitions:
-      - trigger: 'need_final_changes'
-        to: 'implementation'
-        additional_instructions: 'Finalization revealed issues that require code changes. Focus on the specific problems identified during final review.'
-        transition_reason: 'Final review found issues requiring implementation changes'
 
-      - trigger: 'finalization_complete'
-        to: 'requirements'
-        transition_reason: 'Feature delivery complete, beginning new development cycle'
+      $DONE_DEFAULT
+    transitions: []

package/packages/core/dist/state-machine.d.ts

@@ -1,52 +0,0 @@
-/**
- * State Machine Definition for Vibe Feature MCP Server
- *
- * This module defines the development workflow state machine, including:
- * - Development phases (states)
- * - Transition triggers and conditions
- * - Phase-specific instructions for LLM guidance
- * - Transition-specific prompts for contextual guidance
- */
-export type DevelopmentPhase = 'idle' | 'requirements' | 'design' | 'implementation' | 'qa' | 'testing' | 'complete';
-export type TransitionTrigger = 'new_feature_request' | 'refine_requirements' | 'requirements_complete' | 'abandon_feature' | 'refine_design' | 'requirements_unclear' | 'design_complete' | 'refine_implementation' | 'design_issues' | 'implementation_complete' | 'refine_qa' | 'implementation_issues' | 'qa_complete' | 'refine_testing' | 'qa_issues' | 'testing_complete' | 'feature_delivered' | 'direct_transition';
-export interface StateTransition {
-    from: DevelopmentPhase;
-    to: DevelopmentPhase;
-    trigger: TransitionTrigger;
-    isModeled: boolean;
-    instructions: string;
-    transitionReason: string;
-}
-/**
- * Complete state transition table
- *
- * This table defines all possible transitions between development phases.
- * - Modeled transitions: Shown in the state diagram, get contextual guidance
- * - Direct transitions: Not shown in diagram, get general phase instructions
- */
-export declare const STATE_TRANSITIONS: StateTransition[];
-/**
- * Direct transition instructions for non-modeled transitions
- * These are used when users jump directly to any phase using proceed_to_phase
- */
-export declare const DIRECT_PHASE_INSTRUCTIONS: Record<DevelopmentPhase, string>;
-/**
- * Get transition instructions for a specific state change
- */
-export declare function getTransitionInstructions(fromState: DevelopmentPhase, toState: DevelopmentPhase, trigger?: TransitionTrigger): {
-    instructions: string;
-    transitionReason: string;
-    isModeled: boolean;
-};
-/**
- * Get all possible transitions from a given state
- */
-export declare function getPossibleTransitions(fromState: DevelopmentPhase): StateTransition[];
-/**
- * Check if a transition is modeled (shown in state diagram)
- */
-export declare function isModeledTransition(fromState: DevelopmentPhase, toState: DevelopmentPhase): boolean;
-/**
- * Get phase-specific instructions for continuing work in current phase
- */
-export declare function getContinuePhaseInstructions(phase: DevelopmentPhase): string;