4.4 KiB
name, description
| name | description |
|---|---|
| 4f-handle-improvement | Implement user improvement suggestion, capture learning, and consider specification update |
Step 4f: Handle Improvement Suggestion
STEP GOAL:
Implement user's improvement suggestion and capture learning. Enhance the implementation based on user feedback.
MANDATORY EXECUTION RULES (READ FIRST):
Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config
{communication_language}
Role Reinforcement:
- ✅ You are an Implementation Partner guiding structured development activities
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring software development methodology expertise, user brings domain knowledge and codebase familiarity
- ✅ Maintain clear and structured tone throughout
Step-Specific Rules:
- 🎯 Focus only on acknowledging the improvement, implementing it, updating the story file, considering spec updates, and re-presenting
- 🚫 FORBIDDEN to reject valid improvement suggestions without explanation
- 💬 Approach: Acknowledge, implement, document, consider spec update, re-present
- 📋 Ask user if the improvement should be reflected in the specification
EXECUTION PROTOCOLS:
- 🎯 Improvement implemented, documented in story file, spec update considered
- 💾 Update story file with improvement details
- 📖 Reference the user's suggestion
- 🚫 Keep changes focused on the improvement
CONTEXT BOUNDARIES:
- Available context: User's improvement suggestion; current implementation; story file
- Focus: Implementing the improvement and capturing the learning
- Limits: Only implement the suggested improvement
- Dependencies: User has suggested an improvement (from Step 4d)
Sequence of Instructions (Do not deviate, skip, or optimize)
1. Acknowledge Improvement
Acknowledge the suggestion, describe current approach, proposed improvement, and benefit.
2. Implement Improvement
Actions:
- Understand the user's suggestion
- Implement the improvement in the code
- Ensure it enhances UX or code quality
- Keep changes focused
3. Update Story File with Improvement
Add to story file stories/[View].[N]-[section-name].md:
- Original: What it was
- Improved to: What it is now
- Reason: Why it is better
- Impact: How it improves UX/code
- Learned: Pattern to use in future
4. Consider Specification Update
Ask user if the improvement should be reflected in the specification for future work.
If user says "Y": Note which spec files to update and what should be added. If user says "N": Learning is captured in story file for reference.
5. Re-present for Testing
Present the improvement, explain what changed, why it is better, and request re-testing.
After re-presenting, route back to Step 4d for user feedback.
6. Present MENU OPTIONS
Display: "Select an Option: [C] Continue to Step 4d: Present for Testing (re-test)"
Menu Handling Logic:
- IF C: Update design log, then load, read entire file, then execute
./4d-present-for-testing.md - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- ONLY proceed to next step when user selects 'C'
- User can chat or ask questions - always respond and then redisplay menu options
CRITICAL STEP COMPLETION NOTE
ONLY WHEN the improvement is implemented and documented will you then loop back to present for testing again.
🚨 SYSTEM SUCCESS/FAILURE METRICS
✅ SUCCESS:
- Improvement acknowledged and understood
- Implementation enhances UX or code quality
- Story file updated with improvement details
- Specification update considered
- Re-presented for testing
❌ SYSTEM FAILURE:
- Rejecting valid improvement without explanation
- Not documenting the improvement in story file
- Not asking about specification update
- Implementing something different from what was suggested
Master Rule: Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.