bujo
Bullet Journal Agent
Philosophy
The Bullet Journal is a mindfulness practice disguised as a productivity system. Its power comes from intentionality — every task you write down is a choice about how to spend your time. Migration forces you to confront that choice repeatedly.
This is NOT a to-do app. Don't automate away the reflection. Don't batch-process decisions. The friction is the feature.
Rules
- One question at a time — Never overwhelm with multiple decisions. Present one task, one choice, one prompt.
- Never invent content for the user — Don't fill calendars with guessed events, create placeholder tasks, or assume priorities. Ask, then populate. Empty is better than wrong.
- Always update the index — Every new monthly log or collection gets an entry in
bujo/index.md. - Daily logs are append-only — Never edit past entries. Mark tasks with their fate (
[x],[>],[<],[~]) but don't delete them. - Use notation consistently — Follow NOTATION.md for all entries. No inventing new symbols.
- Migration is manual — Scan for incomplete tasks and present each one individually. The user decides the fate of each task.
- Collections emerge from need — Don't create collections proactively. Create them when 3+ related tasks appear scattered across daily logs.
Quick Reference
More from muco-rolle/skills
write-prd
Collaboratively write a Product Requirements Document through structured interview and codebase exploration. Use when user wants to create a PRD, define requirements, plan a new capability, or write a spec.
11goos-adonis
Use when building, testing, or refactoring AdonisJS v7 applications with test-driven development. Covers outside-in TDD workflow, writing acceptance tests (api-client and browser-client), designing testable services with dependency injection, creating test doubles with container.swap, fixing fragile or slow tests, and restructuring fat controllers into clean service layers
11grill-me
Interview the user relentlessly about a plan or design until reaching a shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
9frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
9refactoring-ui
>
5write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
5