journal-planner

Organize daily, weekly, monthly, and yearly notes with YAML frontmatter.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/KevinBean/emptyos --skill journal-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journal-planner
Source: https://github.com/KevinBean/emptyos/tree/main/skills/vault-journal-planner
Command: npx skills add https://github.com/KevinBean/emptyos --skill journal-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing daily, weekly, monthly, and yearly notes across different templates can be tedious and error-prone; this skill provides a structured approach to consistently create, connect, and review notes over multiple time horizons.

Core Features & Use Cases

  • Create and organize daily/weekly/monthly/yearly notes with unified naming conventions and templates.
  • Link related notes across horizons (e.g., weekly plans linked to monthly themes) for coherent planning.
  • Support quick entry and reviews with a predictable workflow that accelerates journaling and planning.

Quick Start

Create/open today's daily note and begin journaling with a simple prompt.

Frequently Asked Questions about journal-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure daily, weekly, monthly, and yearly journal notes in Obsidian?

To structure journal notes in Obsidian, use unified naming conventions and templates to organize time-based horizons. This approach enforces YAML frontmatter and links related notes across daily, weekly, monthly, and yearly scopes for coherent reviews.

What is the best way to link daily reflections to long-term planning workflows?

The best way to link daily reflections to long-term planning workflows is using a structured file hierarchy. By connecting notes across multiple time horizons, you create a predictable workflow that accelerates quick journaling entries and coherent long-term reviews.

How do I start time-management journaling with a quick entry prompt?

You can start time-management journaling by creating or opening today's daily note. A simple prompt initiates the process, leveraging structured templates and optional folders like scripts or references to maintain a consistent file hierarchy for quick discovery and review.

Does this journaling approach require YAML frontmatter for templates?

Yes, this journaling approach requires YAML frontmatter containing name and description fields for templates. Enforcing this frontmatter ensures consistent organization across daily, weekly, monthly, and yearly notes, preventing structural errors in your time-based workflows.

Can I use optional folders for scripts and references when managing planning notes?

Yes, you can use optional folders for scripts and references when managing planning notes. These folders support diverse workflows and scenarios, providing a consistent file hierarchy that aids discovery and organizes time-based journaling assets effectively alongside daily and weekly entries.

Why does managing multiple time horizon templates become error-prone without a structured approach?

Managing multiple time horizon templates becomes error-prone without a structured approach due to inconsistent naming and disconnected notes. A unified system enforces YAML frontmatter and predictable file hierarchies, ensuring daily entries correctly link to monthly themes and yearly reviews without tedious manual corrections.