@cloudkinetix/bmad-enhanced/expansion-packs/ck-jira-integration/tasks/check-feedback-reminder.md

Cloud-Kinetix enhanced fork of BMAD-METHOD - Breakthrough Method of Agile AI-driven Development with robust versioning and unified validation.

# Check Feedback Reminder

## Purpose

Check if it's appropriate to show a feedback reminder and display it at natural moments.

## Context

Shows feedback reminders only at appropriate times to avoid interrupting work.

## Input Required

- Current context (what user just completed)
- Session event count

## Steps

1. **Check reminder state**

   ```bash
   # Check if reminder state file exists
   if [ -f .bmad-workspace/ck-jira-integration/feedback/.reminder-state.yml ]; then
       cat .bmad-workspace/ck-jira-integration/feedback/.reminder-state.yml
   fi
   ```

2. **Evaluate reminder conditions**
   Show reminder only if ALL conditions are met:
   - At least 20 events logged in current session
   - Last reminder was >30 days ago (or never shown)
   - User just completed a successful operation
   - Not during setup, errors, or urgent work

3. **Natural moments for reminders**
   - After successful sprint report generation
   - When user says "thanks" or "done"
   - After successful bulk sync
   - During help command (if appropriate)

4. **Show contextual reminder** (if conditions met)

   For new users:

   ```
   💡 Quick tip: Your anonymous usage patterns help improve this tool for everyone.
   No personal data is collected - just patterns like "bulk sync is popular" or
   "setup takes 5-10 minutes on average."
   ```

   For experienced users:

   ```
   🎯 You've been productive with JIRA sync! Your usage patterns (anonymous) help
   identify which features to improve. For example, we've noticed bulk sync saves
   teams an average of 2 hours per sprint.
   ```

5. **Update reminder state**
   ```yaml
   # .bmad-workspace/ck-jira-integration/feedback/.reminder-state.yml
   last_shown: { { current_date } }
   total_shown: { { count + 1 } }
   user_level: { { new|regular|power } }
   ```

## Implementation Notes

- Never force or nag
- Keep messages brief and positive
- Focus on value to community
- Make privacy prominent
- Don't show during errors/struggles

## DO NOT Show When

- User is struggling or confused
- During error messages
- In the middle of active work
- More than once per month
- If user previously opted out