---
description: Append an entry to the current ticket's journal; overwrite Current state
argument-hint: "<entry text>"
---

The user wants to append a journal entry. Text: **$ARGUMENTS**

Follow the @cleepi/sdd workflow (load `/skill:sdd` if you haven't,
specifically the "Journal discipline" and "Voice and length" sections).

1. **Resolve the current ticket folder.**
   - If `cwd` is inside `docs/<ticket-id>-slug/` or
     `packages/<n>/docs/<ticket-id>-slug/`, use that folder.
   - Otherwise ask: *"Which ticket is this entry for? Provide the
     folder path or ticket ID."*

2. **Find or create `<folder>/journal.md`.**
   - If it exists, read it.
   - If not, scaffold from the @cleepi/sdd `templates/journal.md`
     template (substitute the ticket ID and slug into the header).

3. **Append the log entry.**
   - Find the `## Log` section.
   - Insert a new dated entry at the **top** of the log
     (newest first):
     ```
     ### YYYY-MM-DD — <author or session label>
     - <entry text, broken into 1–5 bullets if multi-line>
     ```
   - Date = today.
   - Author = the session user; ask if unclear.

4. **Update Current state.**
   - Ask the user: *"What's the current state in one line, after
     this entry?"*
   - Replace the bullets under `## Current state` with the
     response. Don't append — overwrite.

5. **Write the file. Report what changed** (one line: path +
   what was appended + what Current state now says).

6. **Discipline check.** If the entry text has no dead end,
   blocker, surprise, or reasoning behind it, gently flag:
   *"This looks like a changelog entry rather than journal
   material — should I run `/changelog` instead?"* Don't refuse;
   just ask.

Be concise (see skill "Voice and length"). The journal entry
itself goes in as the user wrote it — apply the delete test
only to your own surrounding output, not the user's content.