mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
custom inst imporove
This commit is contained in:
31
example-custom-module/mwm/workflows/crisis-support/README.md
Normal file
31
example-custom-module/mwm/workflows/crisis-support/README.md
Normal file
@@ -0,0 +1,31 @@
|
||||
# Crisis Support Workflow
|
||||
|
||||
## Purpose
|
||||
|
||||
Immediate response protocol for users in distress, providing resources and appropriate escalation.
|
||||
|
||||
## Trigger
|
||||
|
||||
Crisis trigger from any agent (emergency response)
|
||||
|
||||
## Key Steps
|
||||
|
||||
1. Crisis level assessment
|
||||
2. Immediate de-escalation techniques
|
||||
3. Safety planning
|
||||
4. Provide crisis resources
|
||||
5. Encourage professional help
|
||||
6. Follow-up check scheduling
|
||||
7. Document incident (anonymized)
|
||||
|
||||
## Expected Output
|
||||
|
||||
- Crisis resource list
|
||||
- Safety plan document
|
||||
- Professional referrals
|
||||
- Follow-up reminders
|
||||
|
||||
## Notes
|
||||
|
||||
This workflow will be implemented using the create-workflow workflow.
|
||||
IMPORTANT: NOT a substitute for professional crisis intervention. Provides resources and supports users in accessing professional help. Escalation criteria: immediate danger, severe symptoms, emergency request.
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
name: crisis-support
|
||||
description: TODO
|
||||
web_bundle: false
|
||||
---
|
||||
|
||||
# crisis-support
|
||||
|
||||
**Goal:** TODO
|
||||
|
||||
**Your Role:** TODO
|
||||
|
||||
## WORKFLOW ARCHITECTURE
|
||||
|
||||
### Core Principles
|
||||
|
||||
TODO
|
||||
|
||||
### Step Processing Rules
|
||||
|
||||
1. **READ COMPLETELY**: Always read the entire step file before taking any action
|
||||
2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
|
||||
3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
|
||||
4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
|
||||
5. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
|
||||
|
||||
### Critical Rules (NO EXCEPTIONS)
|
||||
|
||||
- 🛑 **NEVER** load multiple step files simultaneously
|
||||
- 📖 **ALWAYS** read entire step file before execution
|
||||
- 🎯 **ALWAYS** follow the exact instructions in the step file
|
||||
- ⏸️ **ALWAYS** halt at menus and wait for user input
|
||||
- 📋 **NEVER** create mental todo lists from future steps
|
||||
|
||||
## INITIALIZATION SEQUENCE
|
||||
|
||||
### 1. Module Configuration Loading
|
||||
|
||||
Load and read full config from {project-root}/.bmad/mwm/config.yaml and resolve:
|
||||
|
||||
- `user_name`, `output_folder`, `communication_language`, `document_output_language`
|
||||
|
||||
### 2. First Step EXECUTION
|
||||
|
||||
TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY.
|
||||
Reference in New Issue
Block a user