Compile the board
Turn rough intent into a scoped goal.md, state.yaml, and starter /goal command.
Goal Buddy
A /goal operating system for long runs
Goal Buddy prepares a goal.md for long /goal runs, keeps state.yaml as local truth, and pressures the work with a local board, receipts, and final proof.
$npx goalbuddy
$$goal-prep # Codex
$/goal-prep # Claude Code
Prepared docs/goals/improve-project/
goal.md
state.yaml
notes/
/goal follow goal.md
Turn rough intent into a scoped goal.md, state.yaml, and starter /goal command.
/goal reads and updates local state instead of relying on a hosted tracker.
Receipts map back to the original outcome before /goal can claim the work is complete.
GoalBuddy opens a local live board before the task list is finished, so the work becomes visible as Scout, Judge, and Worker tasks populate.
Goal Buddy separates mapping, decision, and implementation so /goal can continue from explicit state and keep checking the same finish line every turn.
Capture file ownership, commands, constraints, risks, and unknowns before selecting implementation work.
Convert findings into one task with allowed files, stop conditions, and concrete acceptance checks.
Implement the slice, record changed files and verification output, then hand updated state back to /goal.
Goal Buddy writes the goal charter, machine-readable state, and notes into your repository. /goal can resume from those files, and the local board shows the same truth without replacing it.
Human-readable charter for /goal: intent, scope, acceptance criteria, and run instructions.
# Goal Charter
/goal Follow docs/goals/<slug>/goal.md
Structured board state for active agent, tasks, dependencies, receipts, and verification status.
version: 2
active_agent: judge
Longer Scout findings, Worker receipts, blocked-task notes, and command output summaries.
T003-worker-receipt.md
Run the CLI once, restart your agent, prepare the board, and start with the printed /goal command.
Each role writes enough information for the next role to continue, and verification gates completion claims.
GoalBuddy keeps the model small: one local board, one active task, one receipt trail, and a final audit that maps evidence back to the original owner outcome.
Record the observable signal that proves the original outcome, then keep testing each slice against it.
Open the live board as tasks populate, without credentials or a hosted tracker.
Every completed or blocked task leaves changed files, commands, evidence, and remaining blockers.
Completion requires a Judge or PM audit with full_outcome_complete: true.
If safe local work remains, /goal advances instead of stopping after the first passing slice.
Judge chooses the largest safe useful slice, and Worker completes it before returning a receipt.
MIT licensed. Dependency-free runtime. Built around local goal.md and state.yaml files.
Track GoalBuddy’s open source momentum over time.