- Rewrite README.md with current architecture, features and stack - Update docs/API.md with all current endpoints (corporate, BI, client 360) - Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL - Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente) - Add docs/INDEX.md documentation index - Add PROJETO.md comprehensive project reference - Add BI-CCC-Implementation-Guide.md - Include AI agent configs (.claude, .agents, .gemini, _bmad) - Add netbird VPN configuration - Add status report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
162 lines
5.6 KiB
Markdown
162 lines
5.6 KiB
Markdown
# 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.
|