@codemcp/workflows-core 5.2.1 → 5.2.3

package/resources/workflows/sdd-greenfield.yaml

@@ -27,18 +27,20 @@ states:
   constitution:
     description: 'Establish constitutional framework and project governance'
     default_instructions: |
-      You are establishing the constitutional framework for this new project. This phase sets the foundational principles that will guide all development decisions.
+      **STEP 1: Create Project Constitution**
+      Use the template provided to create a `constitution.md` file in the project root.
 
-      **Your tasks:**
-      1. **Create Project Constitution**: Use the template provided to create a `constitution.md` file
-      2. **Customize Principles**: Adapt the principles to your specific project needs
-      3. **Set Quality Gates**: Define what constitutes acceptable quality and when to reject solutions
-      4. **Document Governance**: Establish how these principles will be enforced
+      **STEP 2: Customize Principles**
+      Adapt the constitutional principles to your specific project needs.
 
-      Create a `constitution.md` file in the project root with project-specific governance principles. This will be referenced in all subsequent phases.
-    additional_instructions: |
-      **Constitutional Framework Template:**
+      **STEP 3: Set Quality Gates**
+      Define what constitutes acceptable quality and when to reject solutions.
+
+      **STEP 4: Document Governance**
+      Establish how these principles will be enforced throughout development.
 
+      This constitutional framework will be referenced in all subsequent phases and serves as the source of truth for development decisions.
+    additional_instructions: |
       Use this template to create your `constitution.md` file:
 
       ```markdown
@@ -97,45 +99,43 @@ states:
   specify:
     description: 'Create comprehensive feature specification'
     default_instructions: |
-      You are creating the feature specification that will be the source of truth for all development.
-
-      **Specification Process:**
-
-      1. **Parse User Requirements**: Extract key concepts from the user's description
-         - Identify: actors, actions, data, constraints
-         - Focus on WHAT users need and WHY, not HOW to implement
-
-      2. **Interactive Requirements Gathering**: Ask clarifying questions about:
-         - **Target Users**: Who will use this system? What are their technical skills?
-         - **Scale & Performance**: How many users? What performance expectations?
-         - **Integration**: Does this need to integrate with existing systems?
-         - **Constraints**: Any specific requirements, compliance needs, or limitations?
-         - **Success Metrics**: How will you measure if this is successful?
-
-      3. **Handle Ambiguities Systematically**:
-         - Make informed guesses based on context and industry standards
-         - Only use [NEEDS CLARIFICATION: specific question] for critical decisions that:
-           - Significantly impact feature scope or user experience
-           - Have multiple reasonable interpretations with different implications
-           - Lack any reasonable default
-         - **LIMIT: Maximum 3 [NEEDS CLARIFICATION] markers total**
-         - Prioritize: scope > security/privacy > user experience > technical details
-
-      4. **Quality Validation**:
-         - No implementation details (languages, frameworks, APIs)
-         - Written for non-technical stakeholders
-         - All requirements are testable
-         - Success criteria are measurable and technology-agnostic
-
-      5. **Handle Clarifications** (if any [NEEDS CLARIFICATION] markers exist):
-         - Present options to user in structured format
-         - Wait for user responses
-         - Update specification with chosen answers
+      Create the feature specification that will be the source of truth for all development.
+
+      **STEP 1: Parse User Requirements**
+      Extract key concepts from the user's description:
+      - Identify: actors, actions, data, constraints
+      - Focus on WHAT users need and WHY, not HOW to implement
+
+      **STEP 2: Interactive Requirements Gathering**
+      Ask clarifying questions about:
+      - Target Users: Who will use this system? What are their technical skills?
+      - Scale & Performance: How many users? What performance expectations?
+      - Integration: Does this need to integrate with existing systems?
+      - Constraints: Any specific requirements, compliance needs, or limitations?
+      - Success Metrics: How will you measure if this is successful?
+
+      **STEP 3: Handle Ambiguities Systematically**
+      - Make informed guesses based on context and industry standards
+      - Use `[NEEDS CLARIFICATION: specific question]` ONLY for critical decisions that:
+        - Significantly impact feature scope or user experience
+        - Have multiple reasonable interpretations with different implications
+        - Lack any reasonable default
+      - **LIMIT: Maximum 3 clarification markers total**
+      - Prioritize: scope > security/privacy > user experience > technical details
+
+      **STEP 4: Validate Quality**
+      - No implementation details (languages, frameworks, APIs)
+      - Written for non-technical stakeholders
+      - All requirements are testable
+      - Success criteria are measurable and technology-agnostic
+
+      **STEP 5: Handle Clarifications** (if any exist)
+      - Present options to user in structured format
+      - Wait for user responses
+      - Update specification with chosen answers
 
       Create `$VIBE_DIR/specs/$BRANCH_NAME/spec.md` using the template provided.
     additional_instructions: |
-      **Feature Specification Template:**
-
       Use this template to create your `spec.md` file:
 
       ```markdown
@@ -232,46 +232,45 @@ states:
   plan:
     description: 'Generate implementation plan with constitutional compliance'
     default_instructions: |
-      You are creating the implementation plan with constitutional compliance gates.
-
-      **Planning Process:**
-
-      1. **Load Context**:
-         - Read the feature specification (`$VIBE_DIR/specs/$BRANCH_NAME/spec.md`)
-         - Read the project constitution (`constitution.md`)
-         - Understand the technical requirements
-
-      2. **Interactive Technology Selection**: Ask the user about their preferences:
-         - **Technology Stack**: What programming languages/frameworks do you prefer?
-         - **Architecture Style**: Monolith, microservices, serverless, or hybrid?
-         - **Database**: What type of data storage do you need? (SQL, NoSQL, files)
-         - **Deployment**: Where will this run? (cloud, on-premise, local)
-         - **Experience Level**: What's your experience with different technologies?
-         - **Constraints**: Any technology restrictions or requirements?
-
-      3. **Technical Context Analysis**:
-         - Identify technology stack and architecture decisions based on user input
-         - Map dependencies and integration points
-         - Mark unknowns as "NEEDS CLARIFICATION" for research phase
-
-      4. **Constitutional Compliance Check**:
-         - Evaluate planned approach against each constitutional article
-         - Identify any violations and justify or resolve them
-         - Document compliance decisions
-
-      5. **Phase 0 - Research & Decisions**:
-         - For each unknown in Technical Context → research task
-         - For each technology choice → best practices task
-         - Generate `$VIBE_DIR/specs/$BRANCH_NAME/technology-research.md` with all decisions and rationale
-
-      6. **Phase 1 - High-Level Design**:
-         - Document high-level architecture and component overview
-         - Identify major system boundaries and integration points
-         - Document technology stack decisions and rationale
-
-      7. **Re-evaluate Constitutional Compliance**:
-         - Verify design decisions align with constitutional principles
-         - Document any adjustments needed
+      Create the implementation plan with constitutional compliance gates.
+
+      **STEP 1: Load Context**
+      - Read the feature specification: `$VIBE_DIR/specs/$BRANCH_NAME/spec.md`
+      - Read the project constitution: `constitution.md`
+      - Understand the technical requirements
+
+      **STEP 2: Interactive Technology Selection**
+      Ask the user about their preferences:
+      - Technology Stack: What programming languages/frameworks do you prefer?
+      - Architecture Style: Monolith, microservices, serverless, or hybrid?
+      - Database: What type of data storage do you need? (SQL, NoSQL, files)
+      - Deployment: Where will this run? (cloud, on-premise, local)
+      - Experience Level: What's your experience with different technologies?
+      - Constraints: Any technology restrictions or requirements?
+
+      **STEP 3: Analyze Technical Context**
+      - Identify technology stack and architecture decisions based on user input
+      - Map dependencies and integration points
+      - Mark unknowns as "NEEDS CLARIFICATION" for research phase
+
+      **STEP 4: Check Constitutional Compliance**
+      - Evaluate planned approach against each constitutional article
+      - Identify any violations and justify or resolve them
+      - Document compliance decisions
+
+      **STEP 5: Generate Research & Decisions**
+      - For each unknown in Technical Context → research task
+      - For each technology choice → best practices task
+      - Generate `$VIBE_DIR/specs/$BRANCH_NAME/technology-research.md` with all decisions and rationale
+
+      **STEP 6: Document High-Level Design**
+      - Document high-level architecture and component overview
+      - Identify major system boundaries and integration points
+      - Document technology stack decisions and rationale
+
+      **STEP 7: Re-evaluate Constitutional Compliance**
+      - Verify design decisions align with constitutional principles
+      - Document any adjustments needed
 
       Create `$VIBE_DIR/specs/$BRANCH_NAME/plan.md` with the complete implementation strategy, including technology decisions, architecture, and development phases.
 
@@ -290,59 +289,58 @@ states:
   tasks:
     description: 'Generate actionable, dependency-ordered tasks organized by user stories'
     default_instructions: |
-      You are generating actionable tasks organized by user stories for independent implementation.
+      Generate actionable tasks organized by user stories for independent implementation.
 
-      **Task Generation Process:**
+      **STEP 1: Load Design Documents**
+      - Required: `$VIBE_DIR/specs/$BRANCH_NAME/plan.md` (tech stack, libraries, structure), `$VIBE_DIR/specs/$BRANCH_NAME/spec.md` (user stories with priorities)
+      - Optional: `$VIBE_DIR/specs/$BRANCH_NAME/technology-research.md`
 
-      1. **Load Design Documents**:
-         - **Required**: `$VIBE_DIR/specs/$BRANCH_NAME/plan.md` (tech stack, libraries, structure), `$VIBE_DIR/specs/$BRANCH_NAME/spec.md` (user stories with priorities)
-         - **Optional**: `$VIBE_DIR/specs/$BRANCH_NAME/technology-research.md`
+      **STEP 2: Extract User Stories**
+      Load user stories with priorities (P1, P2, P3...)
 
-      2. **Extract User Stories**: Load user stories with priorities (P1, P2, P3...)
+      **STEP 3: Generate Tasks Organized by User Story**
+      - Setup Phase: Shared infrastructure needed by all stories
+      - Foundational Phase: Prerequisites that must complete before ANY user story
+      - User Story Phases (P1, P2, P3...): One phase per story in priority order
+        - Group all tasks needed to complete JUST that story
+        - Include models, services, endpoints, UI components specific to that story
+        - Mark parallelizable tasks with `[P]`
+        - Each story should be independently testable
 
-      3. **Generate Tasks Organized by User Story**:
-         - **Setup Phase**: Shared infrastructure needed by all stories
-         - **Foundational Phase**: Prerequisites that must complete before ANY user story
-         - **User Story Phases** (P1, P2, P3...): One phase per story in priority order
-           - Group all tasks needed to complete JUST that story
-           - Include models, services, endpoints, UI components specific to that story
-           - Mark parallelizable tasks with [P]
-           - Each story should be independently testable
+      **STEP 4: Apply Task Rules**
+      - Different files = mark `[P]` for parallel execution
+      - Same file = sequential (no `[P]`)
+      - Number tasks sequentially (T001, T002...)
+      - Each task specific enough for LLM to complete without additional context
 
-      4. **Task Rules**:
-         - Different files = mark [P] for parallel execution
-         - Same file = sequential (no [P])
-         - Number tasks sequentially (T001, T002...)
-         - Each task specific enough for LLM to complete without additional context
+      **STEP 5: Generate Dependency Graph**
+      Show user story completion order and parallel opportunities
 
-      5. **Generate Dependency Graph**: Show user story completion order and parallel opportunities
-
-      6. **Implementation Strategy**: MVP-first approach (typically just User Story 1)
+      **STEP 6: Document Implementation Strategy**
+      MVP-first approach (typically just User Story 1)
 
     additional_instructions: |
-      **Document Creation Instructions:**
-
       Create these documents in the following order:
 
-      **1. Data Model (`$VIBE_DIR/specs/$BRANCH_NAME/data-model.md`)**:
+      **1. Data Model** (`$VIBE_DIR/specs/$BRANCH_NAME/data-model.md`)
       - Extract entities from the specification
       - Define relationships between entities
       - Include validation rules from requirements
       - Document state transitions if applicable
 
-      **2. API Contracts (`$VIBE_DIR/specs/$BRANCH_NAME/contracts/`)**:
+      **2. API Contracts** (`$VIBE_DIR/specs/$BRANCH_NAME/contracts/`)
       - Generate API contracts from functional requirements
       - Create OpenAPI/GraphQL schemas based on chosen technology stack
       - Ensure contracts align with data models
       - Include error handling and validation
 
-      **3. Development Setup (`$VIBE_DIR/specs/$BRANCH_NAME/quickstart.md`)**:
+      **3. Development Setup** (`$VIBE_DIR/specs/$BRANCH_NAME/quickstart.md`)
       - Project setup instructions based on chosen technology stack
       - Development environment configuration
       - Build and run instructions
       - Testing setup and commands
 
-      **4. Task Breakdown (`$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`)**:
+      **4. Task Breakdown** (`$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`)
       Use this structure for the tasks file:
 
       ```markdown
@@ -384,18 +382,28 @@ states:
   implement:
     description: 'Execute implementation following the task breakdown'
     default_instructions: |
-      You are implementing the solution by executing the tasks in the order defined in `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`.
-
-      **Implementation Guidelines:**
-      1. **Follow Task Order**: Execute tasks in the sequence defined, respecting dependencies
-      2. **Constitutional Compliance**: Ensure all implementation decisions align with the project constitution
-      3. **User Story Focus**: Complete one user story at a time for incremental delivery
-      4. **Quality Gates**: Each user story must meet the success criteria from the specification
-      5. **Testing**: Validate each user story independently before moving to the next
-      6. **Documentation**: Update documentation as you implement
-
-      **Progress Tracking**:
-      - Mark completed tasks with [x] in `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`
+      Execute the implementation by following the tasks in the order defined in `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`.
+
+      **STEP 1: Follow Task Order**
+      Execute tasks in the sequence defined, respecting dependencies
+
+      **STEP 2: Ensure Constitutional Compliance**
+      Verify all implementation decisions align with the project constitution
+
+      **STEP 3: Complete User Stories Incrementally**
+      Focus on one user story at a time for incremental delivery
+
+      **STEP 4: Meet Quality Gates**
+      Each user story must meet the success criteria from the specification
+
+      **STEP 5: Validate Each User Story**
+      Test each user story independently before moving to the next
+
+      **STEP 6: Keep Documentation Current**
+      Update documentation as you implement
+
+      **Progress Tracking:**
+      - Mark completed tasks with `[x]` in `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`
       - Document any deviations or decisions in the plan file
       - Update the specification if requirements evolve during implementation
 
@@ -416,26 +424,25 @@ states:
   document:
     description: 'Create comprehensive project documentation'
     default_instructions: |
-      You are creating the final project documentation that serves users and maintainers.
-
-      **Documentation Tasks:**
-      1. **User Documentation**:
-         - Installation and setup guide
-         - User manual with examples
-         - API documentation (if applicable)
-         - Troubleshooting guide
-
-      2. **Developer Documentation**:
-         - Architecture overview
-         - Development setup
-         - Contributing guidelines
-         - Code organization
-
-      3. **Project Documentation**:
-         - README with project overview
-         - Changelog
-         - License information
-         - Deployment guide
+      Create the final project documentation that serves users and maintainers.
+
+      **STEP 1: Create User Documentation**
+      - Installation and setup guide
+      - User manual with examples
+      - API documentation (if applicable)
+      - Troubleshooting guide
+
+      **STEP 2: Create Developer Documentation**
+      - Architecture overview
+      - Development setup
+      - Contributing guidelines
+      - Code organization
+
+      **STEP 3: Create Project Documentation**
+      - README with project overview
+      - Changelog
+      - License information
+      - Deployment guide
 
       **Quality Standards** (from constitution):
       - Documentation serves users, not developers
@@ -459,6 +466,5 @@ global_transitions:
   - trigger: 'abandon_project'
     to: 'constitution'
     instructions: >
-      Project abandoned. If you want to restart, you'll begin again with establishing
-      the constitutional framework.
+      If you want to restart the project, you'll begin again with establishing the constitutional framework.
     transition_reason: 'Project abandoned, restart from beginning'

package/resources/workflows/slides.yaml

@@ -24,17 +24,15 @@ states:
   ideate:
     description: 'Brainstorm presentation concept and define strategic foundation'
     default_instructions: |
-      You are in the ideation phase for presentation development. This is where you define the foundation of your presentation.
+      **Clarify the presentation foundation** with the user by gathering essential information:
 
-      Focus on understanding the core purpose and audience:
       - Brainstorm presentation topic and key messages
       - Define target audience and their knowledge level
       - Set presentation goals and success criteria
       - Research topic and gather reference materials
       - Define scope, time constraints, and context
 
-      Work with the user to clarify these fundamental aspects before moving to structure.
-      Update the plan file with ideation progress and key decisions.
+      **Update** the plan file with ideation progress and key decisions before proceeding to structure.
 
     transitions:
       - trigger: ideation_complete
@@ -44,7 +42,8 @@ states:
       - trigger: abandon_presentation
         to: ideate
         instructions: |
-          Presentation development abandoned. Clean up any ideation work and prepare for new presentation topics.
+          **Abandon ideation work** - Clean up any ideation work and prepare for new presentation topics.
+
           The plan file will remain for future reference if needed.
         additional_instructions: 'Presentation development abandoned. Prepare for new presentation topics.'
         transition_reason: 'User decided to abandon current presentation development'
@@ -52,9 +51,8 @@ states:
   structure:
     description: 'Organize content flow and logical progression'
     default_instructions: |
-      Working on presentation structure phase. Focus on organizing your content logically and effectively.
+      **Create a detailed presentation structure** by organizing your content logically and effectively:
 
-      Key activities for this phase:
       - Create detailed presentation outline with main sections
       - Define slide sequence and narrative flow
       - Plan smooth transitions between topics
@@ -62,14 +60,13 @@ states:
       - Estimate timing for each section and overall presentation
       - Consider audience engagement points and interaction opportunities
 
-      Work with the user to create a solid structural foundation before moving to content drafting.
-      Update the plan file with structural decisions and progress.
+      **Update** the plan file with structural decisions and progress before moving to content drafting.
 
     transitions:
       - trigger: structure_complete
         to: draft
         additional_instructions: |
-          Structure complete! ✅ You have a well-organized outline and clear content flow.
+          **Structure phase complete!** You have a well-organized outline and clear content flow.
 
           Update the plan file with drafting tasks and mark completed structural work.
         transition_reason: 'Content structure and flow established, ready for content creation'
@@ -82,7 +79,8 @@ states:
       - trigger: abandon_presentation
         to: ideate
         instructions: |
-          Presentation development abandoned during structuring. Clean up structural work and return to ideation.
+          **Abandon structural work** - Clean up structural work and return to ideation.
+
           The plan file and any completed work will remain for future reference.
         additional_instructions: 'Presentation abandoned during structure phase. Clean up and prepare for new topics.'
         transition_reason: 'User decided to abandon presentation during structure phase'
@@ -90,9 +88,8 @@ states:
   draft:
     description: 'Create content, speaker notes, and visual planning'
     default_instructions: |
-      Working on content drafting phase. This is where you create the actual presentation content and materials.
+      **Create content and speaker notes** to establish the presentation material and delivery guide:
 
-      Key activities for this phase:
       - Write clear, engaging content for each slide/section
       - Create comprehensive speaker notes as a main deliverable
       - Make strategic decisions about visual vs. spoken content split
@@ -101,14 +98,13 @@ states:
       - Create placeholders and specifications for visual content
       - Ensure content aligns with timing and audience needs
 
-      Focus on creating high-quality content that serves both the slides and the speaker.
-      Update the plan file with drafting progress and content decisions.
+      **Update** the plan file with drafting progress and content decisions before moving to styling.
 
     transitions:
       - trigger: draft_complete
         to: style
         additional_instructions: |
-          Draft complete! ✅ You have solid content, speaker notes, and visual planning.
+          **Draft phase complete!** You have solid content, speaker notes, and visual planning.
 
           Update the plan file with styling tasks and mark completed drafting work.
         transition_reason: 'Content and speaker notes complete, ready for visual design and styling'
@@ -121,7 +117,8 @@ states:
       - trigger: abandon_presentation
         to: ideate
         instructions: |
-          Presentation development abandoned during drafting. Clean up content work and return to ideation.
+          **Abandon drafting work** - Clean up content work and return to ideation.
+
           The plan file and any completed work will remain for future reference.
         additional_instructions: 'Presentation abandoned during draft phase. Clean up and prepare for new topics.'
         transition_reason: 'User decided to abandon presentation during draft phase'
@@ -129,9 +126,8 @@ states:
   style:
     description: 'Apply design, create visuals, and enhance presentation aesthetics'
     default_instructions: |
-      Working on styling and visual design phase. This is where you bring visual appeal and consistency to your presentation.
+      **Apply visual design and create presentation aesthetics** to bring professional appeal and consistency:
 
-      Key activities for this phase:
       - Evaluate presentation requirements and choose appropriate tool/platform
       - Select themes, templates, and establish visual design approach
       - Source existing visuals, images, and graphic elements
@@ -141,14 +137,13 @@ states:
       - Ensure visual elements effectively support and enhance the content
       - Test visual consistency across all slides/sections
 
-      Focus on creating a visually appealing and professional presentation.
-      Update the plan file with styling progress and design decisions.
+      **Update** the plan file with styling progress and design decisions before moving to review.
 
     transitions:
       - trigger: style_complete
         to: review
         additional_instructions: |
-          Styling complete! ✅ You have a visually appealing presentation with consistent design.
+          **Style phase complete!** You have a visually appealing presentation with consistent design.
 
           Update the plan file with review tasks and mark completed styling work.
         transition_reason: 'Visual design and styling complete, ready for content and delivery review'
@@ -161,7 +156,8 @@ states:
       - trigger: abandon_presentation
         to: ideate
         instructions: |
-          Presentation development abandoned during styling. Clean up design work and return to ideation.
+          **Abandon styling work** - Clean up design work and return to ideation.
+
           The plan file and any completed work will remain for future reference.
         additional_instructions: 'Presentation abandoned during style phase. Clean up and prepare for new topics.'
         transition_reason: 'User decided to abandon presentation during style phase'
@@ -169,9 +165,8 @@ states:
   review:
     description: 'Validate content quality and presentation effectiveness'
     default_instructions: |
-      Working on review and validation phase. This is where you ensure your presentation is ready for delivery.
+      **Validate presentation quality** by reviewing content, timing, visuals, and delivery readiness:
 
-      Key activities for this phase:
       - Review content flow, narrative coherence, and logical progression
       - Test presentation timing and pacing for your allocated time
       - Verify visual quality, consistency, and professional appearance
@@ -181,14 +176,13 @@ states:
       - Ensure all interactive elements and visuals work correctly
       - Refine speaker notes and delivery preparation
 
-      Focus on validating that your presentation achieves its goals effectively.
-      Update the plan file with review progress and any refinements made.
+      **Update** the plan file with review progress and refinements before moving to delivery preparation.
 
     transitions:
       - trigger: review_complete
         to: deliver
         additional_instructions: |
-          Review complete! ✅ Your presentation has been validated and refined for delivery.
+          **Review phase complete!** Your presentation has been validated and refined for delivery.
 
           Update the plan file with delivery preparation tasks and mark completed review work.
         transition_reason: 'Presentation reviewed and validated, ready for final delivery preparation'
@@ -206,7 +200,8 @@ states:
       - trigger: abandon_presentation
         to: ideate
         instructions: |
-          Presentation development abandoned during review. Clean up review work and return to ideation.
+          **Abandon review work** - Clean up review work and return to ideation.
+
           The plan file and any completed work will remain for future reference.
         additional_instructions: 'Presentation abandoned during review phase. Clean up and prepare for new topics.'
         transition_reason: 'User decided to abandon presentation during review phase'
@@ -214,9 +209,8 @@ states:
   deliver:
     description: 'Prepare final presentation for delivery'
     default_instructions: |
-      Working on delivery preparation phase. This is the final phase to ensure your presentation is ready for successful delivery.
+      **Prepare final delivery** by exporting formats, testing setup, and ensuring flawless execution:
 
-      Key activities for this phase:
       - Export presentation to all required formats (native, PDF, backup formats)
       - Finalize speaker setup, notes, and delivery materials
       - Configure and test presentation environment and technical setup
@@ -226,14 +220,13 @@ states:
       - Ensure all backup plans and alternatives are ready
       - Final check of timing, flow, and delivery readiness
 
-      Focus on ensuring flawless delivery execution and professional presentation.
-      Update the plan file with delivery preparation progress.
+      **Update** the plan file with delivery preparation progress to ensure successful delivery.
 
     transitions:
       - trigger: delivery_complete
         to: ideate
         additional_instructions: |
-          Presentation delivery complete! ✅ Your presentation has been successfully delivered.
+          **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'
@@ -246,7 +239,8 @@ states:
       - trigger: abandon_presentation
         to: ideate
         instructions: |
-          Presentation development abandoned before delivery. Clean up delivery preparation and return to ideation.
+          **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'