菜单
Bullet Journal management: daily/weekly/monthly logs, task migration, reviews. Use when user says daily log, bujo, weekly review, monthly log, journal, migrate tasks, what's on my plate. Not for task sync with external tools (use bujo-sync).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execution trace capture and token baselining. Use when user says trace, extract trace, count tokens, token baseline, or /harness-trace. Not for harness optimization (use harness-mechanic).
Release prep and tagging with pre-flight verification. Use when user says release, tag, ship it, push to production, create release, or bump version. Not for editing a version string outside a release, a lockfile or a changelog entry by hand, and not for reading what changed in a past release: those are ordinary edits, just do them.
Mine LEARNING.md retrospectives across all repos for recurring failure-modes, then propose harness changes (hooks, rules, skills, checklist items) with falsifiable change-contracts. Also runs the doc-gardening pass over the governance docs (stale rules, dead cross-references, skill-table drift). Use when user says learning loop, mine learnings, recurring failures, what should I fix in my process, cross-repo retrospective, doc gardening, stale docs, or run learning-loop. Runs on human schedule, never autonomously. Not for single-project retrospectives (use learning-docs) or trace/token analysis (use harness-mechanic).
Full contractor-mode loop: sub-protocols (LOCALIZE, BENCH-BASELINE, REPRODUCE, DRIFT), review routing by file pattern, blast radius, UAT, parallelism and effort caps, escalation, just-do-it, goal-backed runs. Load it to RUN that loop, once you have an approved plan and are entering step 1, or when a step needs its detail. It is a protocol, not a way to do the work: it never replaces the language, review or planning skill the task itself calls for, and a task small enough to just edit (SKIP_SET) needs none of it. The always-on spine lives in rules/orchestrator-protocol.md. Not for trace capture (harness-trace) or harness optimization (harness-mechanic).
Ruby on Rails with service-oriented architecture, Dry-validation, Sidekiq/Solid Queue, Hotwire. Use for Rails API, Rails services, Rails forms, RSpec, ActiveRecord, Rails migrations. Not for standalone Ruby gems (use ruby skill), and not for judging whether a migration is safe to run in production (that is the database-reviewer agent).
Get three independent second opinions (isolated Claude + isolated Gemini + isolated DeepSeek) on a problem Claude is analyzing. Use when user says second opinion, another perspective, challenge this approach, or asks gemini/deepseek about a decision, approach, or diagnosis. Also invoke on your own initiative, without being asked: on a complex task before planning, after 2 failed root-cause attempts, on a 🔴 decision (rewrite, core logic, security), or when the review loop is stuck below 80 after 2 fix rounds. Gathers context, writes a focused prompt, calls all reviewers in isolated Docker containers, and synthesizes all viewpoints. Not for reviewing code or changes, even phrased as 'ask gemini to review' (use gemini-review).
| name | bujo |
| description | Bullet Journal management: daily/weekly/monthly logs, task migration, reviews. Use when user says daily log, bujo, weekly review, monthly log, journal, migrate tasks, what's on my plate. Not for task sync with external tools (use bujo-sync). |
| compatibility | Requires Obsidian CLI (obsidian MCP commands). |
Vault path: Journal/ in Obsidian vault
Templates: Journal/Templates/ (Daily Note, Weekly Review, Monthly Log)
Obsidian skill: See ../obsidian/SKILL.md for vault CLI commands
bujo dailyCreate today's daily note from template (if it doesn't exist). Show summary of today's tasks.
# Check if today's note exists
obsidian read file="Journal/Daily/$(date +%Y-%m-%d)"
# If not found, create from template
obsidian template:create template="Journal/Templates/Daily Note" name="Journal/Daily/$(date +%Y-%m-%d)"
# Show summary
obsidian read file="Journal/Daily/$(date +%Y-%m-%d)"
If the daily note already exists, just read and summarize it. Highlight:
bujo weeklyCreate weekly review for current week. Scan all daily notes from the week.
date +%Y-W%V[x] completed tasks per project[>] migrated tasks[-] cancelled tasks[ ] tasks (carried forward)Journal/Weekly/YYYY-Www.md from template# Read daily notes for the week
for day in $(python3 -c "
from datetime import date, timedelta
import sys
today = date.today()
start = today - timedelta(days=today.weekday())
for i in range(7):
d = start + timedelta(days=i)
if d <= today:
print(d.isoformat())
"); do
obsidian read file="Journal/Daily/$day" 2>/dev/null
done
bujo monthlyCreate monthly log for current month. Summarize week by week.
date +%Y-%mJournal/Monthly/YYYY-MM.md from template (if not exists)bujo migrateScan yesterday's daily note for open tasks. For each one, ask what to do.
- [ ] items[CU-xxx] or [LIN-xxx]): mark as [>] in yesterday's note. It will reappear via bujo sync.[>] in yesterday's[-] in yesterday'sJournal/Future Log.md, mark [>] in yesterday's[x] (did it but forgot to check off)[>] or [-] markersMigration format:
# Yesterday's note:
- [>] Task that was migrated [CU-abc]
- [-] Task that was cancelled
- [x] Task completed
# Today's note (Personal section):
- [ ] Migrated personal task
bujo reviewShow today's daily note with highlights on overdue/blocked items.
**BLOCKS**: these are blocking others| Symbol | Meaning |
|---|---|
- [ ] | Open task |
- [x] | Completed task |
- [>] | Migrated (moved forward) |
- [-] | Cancelled |
- [!] | Event |
- [i] | Note/info |
| Type | Pattern | Example |
|---|---|---|
| Daily | Journal/Daily/YYYY-MM-DD.md | Journal/Daily/2026-02-22.md |
| Weekly | Journal/Weekly/YYYY-Www.md | Journal/Weekly/2026-W08.md |
| Monthly | Journal/Monthly/YYYY-MM.md | Journal/Monthly/2026-02.md |
| Future Log | Journal/Future Log.md | |
| Collections | Journal/Collections/*.md |
Task sync is handled by the bujo-sync skill. This skill only manages note creation, migration, and review.
Sync markers in daily notes (HTML comments) delimit zones where bujo-sync writes. This skill NEVER modifies content between sync markers.
<!-- bujo-sync:clickup:start -->
(bujo-sync writes here)
<!-- bujo-sync:clickup:end -->