initial commit
This commit is contained in:
@@ -0,0 +1,141 @@
|
||||
---
|
||||
name: 'step-e-01-assess-workflow'
|
||||
description: 'Assess what needs to be edited in the teaching workflow'
|
||||
|
||||
nextStepFile: './step-e-02-apply-edits.md'
|
||||
workflowPath: '../'
|
||||
advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
|
||||
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Edit Step 1: Assess What to Edit
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
To identify what the user wants to edit in the teach-me-testing workflow and gather requirements for the modifications.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read complete step file before action
|
||||
- ✅ SPEAK OUTPUT In {communication_language}
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a workflow architect helping with modifications
|
||||
- ✅ Collaborative dialogue for understanding edit needs
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on understanding what to edit
|
||||
- 🚫 FORBIDDEN to make edits yet
|
||||
- 💬 Ask questions to clarify requirements
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Understand edit requirements
|
||||
- 💾 Document what needs editing
|
||||
- 📖 Prepare for edits in next step
|
||||
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
### 1. Welcome to Edit Mode
|
||||
|
||||
"**Edit Mode: Teach Me Testing Workflow**
|
||||
|
||||
What would you like to edit?
|
||||
|
||||
**Common edits:**
|
||||
|
||||
- Update session content (new concepts, updated examples)
|
||||
- Modify quiz questions
|
||||
- Add/remove knowledge fragments from session 7
|
||||
- Update TEA resource references
|
||||
- Change session durations or structure
|
||||
- Update role-based examples
|
||||
|
||||
**Tell me what you'd like to change.**"
|
||||
|
||||
### 2. Gather Edit Requirements
|
||||
|
||||
Ask targeted questions based on their response:
|
||||
|
||||
**If editing session content:**
|
||||
|
||||
- Which session? (1-7)
|
||||
- What specific content needs updating?
|
||||
- Why the change? (outdated, incorrect, needs improvement)
|
||||
|
||||
**If editing quiz questions:**
|
||||
|
||||
- Which session's quiz?
|
||||
- Which question(s)?
|
||||
- What's wrong with current questions?
|
||||
|
||||
**If editing session 7 fragments:**
|
||||
|
||||
- Add new fragment category?
|
||||
- Update existing fragment references?
|
||||
- Change organization?
|
||||
|
||||
**If editing templates:**
|
||||
|
||||
- Progress template?
|
||||
- Session notes template?
|
||||
- Certificate template?
|
||||
- What fields need changing?
|
||||
|
||||
**If editing data files:**
|
||||
|
||||
- Curriculum structure?
|
||||
- Role customizations?
|
||||
- Resource mappings?
|
||||
|
||||
### 3. Load Current Content
|
||||
|
||||
Based on what they want to edit, load the relevant files:
|
||||
|
||||
- Session step files (steps-c/step-04-session-\*.md)
|
||||
- Templates (`templates/*.md` or `*.yaml`)
|
||||
- Data files (data/\*.yaml)
|
||||
|
||||
Show user the current content.
|
||||
|
||||
### 4. Document Edit Plan
|
||||
|
||||
"**Edit Plan:**
|
||||
|
||||
**Target Files:**
|
||||
|
||||
- {list files to be modified}
|
||||
|
||||
**Changes Required:**
|
||||
|
||||
- {list specific changes}
|
||||
|
||||
**Reason:**
|
||||
|
||||
- {why these edits are needed}
|
||||
|
||||
Ready to proceed with edits?"
|
||||
|
||||
### 5. Menu
|
||||
|
||||
Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Apply Edits
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF A: Execute {advancedElicitationTask}, redisplay menu
|
||||
- IF P: Execute {partyModeWorkflow}, redisplay menu
|
||||
- IF C: Load, read entire file, then execute {nextStepFile}
|
||||
- IF Any other: help user, redisplay menu
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SUCCESS METRICS
|
||||
|
||||
✅ Edit requirements clearly understood, target files identified, edit plan documented, user approves plan.
|
||||
|
||||
**Master Rule:** Understand before editing. Get clear requirements first.
|
||||
@@ -0,0 +1,122 @@
|
||||
---
|
||||
name: 'step-e-02-apply-edits'
|
||||
description: 'Apply modifications to the teaching workflow based on edit plan'
|
||||
|
||||
workflowPath: '../'
|
||||
---
|
||||
|
||||
# Edit Step 2: Apply Edits
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
To apply the approved edits to the teach-me-testing workflow files while maintaining integrity and quality standards.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
### Universal Rules:
|
||||
|
||||
- 🛑 NEVER edit without showing user the changes first
|
||||
- 📖 CRITICAL: Read complete step file before action
|
||||
- ✅ SPEAK OUTPUT In {communication_language}
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a workflow architect applying modifications
|
||||
- ✅ Collaborative edits with user approval
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on applying approved edits only
|
||||
- 🚫 FORBIDDEN to make unapproved changes
|
||||
- 💬 Show changes before applying
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Apply edits systematically
|
||||
- 💾 Validate after each edit
|
||||
- 📖 Document changes made
|
||||
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
### 1. Review Edit Plan
|
||||
|
||||
"**Applying approved edits to teach-me-testing workflow**
|
||||
|
||||
From step-e-01, we identified:
|
||||
{Summarize edit plan from previous step}
|
||||
|
||||
Let me apply these changes systematically."
|
||||
|
||||
### 2. Apply Edits by Category
|
||||
|
||||
**For each file to be edited:**
|
||||
|
||||
1. Load the current file
|
||||
2. Show the proposed changes (before/after)
|
||||
3. Ask: "Apply this edit? [Y/N]"
|
||||
4. If Y: Make the edit
|
||||
5. If N: Skip this edit
|
||||
6. Confirm edit applied successfully
|
||||
|
||||
### 3. Validate Edits
|
||||
|
||||
After all edits applied:
|
||||
|
||||
**Check:**
|
||||
|
||||
- Frontmatter still valid
|
||||
- File references still correct
|
||||
- Menu handling logic intact
|
||||
- Step sequence maintained
|
||||
|
||||
"**Validation:**
|
||||
|
||||
All edits applied successfully:
|
||||
|
||||
- {list files modified}
|
||||
|
||||
Checking integrity:
|
||||
|
||||
- ✅ Frontmatter valid
|
||||
- ✅ File references correct
|
||||
- ✅ Menu logic intact
|
||||
- ✅ Step sequence maintained"
|
||||
|
||||
### 4. Summary of Changes
|
||||
|
||||
"**Edit Summary:**
|
||||
|
||||
**Files Modified:** {count}
|
||||
{List each file with changes made}
|
||||
|
||||
**Changes Applied:**
|
||||
{Summarize what was changed}
|
||||
|
||||
**Workflow Status:** ✅ Edits complete, workflow intact
|
||||
|
||||
**Next:** You can run the workflow to test your changes, or run validation mode to check quality."
|
||||
|
||||
### 5. Completion
|
||||
|
||||
"**Edit Mode Complete!**
|
||||
|
||||
The teach-me-testing workflow has been updated.
|
||||
|
||||
**Modified files:**
|
||||
{List paths to modified files}
|
||||
|
||||
**Recommended next steps:**
|
||||
|
||||
1. Run validation: `bmad run teach-me-testing -v`
|
||||
2. Test the workflow: `bmad run teach-me-testing`
|
||||
3. Make additional edits if needed"
|
||||
|
||||
**This is the final edit step - workflow ends here.**
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SUCCESS METRICS
|
||||
|
||||
✅ Edits applied to approved files only, changes validated, workflow integrity maintained, user informed of modifications.
|
||||
|
||||
**Master Rule:** Show changes, get approval, apply edits, validate integrity.
|
||||
Reference in New Issue
Block a user