Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177
  1. # Step 14: Workflow Completion
  2. ## MANDATORY EXECUTION RULES (READ FIRST):
  3. - ✅ THIS IS A FINAL STEP - Workflow completion required
  4. - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
  5. - 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
  6. - 🛑 NO content generation - this is a wrap-up step
  7. - 📋 FINALIZE document and update workflow status
  8. - 💬 FOCUS on completion, validation, and next steps
  9. - 🎯 UPDATE workflow status files with completion information
  10. - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
  11. ## EXECUTION PROTOCOLS:
  12. - 🎯 Show your analysis before taking any action
  13. - 💾 Update the main workflow status file with completion information
  14. - 📖 Suggest potential next workflow steps for the user
  15. - 🚫 DO NOT load additional steps after this one
  16. ## TERMINATION STEP PROTOCOLS:
  17. - This is a FINAL step - workflow completion required
  18. - 📖 Update output file frontmatter, adding this step to the end of the list of stepsCompleted to indicate all is finished..
  19. - Output completion summary and next step guidance
  20. - Update the main workflow status file with finalized document
  21. - Suggest potential next workflow steps for the user
  22. - Mark workflow as complete in status tracking
  23. ## CONTEXT BOUNDARIES:
  24. - Complete UX design specification is available from all previous steps
  25. - Workflow frontmatter shows all completed steps
  26. - All collaborative content has been generated and saved
  27. - Focus on completion, validation, and next steps
  28. ## YOUR TASK:
  29. Complete the UX design workflow, update status files, and suggest next steps for the project.
  30. ## WORKFLOW COMPLETION SEQUENCE:
  31. ### 1. Announce Workflow Completion
  32. Inform user that the UX design is complete:
  33. "🎉 **UX Design Complete, {{user_name}}!**
  34. I've successfully collaborated with you to create a comprehensive UX design specification for {{project_name}}.
  35. **What we've accomplished:**
  36. - ✅ Project understanding and user insights
  37. - ✅ Core experience and emotional response definition
  38. - ✅ UX pattern analysis and inspiration
  39. - ✅ Design system choice and implementation strategy
  40. - ✅ Core interaction definition and experience mechanics
  41. - ✅ Visual design foundation (colors, typography, spacing)
  42. - ✅ Design direction mockups and visual explorations
  43. - ✅ User journey flows and interaction design
  44. - ✅ Component strategy and custom component specifications
  45. - ✅ UX consistency patterns for common interactions
  46. - ✅ Responsive design and accessibility strategy
  47. **The complete UX design specification is now available at:** `{planning_artifacts}/ux-design-specification.md`
  48. **Supporting Visual Assets:**
  49. - Color themes visualizer: `{planning_artifacts}/ux-color-themes.html`
  50. - Design directions mockups: `{planning_artifacts}/ux-design-directions.html`
  51. This specification is now ready to guide visual design, implementation, and development."
  52. ### 2. Workflow Status Update
  53. Update the main workflow status file:
  54. - Load the project's workflow status file (if one exists)
  55. - Update workflow_status["create-ux-design"] = `{planning_artifacts}/ux-design-specification.md`
  56. - Save file, preserving all comments and structure
  57. - Mark current timestamp as completion time
  58. ### 3. Suggest Next Steps
  59. UX Design complete. Invoke the `bmad-help` skill.
  60. ### 5. Final Completion Confirmation
  61. Congratulate the user on the completion you both completed together of the UX.
  62. ## SUCCESS METRICS:
  63. ✅ UX design specification contains all required sections
  64. ✅ All collaborative content properly saved to document
  65. ✅ Workflow status file updated with completion information
  66. ✅ Clear next step guidance provided to user
  67. ✅ Document quality validation completed
  68. ✅ User acknowledges completion and understands next options
  69. ## FAILURE MODES:
  70. ❌ Not updating workflow status file with completion information
  71. ❌ Missing clear next step guidance for user
  72. ❌ Not confirming document completeness with user
  73. ❌ Workflow not properly marked as complete in status tracking
  74. ❌ User unclear about what happens next
  75. ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
  76. ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
  77. ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
  78. ## WORKFLOW COMPLETION CHECKLIST:
  79. ### Design Specification Complete:
  80. - [ ] Executive summary and project understanding
  81. - [ ] Core experience and emotional response definition
  82. - [ ] UX pattern analysis and inspiration
  83. - [ ] Design system choice and strategy
  84. - [ ] Core interaction mechanics definition
  85. - [ ] Visual design foundation (colors, typography, spacing)
  86. - [ ] Design direction decisions and mockups
  87. - [ ] User journey flows and interaction design
  88. - [ ] Component strategy and specifications
  89. - [ ] UX consistency patterns documentation
  90. - [ ] Responsive design and accessibility strategy
  91. ### Process Complete:
  92. - [ ] All steps completed with user confirmation
  93. - [ ] All content saved to specification document
  94. - [ ] Frontmatter properly updated with all steps
  95. - [ ] Workflow status file updated with completion
  96. - [ ] Next steps clearly communicated
  97. ## NEXT STEPS GUIDANCE:
  98. **Immediate Options:**
  99. 1. **Wireframe Generation** - Create low-fidelity layouts based on UX spec
  100. 2. **Interactive Prototype** - Build clickable prototypes for testing
  101. 3. **Solution Architecture** - Technical design with UX context
  102. 4. **Figma Visual Design** - High-fidelity UI implementation
  103. 5. **Epic Creation** - Break down UX requirements for development
  104. **Recommended Sequence:**
  105. For design-focused teams: Wireframes → Prototypes → Figma Design → Development
  106. For technical teams: Architecture → Epic Creation → Development
  107. Consider team capacity, timeline, and whether user validation is needed before implementation.
  108. ## WORKFLOW FINALIZATION:
  109. - Set `lastStep = 14` in document frontmatter
  110. - Update workflow status file with completion timestamp
  111. - Provide completion summary to user
  112. - Do NOT load any additional steps
  113. ## FINAL REMINDER:
  114. This UX design workflow is now complete. The specification serves as the foundation for all visual and development work. All design decisions, patterns, and requirements are documented to ensure consistent, accessible, and user-centered implementation.
  115. **Congratulations on completing the UX Design Specification for {{project_name}}!** 🎉
  116. **Core Deliverables:**
  117. - ✅ UX Design Specification: `{planning_artifacts}/ux-design-specification.md`
  118. - ✅ Color Themes Visualizer: `{planning_artifacts}/ux-color-themes.html`
  119. - ✅ Design Directions: `{planning_artifacts}/ux-design-directions.html`
  120. ## On Complete
  121. Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
  122. If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.