siesa-agents 2.1.42 → 2.1.44
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards/architecture-patterns.md +5 -5
- package/bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards/backend-standards.md +1 -1
- package/bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards/technology-stack.md +3 -3
- package/bmad/bmm/workflows/5-documentation/README.md +234 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/data/audience-types.csv +5 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/data/diagram-types.csv +6 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/data/section-structure.csv +10 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/steps/step-01-init.md +313 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/steps/step-01b-continue.md +268 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/steps/step-02-seleccion-epicas.md +212 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/steps/step-03-analisis-fuentes.md +308 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/steps/step-04-elicitacion.md +332 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/steps/step-05-generacion-espanol.md +608 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/steps/step-06-traduccion-ingles.md +607 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/steps/step-07-validacion-guardado.md +549 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/templates/user-guide-template-en.md +50 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/templates/user-guide-template-es.md +50 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/workflow-plan-create-user-guide.md +949 -0
- package/bmad/bmm/workflows/5-documentation/create-user-guide/workflow.md +61 -0
- package/claude/commands/bmad/bmm/workflows/create-user-guide.md +5 -0
- package/gemini/commands/bmad-workflow-bmm-create-user-guide.toml +4 -0
- package/package.json +1 -1
|
@@ -0,0 +1,268 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: 'step-01b-continue'
|
|
3
|
+
description: 'Handle workflow continuation from previous session for user guide generation'
|
|
4
|
+
|
|
5
|
+
# Path Definitions
|
|
6
|
+
workflow_path: '{project-root}/_bmad/bmm/workflows/5-documentation/create-user-guide'
|
|
7
|
+
|
|
8
|
+
# File References
|
|
9
|
+
thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
|
|
10
|
+
workflowFile: '{workflow_path}/workflow.md'
|
|
11
|
+
outputFileSpanish: '{output_folder}/documentation-artifacts/user-guide/es/{audience}-guide.md'
|
|
12
|
+
|
|
13
|
+
# Step files (for reading completed steps)
|
|
14
|
+
step02File: '{workflow_path}/steps/step-02-seleccion-epicas.md'
|
|
15
|
+
step03File: '{workflow_path}/steps/step-03-analisis-fuentes.md'
|
|
16
|
+
step04File: '{workflow_path}/steps/step-04-elicitacion.md'
|
|
17
|
+
step05File: '{workflow_path}/steps/step-05-generacion-espanol.md'
|
|
18
|
+
step06File: '{workflow_path}/steps/step-06-traduccion-ingles.md'
|
|
19
|
+
step07File: '{workflow_path}/steps/step-07-validacion-guardado.md'
|
|
20
|
+
|
|
21
|
+
# Task References
|
|
22
|
+
advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
|
|
23
|
+
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
|
|
24
|
+
|
|
25
|
+
# Config
|
|
26
|
+
bmmConfig: '{project-root}/_bmad/bmm/config.yaml'
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
# Step 1B: Continuación del Workflow
|
|
30
|
+
|
|
31
|
+
## STEP GOAL:
|
|
32
|
+
|
|
33
|
+
Reanudar el workflow de generación de guías de usuario desde donde se dejó, asegurando una continuación fluida sin pérdida de contexto o progreso. Analizar el estado actual, cargar el contexto previo y determinar el siguiente step a ejecutar.
|
|
34
|
+
|
|
35
|
+
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
36
|
+
|
|
37
|
+
### Universal Rules:
|
|
38
|
+
|
|
39
|
+
- 🛑 NEVER generate content without user input
|
|
40
|
+
- 📖 CRITICAL: Read the complete step file before taking any action
|
|
41
|
+
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
|
42
|
+
- 📋 YOU ARE A FACILITATOR, not a content generator
|
|
43
|
+
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
|
44
|
+
|
|
45
|
+
### Role Reinforcement:
|
|
46
|
+
|
|
47
|
+
- ✅ You are a technical writer and documentation specialist
|
|
48
|
+
- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
|
|
49
|
+
- ✅ We engage in collaborative dialogue, not command-response
|
|
50
|
+
- ✅ You bring documentation expertise, user brings project knowledge
|
|
51
|
+
- ✅ Maintain collaborative professional tone throughout
|
|
52
|
+
|
|
53
|
+
### Step-Specific Rules:
|
|
54
|
+
|
|
55
|
+
- 🎯 Focus ONLY on analyzing and resuming workflow state
|
|
56
|
+
- 🚫 FORBIDDEN to modify content completed in previous steps
|
|
57
|
+
- 💬 Maintain continuity with previous sessions
|
|
58
|
+
- 🚪 DETECT exact continuation point from frontmatter
|
|
59
|
+
|
|
60
|
+
## EXECUTION PROTOCOLS:
|
|
61
|
+
|
|
62
|
+
- 🎯 Show your analysis of current state before taking action
|
|
63
|
+
- 💾 Keep existing frontmatter `stepsCompleted` values intact
|
|
64
|
+
- 📖 Review content already generated in outputFile
|
|
65
|
+
- 🚫 FORBIDDEN to modify content completed in previous steps
|
|
66
|
+
- 📝 Update frontmatter.last_modified when resuming
|
|
67
|
+
|
|
68
|
+
## CONTEXT BOUNDARIES:
|
|
69
|
+
|
|
70
|
+
- Current user guide document (Spanish version) is already loaded
|
|
71
|
+
- Previous context = complete document + existing frontmatter
|
|
72
|
+
- Data collected in previous sessions (audience, epics, preferences)
|
|
73
|
+
- Last completed step = last value in `stepsCompleted` array
|
|
74
|
+
|
|
75
|
+
## CONTINUATION SEQUENCE:
|
|
76
|
+
|
|
77
|
+
### 1. Load Configuration
|
|
78
|
+
|
|
79
|
+
Load `{bmmConfig}` to resolve:
|
|
80
|
+
- `{project_name}`
|
|
81
|
+
- `{communication_language}`
|
|
82
|
+
- `{document_output_language}`
|
|
83
|
+
|
|
84
|
+
Communicate with user in `{communication_language}` (typically Spanish).
|
|
85
|
+
|
|
86
|
+
### 2. Analyze Current State
|
|
87
|
+
|
|
88
|
+
Read the complete Spanish output file at `{outputFileSpanish}` including frontmatter:
|
|
89
|
+
|
|
90
|
+
Extract from frontmatter:
|
|
91
|
+
- `stepsCompleted`: Array of completed step numbers (e.g., [1, 2, 3, 4])
|
|
92
|
+
- `currentStep`: Name of the last step (e.g., "step-04-elicitacion")
|
|
93
|
+
- `target_audience`: Audience selected (enduser/admin/api/mixed)
|
|
94
|
+
- `epics_selected`: Which epics were selected for documentation
|
|
95
|
+
- `technical_level`: Technical level chosen
|
|
96
|
+
- `include_troubleshooting`: Whether troubleshooting section is included
|
|
97
|
+
- `features_documented`: Count of features documented
|
|
98
|
+
- `workflows_documented`: Count of workflows documented
|
|
99
|
+
- `translation_completed`: Whether English version is done
|
|
100
|
+
|
|
101
|
+
The **last step completed** is the rightmost value in `stepsCompleted` array.
|
|
102
|
+
|
|
103
|
+
### 3. Read Completed Step Files
|
|
104
|
+
|
|
105
|
+
For each step number in `stepsCompleted` (excluding step 1):
|
|
106
|
+
|
|
107
|
+
**Example:** If `stepsCompleted: [1, 2, 3, 4]`:
|
|
108
|
+
|
|
109
|
+
Read these step files to understand what was accomplished:
|
|
110
|
+
- `{step02File}` - Epic selection
|
|
111
|
+
- `{step03File}` - Artifact analysis
|
|
112
|
+
- `{step04File}` - Information elicitation
|
|
113
|
+
|
|
114
|
+
The last completed step file will indicate the next step via `nextStepFile` reference.
|
|
115
|
+
|
|
116
|
+
### 4. Review Previous Output Content
|
|
117
|
+
|
|
118
|
+
Scan the Spanish output document to understand:
|
|
119
|
+
- Which sections have been generated (Introduction, Getting Started, Features, etc.)
|
|
120
|
+
- How many features are documented
|
|
121
|
+
- How many workflows are documented
|
|
122
|
+
- Presence of diagrams, screenshots, citations
|
|
123
|
+
- Current completeness status
|
|
124
|
+
|
|
125
|
+
### 5. Determine Next Step
|
|
126
|
+
|
|
127
|
+
Based on `stepsCompleted` array:
|
|
128
|
+
|
|
129
|
+
| Last Step | Next Step File | Next Step Description |
|
|
130
|
+
|-----------|----------------|------------------------|
|
|
131
|
+
| 1 | step-02-seleccion-epicas.md | Seleccionar épicas a documentar |
|
|
132
|
+
| 2 | step-03-analisis-fuentes.md | Analizar artefactos del proyecto |
|
|
133
|
+
| 3 | step-04-elicitacion.md | Elicitar información adicional |
|
|
134
|
+
| 4 | step-05-generacion-espanol.md | Generar contenido en español |
|
|
135
|
+
| 5 | step-06-traduccion-ingles.md | Traducir a inglés |
|
|
136
|
+
| 6 | step-07-validacion-guardado.md | Validar y guardar |
|
|
137
|
+
|
|
138
|
+
If step 7 is completed → workflow is fully finished (shouldn't reach here)
|
|
139
|
+
|
|
140
|
+
### 6. Welcome Back Dialog
|
|
141
|
+
|
|
142
|
+
Present context-aware welcome message:
|
|
143
|
+
|
|
144
|
+
"👋 **¡Bienvenido de vuelta!**
|
|
145
|
+
|
|
146
|
+
He detectado que tenemos un workflow de guía de usuario en progreso para **{project_name}**.
|
|
147
|
+
|
|
148
|
+
**Estado del Workflow:**
|
|
149
|
+
- Audiencia objetivo: **{target_audience_name}**
|
|
150
|
+
- Steps completados: **{count} de 7**
|
|
151
|
+
- Último step: **{last_step_description}**
|
|
152
|
+
- Épicas seleccionadas: **{epics_selected_count}**
|
|
153
|
+
- Features documentadas: **{features_documented}** (si aplica)
|
|
154
|
+
- Estado: **{review_status}**
|
|
155
|
+
|
|
156
|
+
**Próximo Step:**
|
|
157
|
+
Estamos listos para continuar con: **{next_step_description}**
|
|
158
|
+
|
|
159
|
+
¿Todo sigue siendo válido o hay algo que necesitas ajustar antes de continuar?"
|
|
160
|
+
|
|
161
|
+
### 7. Validate Continuation Intent
|
|
162
|
+
|
|
163
|
+
Offer optional review:
|
|
164
|
+
|
|
165
|
+
"**Opciones de Revisión:**
|
|
166
|
+
|
|
167
|
+
**[S]** Resumen - Ver resumen detallado del progreso
|
|
168
|
+
**[M]** Modificar - Ajustar configuración o decisiones previas
|
|
169
|
+
**[C]** Continuar - Proceder directo al siguiente step
|
|
170
|
+
|
|
171
|
+
¿Qué deseas hacer?"
|
|
172
|
+
|
|
173
|
+
#### Menu Handling for Review Options:
|
|
174
|
+
|
|
175
|
+
- **IF S (Resumen):**
|
|
176
|
+
- Display detailed summary:
|
|
177
|
+
```
|
|
178
|
+
**Resumen Completo:**
|
|
179
|
+
|
|
180
|
+
1. Configuración Inicial (step-01):
|
|
181
|
+
- Audiencia: {target_audience}
|
|
182
|
+
- Fecha inicio: {generated_date}
|
|
183
|
+
|
|
184
|
+
2. Selección de Épicas (step-02):
|
|
185
|
+
- Épicas incluidas: {epics_selected}
|
|
186
|
+
- Épicas excluidas: {epics_excluded}
|
|
187
|
+
|
|
188
|
+
3. Análisis de Fuentes (step-03):
|
|
189
|
+
- PRDs encontrados: {prd_docs_count}
|
|
190
|
+
- Épicas analizadas: {epics_count}
|
|
191
|
+
- Arquitectura: {architecture_docs_count}
|
|
192
|
+
|
|
193
|
+
4. Elicitación (step-04):
|
|
194
|
+
- Nivel técnico: {technical_level}
|
|
195
|
+
- Troubleshooting: {include_troubleshooting}
|
|
196
|
+
- Escenarios adicionales: {additional_scenarios}
|
|
197
|
+
|
|
198
|
+
5-7. Generación/Traducción/Validación:
|
|
199
|
+
- Features: {features_documented}
|
|
200
|
+
- Workflows: {workflows_documented}
|
|
201
|
+
- Diagramas: {diagrams_generated}
|
|
202
|
+
- Screenshots: {screenshot_placeholders}
|
|
203
|
+
```
|
|
204
|
+
- Return to menu
|
|
205
|
+
|
|
206
|
+
- **IF M (Modificar):**
|
|
207
|
+
- "¿Qué deseas modificar?
|
|
208
|
+
- [A] Audiencia objetivo
|
|
209
|
+
- [E] Épicas seleccionadas
|
|
210
|
+
- [P] Preferencias (nivel técnico, troubleshooting)
|
|
211
|
+
- [X] Cancelar modificaciones"
|
|
212
|
+
- Handle modifications (may require re-running some steps)
|
|
213
|
+
- Return to menu
|
|
214
|
+
|
|
215
|
+
- **IF C (Continuar):**
|
|
216
|
+
- Proceed to step 8
|
|
217
|
+
|
|
218
|
+
### 8. Update Continuation Metadata
|
|
219
|
+
|
|
220
|
+
Before loading next step:
|
|
221
|
+
- Update `frontmatter.last_modified` with current timestamp
|
|
222
|
+
- Keep `frontmatter.stepsCompleted` intact (don't modify)
|
|
223
|
+
- Optionally log continuation event
|
|
224
|
+
|
|
225
|
+
### 9. Present MENU OPTIONS
|
|
226
|
+
|
|
227
|
+
Display: **Select an Option:** [C] Continue to {next_step_name}
|
|
228
|
+
|
|
229
|
+
#### EXECUTION RULES:
|
|
230
|
+
|
|
231
|
+
- ALWAYS halt and wait for user input after presenting menu
|
|
232
|
+
- ONLY proceed to next step when user selects 'C'
|
|
233
|
+
- User can chat or ask questions - always respond and then redisplay menu
|
|
234
|
+
|
|
235
|
+
#### Menu Handling Logic:
|
|
236
|
+
|
|
237
|
+
- IF C: Update last_modified, then load, read entire file, then execute **{nextStepFile}**
|
|
238
|
+
- IF Any other: Respond and redisplay menu
|
|
239
|
+
|
|
240
|
+
## CRITICAL STEP COMPLETION NOTE
|
|
241
|
+
|
|
242
|
+
ONLY WHEN C is selected and continuation analysis is complete, will you then load, read entire file, then execute the determined next step file to resume the workflow.
|
|
243
|
+
|
|
244
|
+
---
|
|
245
|
+
|
|
246
|
+
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
247
|
+
|
|
248
|
+
### ✅ SUCCESS:
|
|
249
|
+
|
|
250
|
+
- Configuration loaded successfully
|
|
251
|
+
- Current state analyzed from frontmatter
|
|
252
|
+
- Completed steps reviewed
|
|
253
|
+
- Output content analyzed
|
|
254
|
+
- Next step determined correctly
|
|
255
|
+
- User welcomed with context
|
|
256
|
+
- Continuation metadata updated
|
|
257
|
+
- Ready to proceed to next step
|
|
258
|
+
|
|
259
|
+
### ❌ SYSTEM FAILURE:
|
|
260
|
+
|
|
261
|
+
- Not reading frontmatter correctly
|
|
262
|
+
- Incorrect determination of next step
|
|
263
|
+
- Modifying completed content
|
|
264
|
+
- Losing context from previous session
|
|
265
|
+
- Not updating continuation metadata
|
|
266
|
+
- Loading wrong next step
|
|
267
|
+
|
|
268
|
+
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
package/bmad/bmm/workflows/5-documentation/create-user-guide/steps/step-02-seleccion-epicas.md
ADDED
|
@@ -0,0 +1,212 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: 'step-02-seleccion-epicas'
|
|
3
|
+
description: 'Select which epics to include in the user guide'
|
|
4
|
+
|
|
5
|
+
# Path Definitions
|
|
6
|
+
workflow_path: '{project-root}/_bmad/bmm/workflows/5-documentation/create-user-guide'
|
|
7
|
+
|
|
8
|
+
# File References
|
|
9
|
+
thisStepFile: '{workflow_path}/steps/step-02-seleccion-epicas.md'
|
|
10
|
+
nextStepFile: '{workflow_path}/steps/step-03-analisis-fuentes.md'
|
|
11
|
+
workflowFile: '{workflow_path}/workflow.md'
|
|
12
|
+
outputFileSpanish: '{output_folder}/documentation-artifacts/user-guide/es/{audience}-guide.md'
|
|
13
|
+
|
|
14
|
+
# Task References
|
|
15
|
+
advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
|
|
16
|
+
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
|
|
17
|
+
|
|
18
|
+
# Config
|
|
19
|
+
bmmConfig: '{project-root}/_bmad/bmm/config.yaml'
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
# Step 2: Selección de Épicas
|
|
23
|
+
|
|
24
|
+
## STEP GOAL:
|
|
25
|
+
|
|
26
|
+
Identificar y presentar todas las épicas disponibles del proyecto al usuario, permitiéndole seleccionar cuáles deben incluirse en la guía de usuario. Registrar épicas seleccionadas/excluidas en el frontmatter del documento de output.
|
|
27
|
+
|
|
28
|
+
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
29
|
+
|
|
30
|
+
### Universal Rules:
|
|
31
|
+
|
|
32
|
+
- 🛑 NEVER generate content without user input
|
|
33
|
+
- 📖 CRITICAL: Read the complete step file before taking any action
|
|
34
|
+
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
|
35
|
+
- 📋 YOU ARE A FACILITATOR, not a content generator
|
|
36
|
+
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
|
37
|
+
|
|
38
|
+
### Role Reinforcement:
|
|
39
|
+
|
|
40
|
+
- ✅ You are a technical writer and documentation specialist
|
|
41
|
+
- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
|
|
42
|
+
- ✅ We engage in collaborative dialogue, not command-response
|
|
43
|
+
- ✅ You bring documentation expertise, user brings project knowledge
|
|
44
|
+
- ✅ Maintain collaborative professional tone throughout
|
|
45
|
+
|
|
46
|
+
### Step-Specific Rules:
|
|
47
|
+
|
|
48
|
+
- 🎯 Focus ONLY on epic discovery and selection
|
|
49
|
+
- 🚫 FORBIDDEN to read epic content in this step (that happens in step-03)
|
|
50
|
+
- 💬 Present epics clearly and wait for user selection
|
|
51
|
+
- 🚫 DO NOT make assumptions about which epics to include
|
|
52
|
+
|
|
53
|
+
## EXECUTION PROTOCOLS:
|
|
54
|
+
|
|
55
|
+
- 🎯 Scan multiple locations for epic files
|
|
56
|
+
- 💾 Update frontmatter with epic selection
|
|
57
|
+
- 📖 Set `stepsCompleted: [1, 2]` before loading next step
|
|
58
|
+
- 🚫 FORBIDDEN to proceed without user confirmation
|
|
59
|
+
|
|
60
|
+
## CONTEXT BOUNDARIES:
|
|
61
|
+
|
|
62
|
+
- Spanish output document created in step-01
|
|
63
|
+
- Target audience configured in frontmatter
|
|
64
|
+
- Epic files need to be discovered and listed
|
|
65
|
+
- No content reading yet - just file discovery
|
|
66
|
+
|
|
67
|
+
## EXECUTION SEQUENCE:
|
|
68
|
+
|
|
69
|
+
### 1. Load Consolidated Epics File
|
|
70
|
+
|
|
71
|
+
Search for consolidated epics file in:
|
|
72
|
+
|
|
73
|
+
**Primary location:**
|
|
74
|
+
- `{planning_artifacts}/epics.md`
|
|
75
|
+
|
|
76
|
+
**Fallback locations (if primary not found):**
|
|
77
|
+
- `{implementation_artifacts}/epics.md`
|
|
78
|
+
- `{project_knowledge}/epics.md`
|
|
79
|
+
|
|
80
|
+
**Read and Parse Epics:**
|
|
81
|
+
1. Read the complete epics.md file
|
|
82
|
+
2. Search for epic headers matching pattern: `### Epic X: [Title]` (H3 headers)
|
|
83
|
+
3. Extract epic number and title from each header
|
|
84
|
+
4. Add to discovery list with: number, title, file_path
|
|
85
|
+
|
|
86
|
+
### 2. Present Epics to User
|
|
87
|
+
|
|
88
|
+
Display in Spanish (using `{communication_language}`):
|
|
89
|
+
|
|
90
|
+
"📚 **Épicas Encontradas en el Proyecto**
|
|
91
|
+
|
|
92
|
+
He encontrado las siguientes épicas disponibles para documentar:
|
|
93
|
+
|
|
94
|
+
{for each epic in sorted order by number}
|
|
95
|
+
- **Epic {number}:** {title}
|
|
96
|
+
Archivo: {relative_path}
|
|
97
|
+
{end for}
|
|
98
|
+
|
|
99
|
+
**Total:** {count} épicas encontradas"
|
|
100
|
+
|
|
101
|
+
### 3. Request Epic Selection (PRESCRIPTIVE)
|
|
102
|
+
|
|
103
|
+
Ask user with exact text:
|
|
104
|
+
|
|
105
|
+
"¿Cuáles épicas deseas incluir en la guía de usuario?
|
|
106
|
+
|
|
107
|
+
**[A]** Todas las épicas - Incluir todas las {count} épicas encontradas
|
|
108
|
+
|
|
109
|
+
**[E]** Épicas específicas - Proporcionar números separados por comas (ej: 1,3,5)
|
|
110
|
+
|
|
111
|
+
**[X]** Excluir específicas - Incluir todas EXCEPTO las que especifiques (ej: 2,4)
|
|
112
|
+
|
|
113
|
+
Por favor selecciona una opción (A/E/X):"
|
|
114
|
+
|
|
115
|
+
HALT and wait for user input.
|
|
116
|
+
|
|
117
|
+
### 4. Parse User Response
|
|
118
|
+
|
|
119
|
+
**IF A (All epics):**
|
|
120
|
+
- Set `epics_selected` = [all epic numbers found]
|
|
121
|
+
- Set `epics_excluded` = []
|
|
122
|
+
- Message: "✅ Incluidas: {count} épicas (todas)"
|
|
123
|
+
|
|
124
|
+
**IF E (Specific epics):**
|
|
125
|
+
- Parse comma-separated numbers from user input
|
|
126
|
+
- Validate each number exists in discovered epics
|
|
127
|
+
- Set `epics_selected` = [parsed numbers]
|
|
128
|
+
- Set `epics_excluded` = [remaining numbers]
|
|
129
|
+
- Message: "✅ Incluidas: {selected_count} épicas | Excluidas: {excluded_count}"
|
|
130
|
+
|
|
131
|
+
**IF X (Exclude specific):**
|
|
132
|
+
- Parse comma-separated numbers from user input
|
|
133
|
+
- Validate each number exists in discovered epics
|
|
134
|
+
- Set `epics_selected` = [all numbers EXCEPT excluded]
|
|
135
|
+
- Set `epics_excluded` = [parsed numbers]
|
|
136
|
+
- Message: "✅ Incluidas: {selected_count} épicas | Excluidas: {excluded_count}"
|
|
137
|
+
|
|
138
|
+
### 5. Update Frontmatter
|
|
139
|
+
|
|
140
|
+
Update `{outputFileSpanish}` frontmatter with:
|
|
141
|
+
|
|
142
|
+
```yaml
|
|
143
|
+
epics_selected: [1, 3, 5] # Example - epic numbers from consolidated file
|
|
144
|
+
epics_excluded: [2, 4] # Example - epic numbers excluded
|
|
145
|
+
source_artifacts:
|
|
146
|
+
epics_file: "path/to/epics.md" # Single consolidated epics file
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
### 6. Confirmation Message
|
|
150
|
+
|
|
151
|
+
"✅ **Selección de Épicas Completada**
|
|
152
|
+
|
|
153
|
+
Documentaremos las siguientes épicas:
|
|
154
|
+
{for each selected epic}
|
|
155
|
+
- Epic {number}: {title}
|
|
156
|
+
{end for}
|
|
157
|
+
|
|
158
|
+
Excluidas: {excluded_count} épicas
|
|
159
|
+
|
|
160
|
+
Procediendo al análisis de documentación..."
|
|
161
|
+
|
|
162
|
+
### 7. Update State Before Next Step
|
|
163
|
+
|
|
164
|
+
Before loading next step:
|
|
165
|
+
- Ensure frontmatter.stepsCompleted = [1, 2]
|
|
166
|
+
- Ensure frontmatter.currentStep = "step-03-analisis-fuentes"
|
|
167
|
+
- Save outputFileSpanish
|
|
168
|
+
|
|
169
|
+
### 8. Present MENU OPTIONS
|
|
170
|
+
|
|
171
|
+
Display: **Select an Option:** [R] Refresh [C] Continue
|
|
172
|
+
|
|
173
|
+
#### EXECUTION RULES:
|
|
174
|
+
|
|
175
|
+
- ALWAYS halt and wait for user input after presenting menu
|
|
176
|
+
- ONLY proceed to next step when user selects 'C'
|
|
177
|
+
- After other menu items execution, return to this menu
|
|
178
|
+
|
|
179
|
+
#### Menu Handling Logic:
|
|
180
|
+
|
|
181
|
+
- IF R: Re-scan directories for epic files and return to step 2
|
|
182
|
+
- IF C: Update frontmatter, then load, read entire file, then execute `{nextStepFile}`
|
|
183
|
+
- IF Any other: Respond and redisplay menu
|
|
184
|
+
|
|
185
|
+
## CRITICAL STEP COMPLETION NOTE
|
|
186
|
+
|
|
187
|
+
ONLY WHEN C is selected and epic selection is saved to frontmatter, will you then load, read entire file, then execute `{nextStepFile}` to begin artifact analysis.
|
|
188
|
+
|
|
189
|
+
---
|
|
190
|
+
|
|
191
|
+
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
192
|
+
|
|
193
|
+
### ✅ SUCCESS:
|
|
194
|
+
|
|
195
|
+
- All epic locations scanned
|
|
196
|
+
- Epics discovered and listed with titles
|
|
197
|
+
- User provided clear selection (all/specific/exclude)
|
|
198
|
+
- Selection parsed and validated
|
|
199
|
+
- Frontmatter updated with epics_selected and epics_excluded
|
|
200
|
+
- frontmatter.stepsCompleted = [1, 2]
|
|
201
|
+
- Confirmation message displayed
|
|
202
|
+
- Ready to proceed to step 3
|
|
203
|
+
|
|
204
|
+
### ❌ SYSTEM FAILURE:
|
|
205
|
+
|
|
206
|
+
- Not scanning all locations
|
|
207
|
+
- Making assumptions about which epics to include
|
|
208
|
+
- Not validating user input
|
|
209
|
+
- Proceeding without user confirmation
|
|
210
|
+
- Not updating frontmatter correctly
|
|
211
|
+
|
|
212
|
+
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|