菜单
Append a structured journal entry after completing work. Use at the end of any task, feature, bug fix, or session to record what was done, what went wrong, and what was learned.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Discover files with trigger_phrase and/or refresh frontmatter, let the user choose which to schedule for periodic re-injection via CronCreate. Prevents behavioral drift by keeping core rules and goals fresh in context.
Write trigger phrases from .claude/triggers.json into file frontmatter as model-scoped trigger_phrase fields. Bridges trigger generation (scan) with scheduled injection (zenflow:schedule).
Build a GitHub issue into a PR. User-launched with an issue number — reads the issue, confirms with user, creates branch, implements against acceptance criteria, runs verification, and opens a PR. Every decision surfaces via AskUserQuestion.
Collaborative working session — you and the user are a team exploring, researching, and planning together. When implementation work is needed, create well-structured GitHub issues. The user launches Builder agents to implement and Reviewer agents to verify.
Shed accumulated context mid-session. Writes a knowledge handoff document capturing session state, decisions, observations, and behavioral calibration, then guides the user through /clear and resumption.
Runtime verification using Playwright MCP + proof artifacts. Use when acceptance criteria mention UI behavior, when claiming runtime verification, or when independently verifying a PR's claims. Produces artifact-backed proof — screenshots, DOM snapshots — not prose claims.
| name | write |
| description | Append a structured journal entry after completing work. Use at the end of any task, feature, bug fix, or session to record what was done, what went wrong, and what was learned. |
| allowed-tools | Read, Bash |
Append a structured entry to the project's agent journal. One JSONL file per project, one line per entry. Every entry captures what happened, not just what was built.
Announce at start: "Writing a journal entry."
The journal lives at .claude/journal.jsonl in the project root. Create it if it doesn't exist.
Why .claude/: Keeps agent artifacts together. The file is gitignored or committed per team preference — both work. JSONL is append-only, so merge conflicts are rare even when committed.
Each entry is a single JSON line:
{
"timestamp": "2026-03-27T14:30:00.000Z",
"workedOn": "plan: resources/plans/245-notifications.md | issue: #123 | description of work",
"branch": "current git branch name",
"type": "work | bug-fix | refactor | audit | exploration | review | reflection | context-refresh",
"origin": "primary | delegated",
"skill": "zenflow:dispatch",
"outcome": "completed | partial | blocked | abandoned",
"summary": "One sentence: what was accomplished",
"details": {
"filesModified": ["path/to/file1.ts", "path/to/file2.ts"],
"filesCreated": ["path/to/new-file.ts"],
"testsAdded": 3,
"testsModified": 1
},
"issues": "Problems encountered (empty string if none)",
"blockers": "What stopped progress (empty string if none)",
"workarounds": "Temporary solutions used (empty string if none)",
"insights": "What worked well, surprising discoveries, useful patterns",
"wouldDoDifferently": "Hindsight improvements for next time",
"feedback": "Observations about the workflow, tools, or process that could improve future sessions",
"duration": "approximate time spent (e.g., '45 min', '2 hours')"
}
| Field | Type | Description |
|---|---|---|
timestamp | string | ISO 8601 timestamp |
workedOn | string | What this entry is about — a plan file path, issue number, or freeform description |
type | string | Entry type: work, bug-fix, refactor, audit, exploration, review, reflection |
summary | string | One sentence describing what was accomplished |
| Field | Type | Description |
|---|---|---|
branch | string | Git branch name |
origin | string | primary (user's session) or delegated (spawned by another agent) |
skill | string | Which zen skill was active (e.g., zenflow:dispatch, zenflow:collab) |
outcome | string | completed, partial, blocked, or abandoned |
feedback | string | Observations about the workflow, tools, or process — meta-level improvements |
All other fields are optional. Include what's relevant — a quick exploration doesn't need filesModified, a bug fix doesn't need duration. The schema is flexible; the only hard rule is one JSON object per line.
Projects can add custom fields. The schema is open — any valid JSON key-value pair is accepted. This lets teams track project-specific data (e.g., issueId, prNumber, deployTarget) without modifying the plugin.
Gather context — review what changed in this session:
git diff --stat for files modifiedTaskList for tasks completedWrite the entry — construct the JSON object with relevant fields
Append to journal — write a single line to .claude/journal.jsonl:
echo '{...}' >> .claude/journal.jsonl
Confirm — announce: "Journal entry written for: {summary}"
Don't write entries for trivial work — if it took 2 minutes and changed 1 line, it doesn't need a journal entry.
zenflow:check-work Gate 5 should invoke this skill instead of writing its own journal entry:
field-notes:write with type work