**Version:** 1.0.0
/plugin marketplace add nguyenthienthanh/aura-frog/plugin install aura-frog@aurafrogworkflow/Version: 1.0.0
Purpose: Request modifications to current phase without full reject/restart
Trigger: User types /workflow:modify <instructions> at approval gate
Faster than reject - only changes specific things, doesn't restart entire phase.
/workflow:modify <instructions>
Examples:
/workflow:modify Add accessibility labels to all buttons
/workflow:modify Change coverage threshold from 85% to 90%
/workflow:modify Extract validation logic into separate utility function
/workflow:modify Update component names to be more descriptive
/workflow:reject when:/workflow:modify when:User types /workflow:modify <instructions>
ā
Agent does LIGHT brainstorming:
- Quick consideration of alternatives
- Ask if related changes needed
ā
Apply changes to deliverables
ā
Show updated approval gate
User types /workflow:modify just do: <instructions>
ā
Skip brainstorming
ā
Apply changes directly
ā
Show updated approval gate
Force phrases: "just do:", "must do:", "exactly:", "no discussion"
See: rules/feedback-brainstorming.md
User: /workflow:modify Add test cases for network timeout scenarios
Agent Response:
š¤ Adding timeout tests. Quick thought:
Should I also add tests for:
- Retry logic after timeout?
- User-facing timeout message?
- Timeout threshold configuration?
Or just basic timeout handling?
(Say "all" or "just basic" or list what you want)
User: /workflow:modify just do: Add test cases for network timeout
Agent Response:
āļø Applying modifications...
Changes:
- Added 3 test cases to PostCaptionEditor.test.tsx
- TC-021: Should handle network timeout
- TC-022: Should retry on timeout
- TC-023: Should show timeout error message
Updated test count: 73 ā 76 tests
[Approval gate with updated info...]
User: /workflow:modify Rename PostCaptionEditor to CaptionEditor
Agent Response:
š¤ Renaming to CaptionEditor. Quick check:
I noticed similar components:
- PostMediaEditor ā Should this be MediaEditor too?
- PostHashtagEditor ā HashtagEditor?
Want me to rename all for consistency, or just this one?
User: /workflow:modify Increase coverage threshold to 90%
Agent Response:
āļø Applying modifications...
Changes:
- Updated coverage threshold: 85% ā 90%
- Updated jest.config.js
- Updated test plan document
- Recalculated required test cases
Impact:
- Need 12 more test cases to reach 90%
- Current: 73 tests (85% coverage)
- Target: 85 tests (90% coverage)
Would you like me to:
a) Generate additional test cases now
b) Update plan only (add tests in Phase 5a)
Your choice: [Enter a or b]
User: /workflow:modify Extract validation logic from handleSaveCaption into validateCaption utility
Agent Response:
āļø Applying modifications...
Changes:
- Created utils/validateCaption.ts
- Extracted validation logic (15 lines)
- Updated handleSaveCaption to use utility
- Added tests for validateCaption
Files:
- Created: utils/validateCaption.ts
- Created: utils/validateCaption.test.ts
- Modified: useSocialMarketingLogic.ts
Code quality:
- Complexity reduced: 12 ā 8
- Reusability improved ā
[Shows updated approval gate...]
{
"phases": {
"4": {
"name": "Test Planning",
"status": "completed",
"modifications": [
{
"timestamp": "2025-11-24T15:45:00Z",
"instruction": "Add test cases for network timeout scenarios",
"changes": [
"Added 3 test cases",
"Updated test plan document"
],
"files_affected": 2
}
]
}
}
}
Some modifications are so common, they have shortcuts:
/workflow:modify +tests ā Add more test cases
/workflow:modify +coverage ā Increase coverage threshold
/workflow:modify +docs ā Add more documentation
/workflow:modify +types ā Improve TypeScript types
/workflow:modify +a11y ā Add accessibility improvements
ā
Good: /workflow:modify Add JSDoc comments to all public functions
ā Vague: /workflow:modify Add comments
ā
Good: /workflow:modify Rename PostCaptionEditor to CaptionEditor
ā
Then: /workflow:modify Add accessibility labels
ā Bad: /workflow:modify Rename component and add accessibility and fix types
After modification, agent shows:
- What changed
- Files affected
- Impact on tests/coverage
- Any new issues introduced
After modification:
Skip brainstorming: Use "just do:", "exactly:", or "no discussion"
You can modify multiple times before approving:
User: /workflow:modify Add accessibility labels
Agent: [Makes changes] ā Approval gate
User: /workflow:modify Also add loading skeletons
Agent: [Makes changes] ā Approval gate
User: /workflow:modify Increase button touch targets to 44pt
Agent: [Makes changes] ā Approval gate
User: /workflow:approve ā Proceeds to next phase
Status: Active command
Related: workflow:approve, workflow:reject, workflow:status