القائمة
Read recent journal entries. Use when resuming work, checking what was done recently, or reviewing a specific session's history.
التثبيت باستخدام 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 | read |
| description | Read recent journal entries. Use when resuming work, checking what was done recently, or reviewing a specific session's history. |
Read and display journal entries. Supports filtering by time range, type, branch, outcome, origin, or keyword.
No confirmation needed — runs immediately and displays results.
Reads from .claude/journal.jsonl in the project root. If the file doesn't exist, report that no journal exists and suggest running field-notes:write.
Show the last N entries (default: 5):
/field-notes:read
/field-notes:read 10
Filter to a specific entry type:
/field-notes:read bug-fix
/field-notes:read refactor
Filter to entries from a time range:
/field-notes:read today
/field-notes:read week
/field-notes:read 2026-03-27
Filter to entries from a specific branch:
/field-notes:read branch feature/notifications
Filter to entries with a specific outcome:
/field-notes:read blocked
/field-notes:read partial
Show only primary sessions or delegated work:
/field-notes:read delegated
/field-notes:read primary
Search across all text fields (summary, workedOn, issues, insights, feedback):
/field-notes:read search SSE
/field-notes:read search "rate limiter"
Present entries in reverse chronological order (newest first):
## Journal — last 5 entries
◆ 2026-03-27 14:30 | work | completed | primary
Branch: feature/notifications | Skill: zenflow:dispatch
Worked on: plan: resources/plans/245-realtime-notifications.md
Added real-time SSE notifications for issue state changes
Files: 5 modified, 2 created | Tests: +8
Insight: Two-stage review caught a missing reconnection handler
Feedback: Worktree delegation kept context clean during side fix
◆ 2026-03-27 10:15 | bug-fix | completed | delegated
Branch: fix/rate-limiter | Skill: zenflow:bug-fix
Worked on: issue: rate limiter counter not resetting
Fixed rate limiter counter not resetting between windows
Files: 1 modified | Tests: +1
◆ 2026-03-26 16:00 | exploration | partial | primary
Branch: feature/mastra | Skill: zenflow:collab
Worked on: Mastra workflow integration patterns
Explored Mastra workflow integration patterns
Insight: Mastra's step() API changed in 0.5 — docs are outdated
Would do differently: Check installed version before reading remote docs
Feedback: Remote docs should be version-pinned in bookmarks
◆ 2026-03-26 11:00 | work | blocked | delegated
Branch: fix/sse-backoff | Skill: zenflow:plan
Worked on: plan: resources/plans/244-sse-backoff.md
Attempted SSE backoff implementation, blocked by unclear retry semantics
Blocker: No spec for max retry count — needs product decision
(4 entries shown, 23 total)
origin badge (primary or delegated) — makes it clear who did the workoutcome — completed entries are normal, highlight blocked and partialworkedOn always shown — it's the anchor for what this entry is aboutfeedback shown when present — it's the meta-level learning.claude/journal.jsonl