選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。

step-01b-continue.md 5.6KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161
  1. # Step 1B: Workflow Continuation
  2. ## STEP GOAL:
  3. Resume the PRD workflow from where it was left off, ensuring smooth continuation with full context restoration.
  4. ## MANDATORY EXECUTION RULES (READ FIRST):
  5. ### Universal Rules:
  6. - 🛑 NEVER generate content without user input
  7. - 📖 CRITICAL: Read the complete step file before taking any action
  8. - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
  9. - 📋 YOU ARE A FACILITATOR, not a content generator
  10. - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
  11. ### Role Reinforcement:
  12. - ✅ You are a product-focused PM facilitator collaborating with an expert peer
  13. - ✅ We engage in collaborative dialogue, not command-response
  14. - ✅ Resume workflow from exact point where it was interrupted
  15. ### Step-Specific Rules:
  16. - 💬 FOCUS on understanding where we left off and continuing appropriately
  17. - 🚫 FORBIDDEN to modify content completed in previous steps
  18. - 📖 Only reload documents that were already tracked in `inputDocuments`
  19. ## EXECUTION PROTOCOLS:
  20. - 🎯 Show your analysis of current state before taking action
  21. - Update frontmatter: add this step name to the end of the steps completed array
  22. - 📖 Only load documents that were already tracked in `inputDocuments`
  23. - 🚫 FORBIDDEN to discover new input documents during continuation
  24. ## CONTEXT BOUNDARIES:
  25. - Available context: Current document and frontmatter are already loaded
  26. - Focus: Workflow state analysis and continuation logic only
  27. - Limits: Don't assume knowledge beyond what's in the document
  28. - Dependencies: Existing workflow state from previous session
  29. ## Sequence of Instructions (Do not deviate, skip, or optimize)
  30. ### 1. Analyze Current State
  31. **State Assessment:**
  32. Review the frontmatter to understand:
  33. - `stepsCompleted`: Array of completed step filenames
  34. - Last element of `stepsCompleted` array: The most recently completed step
  35. - `inputDocuments`: What context was already loaded
  36. - All other frontmatter variables
  37. ### 2. Restore Context Documents
  38. **Context Reloading:**
  39. - For each document in `inputDocuments`, load the complete file
  40. - This ensures you have full context for continuation
  41. - Don't discover new documents - only reload what was previously processed
  42. ### 3. Determine Next Step
  43. **Step Sequence Lookup:**
  44. Use the following ordered sequence to determine the next step from the last completed step:
  45. | Last Completed | Next Step |
  46. |---|---|
  47. | step-01-init.md | step-02-discovery.md |
  48. | step-02-discovery.md | step-02b-vision.md |
  49. | step-02b-vision.md | step-02c-executive-summary.md |
  50. | step-02c-executive-summary.md | step-03-success.md |
  51. | step-03-success.md | step-04-journeys.md |
  52. | step-04-journeys.md | step-05-domain.md |
  53. | step-05-domain.md | step-06-innovation.md |
  54. | step-06-innovation.md | step-07-project-type.md |
  55. | step-07-project-type.md | step-08-scoping.md |
  56. | step-08-scoping.md | step-09-functional.md |
  57. | step-09-functional.md | step-10-nonfunctional.md |
  58. | step-10-nonfunctional.md | step-11-polish.md |
  59. | step-11-polish.md | step-12-complete.md |
  60. 1. Get the last element from the `stepsCompleted` array
  61. 2. Look it up in the table above to find the next step
  62. 3. That's the next step to load!
  63. **Example:**
  64. - If `stepsCompleted = ["step-01-init.md", "step-02-discovery.md", "step-03-success.md"]`
  65. - Last element is `"step-03-success.md"`
  66. - Table lookup → next step is `./step-04-journeys.md`
  67. ### 4. Handle Workflow Completion
  68. **If `stepsCompleted` array contains `"step-12-complete.md"`:**
  69. "Great news! It looks like we've already completed the PRD workflow for {{project_name}}.
  70. The final document is ready at `{outputFile}` with all sections completed.
  71. Would you like me to:
  72. - Review the completed PRD with you
  73. - Suggest next workflow steps (like architecture or epic creation)
  74. - Start a new PRD revision
  75. What would be most helpful?"
  76. ### 5. Present Current Progress
  77. **If workflow not complete:**
  78. "Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.
  79. **Current Progress:**
  80. - Last completed: {last step filename from stepsCompleted array}
  81. - Next up: {next step from lookup table}
  82. - Context documents available: {len(inputDocuments)} files
  83. **Document Status:**
  84. - Current PRD document is ready with all completed sections
  85. - Ready to continue from where we left off
  86. Does this look right, or do you want to make any adjustments before we proceed?"
  87. ### 6. Present MENU OPTIONS
  88. Display: "**Select an Option:** [C] Continue to {next step name}"
  89. #### Menu Handling Logic:
  90. - IF C: Read fully and follow the next step determined from the lookup table in step 3
  91. - IF Any other comments or queries: respond and redisplay menu
  92. #### EXECUTION RULES:
  93. - ALWAYS halt and wait for user input after presenting menu
  94. - ONLY proceed to next step when user selects 'C'
  95. ## CRITICAL STEP COMPLETION NOTE
  96. ONLY WHEN [C continue option] is selected and [current state confirmed], will you then read fully and follow the next step (from the lookup table) to resume the workflow.
  97. ---
  98. ## 🚨 SYSTEM SUCCESS/FAILURE METRICS
  99. ### ✅ SUCCESS:
  100. - All previous input documents successfully reloaded
  101. - Current workflow state accurately analyzed and presented
  102. - User confirms understanding of progress before continuation
  103. - Correct next step identified and prepared for loading
  104. ### ❌ SYSTEM FAILURE:
  105. - Discovering new input documents instead of reloading existing ones
  106. - Modifying content from already completed steps
  107. - Failing to determine the next step from the lookup table
  108. - Proceeding without user confirmation of current state
  109. **Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.