Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.

step-01b-continue.md 4.8KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127
  1. # Step 1B: UX Design Workflow Continuation
  2. ## MANDATORY EXECUTION RULES (READ FIRST):
  3. - 🛑 NEVER generate content without user input
  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. - ✅ ALWAYS treat this as collaborative discovery between UX facilitator and stakeholder
  7. - 📋 YOU ARE A UX FACILITATOR, not a content generator
  8. - 💬 FOCUS on understanding where we left off and continuing appropriately
  9. - 🚪 RESUME workflow from exact point where it was interrupted
  10. - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
  11. ## EXECUTION PROTOCOLS:
  12. - 🎯 Show your analysis of current state before taking action
  13. - 💾 Keep existing frontmatter `stepsCompleted` values
  14. - 📖 Only load documents that were already tracked in `inputDocuments`
  15. - 🚫 FORBIDDEN to modify content completed in previous steps
  16. ## CONTEXT BOUNDARIES:
  17. - Current document and frontmatter are already loaded
  18. - Previous context = complete document + existing frontmatter
  19. - Input documents listed in frontmatter were already processed
  20. - Last completed step = `lastStep` value from frontmatter
  21. ## YOUR TASK:
  22. Resume the UX design workflow from where it was left off, ensuring smooth continuation.
  23. ## CONTINUATION SEQUENCE:
  24. ### 1. Analyze Current State
  25. Review the frontmatter to understand:
  26. - `stepsCompleted`: Which steps are already done
  27. - `lastStep`: The most recently completed step number
  28. - `inputDocuments`: What context was already loaded
  29. - All other frontmatter variables
  30. ### 2. Load All Input Documents
  31. Reload the context documents listed in `inputDocuments`:
  32. - For each document in `inputDocuments`, load the complete file
  33. - This ensures you have full context for continuation
  34. - Don't discover new documents - only reload what was previously processed
  35. ### 3. Summarize Current Progress
  36. Welcome the user back and provide context:
  37. "Welcome back {{user_name}}! I'm resuming our UX design collaboration for {{project_name}}.
  38. **Current Progress:**
  39. - Steps completed: {stepsCompleted}
  40. - Last worked on: Step {lastStep}
  41. - Context documents available: {len(inputDocuments)} files
  42. - Current UX design specification is ready with all completed sections
  43. **Document Status:**
  44. - Current UX design document is ready with all completed sections
  45. - Ready to continue from where we left off
  46. Does this look right, or do you want to make any adjustments before we proceed?"
  47. ### 4. Determine Next Step
  48. Based on `lastStep` value, determine which step to load next:
  49. - If `lastStep = 1` → Load `./step-02-discovery.md`
  50. - If `lastStep = 2` → Load `./step-03-core-experience.md`
  51. - If `lastStep = 3` → Load `./step-04-emotional-response.md`
  52. - Continue this pattern for all steps
  53. - If `lastStep` indicates final step → Workflow already complete
  54. ### 5. Present Continuation Options
  55. After presenting current progress, ask:
  56. "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
  57. [C] Continue to Step {nextStepNumber}"
  58. ## SUCCESS METRICS:
  59. ✅ All previous input documents successfully reloaded
  60. ✅ Current workflow state accurately analyzed and presented
  61. ✅ User confirms understanding of progress
  62. ✅ Correct next step identified and prepared for loading
  63. ## FAILURE MODES:
  64. ❌ Discovering new input documents instead of reloading existing ones
  65. ❌ Modifying content from already completed steps
  66. ❌ Loading wrong next step based on `lastStep` value
  67. ❌ Proceeding without user confirmation of current state
  68. ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
  69. ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
  70. ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
  71. ## WORKFLOW ALREADY COMPLETE?
  72. If `lastStep` indicates the final step is completed:
  73. "Great news! It looks like we've already completed the UX design workflow for {{project_name}}.
  74. The final UX design specification is ready at {planning_artifacts}/ux-design-specification.md with all sections completed through step {finalStepNumber}.
  75. The complete UX design includes visual foundations, user flows, and design specifications ready for implementation.
  76. Would you like me to:
  77. - Review the completed UX design specification with you
  78. - Suggest next workflow steps (like wireframe generation or architecture)
  79. - Start a new UX design revision
  80. What would be most helpful?"
  81. ## NEXT STEP:
  82. After user confirms they're ready to continue, load the appropriate next step file based on the `lastStep` value from frontmatter.
  83. Remember: Do NOT load the next step until user explicitly selects [C] to continue!