journal-capture

# Journal Capture Skill

You have the ability to proactively capture significant work into the user's journal.

## When to Use This Skill

Use this skill **automatically and proactively** when you:

1. **Complete a significant feature or task**
   - Implemented new functionality
   - Fixed a complex bug
   - Refactored important code
   - Set up infrastructure or tooling

2. **Make important technical decisions**
   - Chose between architectural approaches
   - Selected libraries or frameworks
   - Decided on implementation strategies
   - Resolved design tradeoffs

3. **Solve challenging problems**
   - Debugged difficult issues
   - Overcame technical obstacles
   - Found non-obvious solutions
   - Learned something valuable

4. **Make progress on projects**
   - Completed a phase of work
   - Reached a milestone
   - Integrated multiple components
   - Finished testing or deployment

## How to Capture

Use the `journal_auto_capture` MCP tool:

```
journal_auto_capture(
  title="Brief title of what was accomplished",
  description="The goal (what we were trying to do) and what was done"
)
```

The tool automatically:
- Determines the project (if in a git repo)
- Adds the "auto-capture" tag
- Generates relevant tags based on content
- Creates a structured journal entry

## Examples

**Example 1: Feature implementation**
```
User: "Add authentication to the API"
[You implement OAuth2 with JWT tokens]
→ journal_auto_capture(
    title="Implemented OAuth2 authentication",
    description="User requested API authentication. Implemented OAuth2 flow with JWT tokens for secure user sessions."
  )
```

**Example 2: Bug fix**
```
User: "The cache is leaking memory"
[You identify and fix the leak]
→ journal_auto_capture(
    title="Fixed cache memory leak",
    description="User reported memory leak in cache. Identified and fixed by implementing automatic clearing of stale entries."
  )
```

**Example 3: Technical decision**
```
User: "Should we use Redis or PostgreSQL for c