# Log Learning Event

## Purpose

Log anonymous usage patterns to help improve the JIRA expansion pack.

## Context

This task creates actual log entries in the feedback directory, making the learning system work with LLM-native file operations.

## Input Required

- Event type (e.g., setup_start, command_confusion, sync_success)
- Event details (anonymized metrics and patterns)
- Session ID (generated at startup)

## Steps

1. **Ensure feedback directory exists**

   ```bash
   mkdir -p .bmad-workspace/ck-jira-integration/feedback
   ```

2. **Create or append to today's learning log**
   - File: `.bmad-workspace/ck-jira-integration/feedback/learning-log-{{DATE}}.md`
   - Format:

   ```markdown
   ## Session: {{session_id}}

   ### Event: {{event_type}}

   - Time: {{relative_time}} (morning/afternoon/evening)
   - Details: {{anonymized_details}}
   - Pattern: {{observed_pattern}}

   ---
   ```

3. **Update aggregated learnings file**
   - File: `.bmad-workspace/ck-jira-integration/feedback/jira-expansion-learnings.md`
   - Only update at natural breaks (not during active operations)
   - Include summary statistics and patterns

## Privacy Rules

- NO project keys, URLs, or ticket IDs
- NO personal or company information
- Round timestamps to relative periods
- Generalize error messages
- Focus on patterns, not specifics

## Example Usage

### Setup Event

```
Event: setup_start
Details:
- Phase: project_detection
- Method: auto_detect
- Time: morning
```

### Command Confusion

```
Event: command_confusion
Details:
- Commands tried: 3 variations
- Help requested: yes
- Resolution: found correct command
- Time spent: 5-10min
```

### Success Pattern

```
Event: sync_success
Details:
- Type: bulk_sync
- Items: 5-10
- First try: yes
- Time: <2min
```

## Implementation Notes

- Use Write tool to create/append files
- Always fail silently if file operations fail
- Never block user operations for logging
- Log immediately for important events
- Batch less critical events