@zeyue0329/xiaoma-cli 1.0.48 → 1.0.66

package/src/core/tasks/xiaoma-create-prd/data/upstream-input-contract.md

@@ -0,0 +1,168 @@
+# Analyst → PM Upstream Input Contract
+
+> **Purpose:** Specify what the PM agent (xiaochan / 小蝉) requires from upstream Analyst (xiaofen / 小芬) artifacts when starting `xiaoma-create-prd`. Defines required fields, where they map into the PRD's 9 sections, and how to handle missing fields.
+>
+> **Loaded by:** `steps-c/step-01-init.md` (PRD initialization) and `auto-requirements-pipeline/steps/step-04-create-prd.md` (pipeline delegation).
+>
+> **Authoritative for:** Validation dimension D04 (Brief Coverage) in `xiaoma-validate-prd`.
+
+---
+
+## 1. Scope and Applicability
+
+This contract applies whenever PRD creation is started **from upstream artifacts** rather than from scratch (i.e., `inputDocuments` array is non-empty after step-01 discovery).
+
+It applies in two execution modes:
+
+| Mode                | Triggered by                       | Behavior on missing fields                                              |
+| ------------------- | ---------------------------------- | ----------------------------------------------------------------------- |
+| **Interactive**     | User invokes `pm *create-prd`      | `reverse-ask` policy — pause and request from user / Analyst            |
+| **Pipeline (auto)** | `auto-requirements-pipeline` step 4 | Degrade `reverse-ask` to `placeholder` + write to `pipeline-status.json.blockers[]` |
+
+Pipeline mode never blocks indefinitely on missing input — placeholders are tracked and surfaced by `step-08-finalize` as human-fixup tasks.
+
+---
+
+## 2. Upstream Artifact Catalog
+
+Four artifact types feed PRD creation. Each is produced by a specific Analyst skill / workflow:
+
+| Artifact              | Producer skill                  | Default file pattern                                          | Authoritative section reference              |
+| --------------------- | ------------------------------- | ------------------------------------------------------------- | -------------------------------------------- |
+| **Product Brief**     | `skill:xiaoma-create-product-brief` | `{planning_artifacts}/product-brief.md` or `*brief*.md`     | step files: vision · users · metrics · scope |
+| **Market Research**   | `skill:xiaoma-market-research`  | `{planning_artifacts}/research/market-*.md`                   | step files: customer-behavior · pain-points · decisions · competitive-analysis |
+| **Domain Research**   | `skill:xiaoma-domain-research`  | `{planning_artifacts}/research/domain-*.md`                   | step files: domain-analysis · regulatory-focus · technical-trends |
+| **Technical Research**| `skill:xiaoma-technical-research` | `{planning_artifacts}/research/technical-*.md`              | step files: technical-overview · integration-patterns · architectural-patterns · implementation-research |
+
+PM agent **must** load all four if present. Absence of a research file is acceptable — they are optional inputs. Absence of `product-brief.md` triggers `reverse-ask` (see §4).
+
+---
+
+## 3. Required Fields per Artifact
+
+Each table lists the fields the PM agent extracts. `Source heading` is the H2/H3 the field was written under by the upstream workflow.
+
+### 3.1 Product Brief (`product-brief.md`)
+
+| Field                    | Required | Source heading              | Maps to PRD §        | Missing-field strategy |
+| ------------------------ | -------- | --------------------------- | -------------------- | ---------------------- |
+| `vision_statement`       | yes      | `## Vision`                 | §1 Executive Summary | reverse-ask            |
+| `core_problem`           | yes      | `## Vision` (problem para)  | §1 Executive Summary | reverse-ask            |
+| `target_personas`        | yes      | `## Target Users`           | §1 + §4 Journeys     | reverse-ask            |
+| `value_propositions`     | yes      | `## Vision` (value para)    | §1 Executive Summary | reverse-ask            |
+| `success_metrics_draft`  | yes      | `## Success Metrics`        | §2 Success Criteria  | reverse-ask            |
+| `mvp_scope`              | yes      | `## Scope` (in-scope)       | §3 Product Scope     | reverse-ask            |
+| `out_of_scope`           | partial  | `## Scope` (out-of-scope)   | §3 Product Scope     | placeholder            |
+| `constraints`            | optional | `## Scope` (constraints)    | §3 Product Scope     | skip                   |
+| `differentiation`        | partial  | `## Vision` (diff para)     | §1 + §6 Innovation   | placeholder            |
+
+### 3.2 Market Research (`market-*.md`)
+
+| Field                    | Required | Source heading                | Maps to PRD §           | Missing-field strategy |
+| ------------------------ | -------- | ----------------------------- | ----------------------- | ---------------------- |
+| `customer_behavior`      | partial  | `## Customer Behavior`        | §4 Journeys (context)   | placeholder            |
+| `pain_points`            | partial  | `## Pain Points`              | §1 + §4 + §8 (driver of FRs) | placeholder       |
+| `decision_factors`       | partial  | `## Customer Decisions`       | §1 differentiation · §6 | placeholder            |
+| `competitive_analysis`   | partial  | `## Competitive Analysis`     | §6 Innovation Analysis  | placeholder            |
+
+If `competitive_analysis` is missing AND `domain_complexity` (from `domain-complexity.csv`) is `medium` or `high`, escalate to **reverse-ask** instead of placeholder — competitive context is load-bearing for the Innovation section in those domains.
+
+### 3.3 Domain Research (`domain-*.md`)
+
+| Field                    | Required | Source heading                | Maps to PRD §            | Missing-field strategy |
+| ------------------------ | -------- | ----------------------------- | ------------------------ | ---------------------- |
+| `regulatory_landscape`   | conditional | `## Regulatory Focus`      | §5 Domain Requirements   | `reverse-ask` if domain ∈ high-complexity (healthcare/fintech/govtech/aerospace/etc.); else skip |
+| `domain_terminology`     | partial  | `## Domain Analysis`          | §5 (terminology table)   | placeholder            |
+| `technical_trends`       | partial  | `## Technical Trends`         | §6 + §7                  | skip                   |
+| `competitive_landscape`  | partial  | `## Competitive Landscape`    | §6                       | skip (overlaps with market research) |
+
+### 3.4 Technical Research (`technical-*.md`)
+
+| Field                    | Required | Source heading                | Maps to PRD §             | Missing-field strategy |
+| ------------------------ | -------- | ----------------------------- | ------------------------- | ---------------------- |
+| `technical_overview`     | partial  | `## Technical Overview`       | §7 Project-Type Reqs      | skip                   |
+| `integration_patterns`   | partial  | `## Integration Patterns`     | §7 + §9 NFR (integration latency) | skip            |
+| `architectural_constraints` | partial | `## Architectural Patterns`  | §7 + §9 NFR scalability   | skip                   |
+| `implementation_options` | optional | `## Implementation Research`  | informational only — **DO NOT** copy into PRD (implementation leakage AP-03) | skip |
+
+**Important:** Technical research is the highest-risk source for AP-03 (implementation leakage). PM agent must extract NFR-shaping facts (latency, scale, integration) but **strip technology names, library choices, and concrete architecture decisions** before writing into the PRD.
+
+---
+
+## 4. Missing-Field Strategy
+
+Three policies, escalated by severity:
+
+### 4.1 `reverse-ask` (interactive only)
+
+- PRD workflow pauses at `step-01-init` (or wherever the missing field would be consumed)
+- PM agent writes a clear request: "Need `<field>` from `<artifact>`. Source heading expected: `<heading>`. Continue from upstream Analyst (`/analyst *<command>`) or paste here."
+- Output PRD frontmatter is not yet written; no placeholders are introduced
+- **Pipeline override:** in `auto-requirements-pipeline`, this policy degrades to `placeholder` + a `blockers[]` entry, so the pipeline does not deadlock
+
+### 4.2 `placeholder`
+
+- Insert literal `{{TBD: <field> from <artifact>}}` at the mapped PRD location
+- Add an entry to PRD frontmatter: `tbds: [{field, artifact, suggested_command}]`
+- `step-11-polish` is responsible for surfacing all unresolved `{{TBD: ...}}` markers and refusing to mark the PRD complete until they are resolved or explicitly waived
+- In pipeline mode, `step-08-finalize` aggregates remaining TBDs into a human-fixup task list
+
+### 4.3 `skip`
+
+- Field is treated as not required for this PRD
+- PRD frontmatter `inputDocuments` entry adds `partial: [<field>]` so validation D04 (Brief Coverage) can still report it as a known gap, not silent omission
+
+---
+
+## 5. PRD-Section Reverse Index
+
+A view of the same mapping organized by PRD section. Used by PM agent during `step-02c` through `step-10` — when authoring a section, read the corresponding row to know which upstream fields to consult.
+
+| PRD §                          | Pulls from (artifact.field)                                                                                                                                  | Merge rule                                                                                       |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
+| §1 Executive Summary           | `brief.vision_statement`, `brief.core_problem`, `brief.target_personas`, `brief.value_propositions`, `brief.differentiation`, `market.pain_points` (context) | brief is authoritative; market provides supporting evidence; densify, don't concatenate          |
+| §2 Success Criteria            | `brief.success_metrics_draft`                                                                                                                                | brief metrics are starting drafts; PM must add baseline + measurement + window if missing        |
+| §3 Product Scope               | `brief.mvp_scope`, `brief.out_of_scope`, `brief.constraints`                                                                                                  | brief is authoritative; PM may refine but not silently drop items                                |
+| §4 User Journeys               | `brief.target_personas`, `market.customer_behavior`, `market.pain_points`                                                                                     | brief defines personas; market provides journey context — synthesize, do not copy verbatim       |
+| §5 Domain Requirements         | `domain.regulatory_landscape`, `domain.domain_terminology` + `domain-complexity.csv`                                                                          | CSV defines required `special_sections`; domain research fills them; mark "N/A" if `general` low |
+| §6 Innovation Analysis         | `brief.differentiation`, `market.competitive_analysis`, `market.decision_factors`                                                                             | combine for differentiation narrative; mark "N/A" only if no external competition                |
+| §7 Project-Type Requirements   | `project-types.csv` + `technical.technical_overview`, `technical.integration_patterns`, `technical.architectural_constraints`                                  | CSV defines `required_sections`; technical research informs but tech names are stripped (AP-03)  |
+| §8 Functional Requirements     | derived from §1, §3, §4, §5, §7 — **not** from upstream artifacts directly                                                                                    | FRs synthesized in step-09; upstream feeds §1-§7, FRs trace back to those                         |
+| §9 Non-Functional Requirements | `technical.architectural_constraints` (scale/latency facts), `domain.regulatory_landscape` (compliance NFRs) + `prd-purpose.md` NFR Industry Baselines       | profile selected per §7 project type; baselines are defaults, upstream facts override            |
+
+---
+
+## 6. Pipeline Integration Points
+
+For `auto-requirements-pipeline/workflow.md`:
+
+1. **Step 1 init** — verify `req.md` exists (pipeline trigger doc) and at least one of `product-brief.md` exists. If neither, abort pipeline with a clear error.
+
+2. **Step 4 create-prd (delegation)** — before invoking `xiaoma-create-prd`:
+   - Run `validate_upstream_contract(inputDocuments)`:
+     - Iterate §3 tables; for each `required: yes` field, check existence in source heading
+     - Iterate `conditional` fields; check trigger condition then existence
+     - Output `{planning_artifacts}/contract-check.json`:
+       ```
+       {
+         "passed": false,
+         "missing_required": [{"artifact": "...", "field": "...", "expected_heading": "..."}],
+         "missing_conditional": [...],
+         "applied_policies": {"<field>": "placeholder|reverse-ask|skip"}
+       }
+       ```
+   - In pipeline mode, downgrade all `reverse-ask` to `placeholder` and append entries to `pipeline-status.json.blockers[]`. Continue.
+   - In interactive mode, if any required field missing, halt PRD creation and surface the request.
+
+3. **Step 5 validate-prd** — `step-v-04-brief-coverage-validation` reads `contract-check.json` as evidence:
+   - Pass if `missing_required.length == 0` and `tbds` resolved
+   - Partial if `missing_required.length == 0` and `tbds.length > 0` but ≤ 3
+   - Fail if `missing_required.length > 0` OR `tbds.length > 3`
+
+---
+
+## 7. Versioning and Updates
+
+- This contract is versioned with `prd-purpose.md` (same milestone bumps).
+- When upstream Analyst workflows change their step files (renaming a heading, adding/removing a step), the §3 tables here must be updated in the same PR. The validation refs `xiaoma-validate-prd/data/prd-quality-rubric.csv` D04 row references field names from §3 — keep in sync.
+- Reference paths (file locations, step file names) tracked here are validated by `npm run validate:refs`.

package/src/core/tasks/xiaoma-create-prd/steps-c/step-01-init.md

@@ -0,0 +1,178 @@
+# Step 1: Workflow Initialization
+
+**Progress: Step 1 of 11** - Next: Project Discovery
+
+## STEP GOAL:
+
+Initialize the PRD workflow by detecting continuation state, discovering input documents, and setting up the document structure for collaborative product requirement discovery.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused PM facilitator collaborating with an expert peer
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on initialization and setup - no content generation yet
+- 🚫 FORBIDDEN to look ahead to future steps or assume knowledge from them
+- 💬 Approach: Systematic setup with clear reporting to user
+- 🚪 Detect existing workflow state and handle continuation properly
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking any action
+- 💾 Initialize document structure and update frontmatter appropriately
+- Update frontmatter: add this step name to the end of the steps completed array (it should be the first entry in the steps array since this is step 1)
+- 🚫 FORBIDDEN to load next step until user selects 'C' (Continue)
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Variables from workflow.md are available in memory
+- Focus: Workflow initialization and document setup only
+- Limits: Don't assume knowledge from other steps or create content yet
+- Dependencies: Configuration loaded from workflow.md initialization
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Check for Existing Workflow State
+
+First, check if the output document already exists:
+
+**Workflow State Detection:**
+
+- Look for file at `{outputFile}`
+- If exists, read the complete file including frontmatter
+- If not exists, this is a fresh workflow
+
+### 2. Handle Continuation (If Document Exists)
+
+If the document exists and has frontmatter with `stepsCompleted` BUT `step-12-complete` is NOT in the list, follow the Continuation Protocol since the document is incomplete:
+
+**Continuation Protocol:**
+
+- **STOP immediately** and load `./step-01b-continue.md`
+- Do not proceed with any initialization tasks
+- Let step-01b handle all continuation logic
+- This is an auto-proceed situation - no user choice needed
+
+### 3. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Input Document Discovery
+
+Discover and load context documents using smart discovery. Documents can be in the following locations:
+- {planning_artifacts}/**
+- {output_folder}/**
+- {project_knowledge}/**
+- docs/**
+
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
+
+Try to discover the following:
+- Product Brief (`*brief*.md`)
+- Research Documents (`/*research*.md`)
+- Project Documentation (generally multiple documents might be found for this in the `{project_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
+
+<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
+
+**Loading Rules:**
+
+- Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
+- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
+- index.md is a guide to what's relevant whenever available
+- Track all successfully loaded files in frontmatter `inputDocuments` array
+
+#### B. Create Initial Document
+
+**Document Setup:**
+
+- Copy the template from `../templates/prd-template.md` to `{outputFile}`
+- Initialize frontmatter with proper structure including inputDocuments array.
+
+#### C. Present Initialization Results
+
+**Setup Report to User:**
+
+"Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
+
+**Document Setup:**
+
+- Created: `{outputFile}` from template
+- Initialized frontmatter with workflow state
+
+**Input Documents Discovered:**
+
+- Product briefs: {{briefCount}} files {if briefCount > 0}✓ loaded{else}(none found){/if}
+- Research: {{researchCount}} files {if researchCount > 0}✓ loaded{else}(none found){/if}
+- Brainstorming: {{brainstormingCount}} files {if brainstormingCount > 0}✓ loaded{else}(none found){/if}
+- Project docs: {{projectDocsCount}} files {if projectDocsCount > 0}✓ loaded (brownfield project){else}(none found - greenfield project){/if}
+
+**Files loaded:** {list of specific file names or "No additional documents found"}
+
+{if projectDocsCount > 0}
+📋 **Note:** This is a **brownfield project**. Your existing project documentation has been loaded. In the next step, I'll ask specifically about what new features or changes you want to add to your existing system.
+{/if}
+
+Do you have any other documents you'd like me to include, or shall we continue to the next step?"
+
+### 4. Present MENU OPTIONS
+
+Display menu after setup report:
+
+"[C] Continue - Save this and move to Project Discovery (Step 2 of 11)"
+
+#### Menu Handling Logic:
+
+- IF C: Update output file frontmatter, adding this step name to the end of the list of stepsCompleted, then read fully and follow: ./step-02-discovery.md
+- IF user provides additional files: Load them, update inputDocuments and documentCounts, redisplay report
+- IF user asks questions: Answer and redisplay menu
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [frontmatter properly updated with this step added to stepsCompleted and documentCounts], will you then read fully and follow: `./step-02-discovery.md` to begin project discovery.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Existing workflow detected and properly handed off to step-01b
+- Fresh workflow initialized with template and proper frontmatter
+- Input documents discovered and loaded using sharded-first logic
+- All discovered files tracked in frontmatter `inputDocuments`
+- User clearly informed of brownfield vs greenfield status
+- Menu presented and user input handled correctly
+- Frontmatter updated with this step name added to stepsCompleted before proceeding
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding with fresh initialization when existing workflow exists
+- Not updating frontmatter with discovered input documents
+- **Not storing document counts in frontmatter**
+- Creating document without proper template structure
+- Not checking sharded folders first before whole files
+- Not reporting discovered documents to user clearly
+- Proceeding without user selecting 'C' (Continue)
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/core/tasks/xiaoma-create-prd/steps-c/step-01b-continue.md

@@ -0,0 +1,161 @@
+# Step 1B: Workflow Continuation
+
+## STEP GOAL:
+
+Resume the PRD workflow from where it was left off, ensuring smooth continuation with full context restoration.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused PM facilitator collaborating with an expert peer
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ Resume workflow from exact point where it was interrupted
+
+### Step-Specific Rules:
+
+- 💬 FOCUS on understanding where we left off and continuing appropriately
+- 🚫 FORBIDDEN to modify content completed in previous steps
+- 📖 Only reload documents that were already tracked in `inputDocuments`
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking action
+- Update frontmatter: add this step name to the end of the steps completed array
+- 📖 Only load documents that were already tracked in `inputDocuments`
+- 🚫 FORBIDDEN to discover new input documents during continuation
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Current document and frontmatter are already loaded
+- Focus: Workflow state analysis and continuation logic only
+- Limits: Don't assume knowledge beyond what's in the document
+- Dependencies: Existing workflow state from previous session
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Analyze Current State
+
+**State Assessment:**
+Review the frontmatter to understand:
+
+- `stepsCompleted`: Array of completed step filenames
+- Last element of `stepsCompleted` array: The most recently completed step
+- `inputDocuments`: What context was already loaded
+- All other frontmatter variables
+
+### 2. Restore Context Documents
+
+**Context Reloading:**
+
+- For each document in `inputDocuments`, load the complete file
+- This ensures you have full context for continuation
+- Don't discover new documents - only reload what was previously processed
+
+### 3. Determine Next Step
+
+**Step Sequence Lookup:**
+
+Use the following ordered sequence to determine the next step from the last completed step:
+
+| Last Completed | Next Step |
+|---|---|
+| step-01-init.md | step-02-discovery.md |
+| step-02-discovery.md | step-02b-vision.md |
+| step-02b-vision.md | step-02c-executive-summary.md |
+| step-02c-executive-summary.md | step-03-success.md |
+| step-03-success.md | step-04-journeys.md |
+| step-04-journeys.md | step-05-domain.md |
+| step-05-domain.md | step-06-innovation.md |
+| step-06-innovation.md | step-07-project-type.md |
+| step-07-project-type.md | step-08-scoping.md |
+| step-08-scoping.md | step-09-functional.md |
+| step-09-functional.md | step-10-nonfunctional.md |
+| step-10-nonfunctional.md | step-11-polish.md |
+| step-11-polish.md | step-12-complete.md |
+
+1. Get the last element from the `stepsCompleted` array
+2. Look it up in the table above to find the next step
+3. That's the next step to load!
+
+**Example:**
+- If `stepsCompleted = ["step-01-init.md", "step-02-discovery.md", "step-03-success.md"]`
+- Last element is `"step-03-success.md"`
+- Table lookup → next step is `./step-04-journeys.md`
+
+### 4. Handle Workflow Completion
+
+**If `stepsCompleted` array contains `"step-12-complete.md"`:**
+"Great news! It looks like we've already completed the PRD workflow for {{project_name}}.
+
+The final document is ready at `{outputFile}` with all sections completed.
+
+Would you like me to:
+
+- Review the completed PRD with you
+- Suggest next workflow steps (like architecture or epic creation)
+- Start a new PRD revision
+
+What would be most helpful?"
+
+### 5. Present Current Progress
+
+**If workflow not complete:**
+"Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.
+
+**Current Progress:**
+- Last completed: {last step filename from stepsCompleted array}
+- Next up: {next step from lookup table}
+- Context documents available: {len(inputDocuments)} files
+
+**Document Status:**
+- Current PRD document is ready with all completed sections
+- Ready to continue from where we left off
+
+Does this look right, or do you want to make any adjustments before we proceed?"
+
+### 6. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to {next step name}"
+
+#### Menu Handling Logic:
+
+- IF C: Read fully and follow the next step determined from the lookup table in step 3
+- IF Any other comments or queries: respond and redisplay menu
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+
+## CRITICAL STEP COMPLETION NOTE
+
+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.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- All previous input documents successfully reloaded
+- Current workflow state accurately analyzed and presented
+- User confirms understanding of progress before continuation
+- Correct next step identified and prepared for loading
+
+### ❌ SYSTEM FAILURE:
+
+- Discovering new input documents instead of reloading existing ones
+- Modifying content from already completed steps
+- Failing to determine the next step from the lookup table
+- Proceeding without user confirmation of current state
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.