Repository navigation
v0.10.0 — optional work plans
Optional work plans connect goals and tasks to project memory without introducing a task-tracker runtime.
- Set
plan: docs/work-plan.mdin.omut/brief.mdto include an existing Markdown plan in project context and pack overviews. - Set
plan: work/README.mdin.omut/local/instance.mdfor a copy-only package, relative to.omut/local/. Local plans stay out of pack overviews and remain in the main checkout when working in linked worktrees. contextand startup hooks include the selected index with source locations. Linked cards are not followed, and task states are never edited automatically.checkreports invalid, missing, unreadable or out-of-layer plan pointers and warns above 80 lines or 8000 Unicode characters. Case aliases on case-insensitive filesystems cannot bypass the local-layer exclusion.- Project rules include an example organized by goals, task IDs, dependencies and acceptance criteria, with one authoritative task state and explicit ownership of active work.
Plans are optional. Existing projects and task packages require no migration; start and zero do not create or rewrite plans.
After upgrading, run omut zero only where you want to refresh the agent rules; in a pack, refresh the pack root for the new lead guidance. Preserve active task packages and coordinate changes with their keeper.
Verified locally with go vet ./..., go test ./..., strict meta checks, and CLI fixtures for plan provenance, privacy, worktrees, error handling, size budgets and preservation of plan/card files.