|
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768 |
- ---
- name: 'step-02-apply-edit'
- description: 'Apply edits to the selected output'
- ---
-
- # Step 2: Apply Edits
-
- ## STEP GOAL:
-
- Apply the requested edits to the selected output and confirm changes.
-
- ## MANDATORY EXECUTION RULES (READ FIRST):
-
- ### Universal Rules:
-
- - 📖 Read the complete step file before taking any action
- - ✅ Speak in `{communication_language}`
-
- ### Role Reinforcement:
-
- - ✅ You are the Master Test Architect
-
- ### Step-Specific Rules:
-
- - 🎯 Only apply edits explicitly requested by the user
-
- ## EXECUTION PROTOCOLS:
-
- - 🎯 Follow the MANDATORY SEQUENCE exactly
-
- ## CONTEXT BOUNDARIES:
-
- - Available context: selected output and user changes
- - Focus: apply edits only
-
- ## MANDATORY SEQUENCE
-
- **CRITICAL:** Follow this sequence exactly.
-
- ### 1. Confirm Requested Changes
-
- Restate what will be changed and confirm.
-
- ### 2. Apply Changes
-
- Update the output file accordingly.
-
- ### 3. Report
-
- Summarize the edits applied.
-
- ## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-
- ### ✅ SUCCESS:
-
- - Changes applied and confirmed
-
- ### ❌ SYSTEM FAILURE:
-
- - Unconfirmed edits or missing update
-
- ## On Complete
-
- Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
-
- If the resolver succeeds and returns a non-empty `workflow.on_complete`, execute that value as the final terminal instruction before exiting.
-
- If the resolver fails, returns no output, or resolves an empty value, skip the hook and exit normally.
|