/boot

> Initialize daily operating session -- load context, generate today's plan.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/boot is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Initialize daily operating session -- load context, generate today's plan.

Teams using /boot should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/boot/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/operations/boot/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/boot/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /boot Compares

Feature / Agent	/boot	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Initialize daily operating session -- load context, generate today's plan.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /boot

> Initialize daily operating session -- load context, generate today's plan.

## Usage
```
/boot [--quiet]
```

## What It Does
Runs the daily boot sequence: loads the week plan, generates today's working file, checks for overdue items, loads L0 context cache, and sets the operating mode. This is the first thing to run when the operator starts their day.

## Implementation
1. Load `rhythm/week-plan.md` -- current week's priorities and time blocks.
2. Generate `rhythm/today.md` -- today's schedule extracted from week plan.
3. Check `rhythm/energy.md` -- review yesterday's energy log.
4. Load L0 cache -- `cd engine && mix optimal.l0` for always-loaded context.
5. Scan signal files for overdue action items.
6. Report: today's non-negotiables, scheduled calls, energy recommendations.

If `--quiet`: skip the verbose output, just generate today.md.

## Examples
```bash
# Full boot sequence
/boot

# Quick boot without verbose output
/boot --quiet
```

## Command