feat: security overhaul (proxy ssrf fix, streaming sanitization, docker optimization)

This commit is contained in:
Michael committed 2026-01-07 08:43:33 +01:00
1 parent 6d87ada2b8
commit 8df9a37baa
810 files changed
+131090 -151

No files matched your search

@@ -0,0 +1,154 @@
---
name: 'step-01b-continue'
description: 'Continue an existing architecture workflow from where it left off'
# Path Definitions
workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
# File References
thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
workflowFile: '{workflow_path}/workflow.md'
outputFile: '{output_folder}/game-architecture.md'
# Step Files (for routing)
step02: '{workflow_path}/steps/step-02-context.md'
step03: '{workflow_path}/steps/step-03-starter.md'
step04: '{workflow_path}/steps/step-04-decisions.md'
step05: '{workflow_path}/steps/step-05-crosscutting.md'
step06: '{workflow_path}/steps/step-06-structure.md'
step07: '{workflow_path}/steps/step-07-patterns.md'
step08: '{workflow_path}/steps/step-08-validation.md'
step09: '{workflow_path}/steps/step-09-complete.md'
---
# Step 1b: Continue Existing Architecture
**Resuming Architecture Workflow**
## STEP GOAL:
Load the existing architecture document, determine progress, and route to the appropriate next step.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- YOU ARE A FACILITATOR, not a content generator
- NEVER mention time estimates
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
### Step-Specific Rules:
- Parse frontmatter to determine completed steps
- Present summary of current progress
- Route to correct next step based on state
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Load Existing Architecture
**Read the existing architecture document:**
Load `{outputFile}` and parse the frontmatter to extract:
- `stepsCompleted` array
- `status`
- `project` name
- Source document references
### 2. Analyze Progress
**Determine workflow state:**
Map completed steps to workflow progress:
- Step 1: Initialize
- Step 2: Context
- Step 3: Starter/Engine
- Step 4: Decisions
- Step 5: Cross-cutting
- Step 6: Structure
- Step 7: Patterns
- Step 8: Validation
- Step 9: Complete
**Calculate next step:**
Find the highest completed step and determine the next step file to load.
### 3. Present Continuation Summary
"**Resuming Architecture Workflow**
{{user_name}}, I found your existing architecture for **{{project_name}}**.
**Progress:** Steps completed: {{stepsCompleted}}
**Current Status:**
- Last completed: {{last_step_name}}
- Next step: {{next_step_name}} (Step {{next_step_number}} of 9)
**Document sections completed:**
{{list_of_completed_sections}}
Would you like to:
1. **Continue** - Resume from {{next_step_name}}
2. **Review** - Show me what we've documented so far
3. **Restart Step** - Redo the last completed step
Select an option:"
### 4. Handle User Selection
**If Continue:**
- Load the next step file based on `stepsCompleted`
**If Review:**
- Present summary of all completed sections
- Return to continuation options
**If Restart Step:**
- Decrement stepsCompleted to remove last step
- Load the step file for the step being restarted
### 5. Route to Next Step
Based on next step number, load the appropriate step file:
| Next Step | File |
| --------- | -------- |
| 2 | {step02} |
| 3 | {step03} |
| 4 | {step04} |
| 5 | {step05} |
| 6 | {step06} |
| 7 | {step07} |
| 8 | {step08} |
| 9 | {step09} |
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Existing document loaded and parsed
- Progress accurately determined
- User presented with clear options
- Correct step file loaded based on state
### SYSTEM FAILURE:
- Failing to parse frontmatter correctly
- Loading wrong step file
- Not presenting continuation options
- Overwriting existing progress without confirmation
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.