goal-lock

Solid

A discipline helper for autonomous and long sessions — given the active goal in `docs/goal.md`, list the unchecked deliverable subgoals (the actual `- [ ]` items), report how many remain, and let the operator (or an autonomous worker) decide whether the next iteration should keep advancing the goal or whether the goal's `Done when` criteria are already satisfied. Does *not* alter the agent loop or override the harness — this is a transparency / discipline tool, not a runtime hook.

AI & Automation 15 stars 4 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
40
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# goal-lock A small discipline helper. When an autonomous worker or a long interactive session is advancing the active goal in `docs/goal.md`, it's useful to know *at a glance* which deliverable subgoals are still unchecked. That's the entire purpose of this skill. ## What this does Reads the first `### YYYY-MM-DD | ...` subsection under `## Active goal` in `docs/goal.md` and lists every `- [ ]` (unchecked) deliverable subgoal. Also reports the count and the "Done when" line if present. ## What this does NOT do - Does not alter the Claude Code harness's turn loop. The agent still runs whatever the operator or scheduler invoked. - Does not auto-tick subgoals. Operator (or the per-commit hook that ticks subgoals on relevant commits) does that. - Does not enforce any policy. This is read-only reporting. If the operator wants autonomous mode to halt when all subgoals are checked, they wire `scripts/check-done.sh`'s exit code into their `AUTONOMY_MODE` driver. ## Why this exists `docs/goal.md` "Done when" criteria are prose plus a list of deliverable subgoals. Without a one-liner check, a long autonomous session has to either (a) re-read the entire goal file between iterations or (b) drift past the goal because no one re-checked completion. This skill makes the check a single `bash` call. ## Invocation ```bash # Default — list unchecked subgoals + counts bash skills/goal-lock/scripts/check-done.sh # One-line summary bash skills/goal-lock/scripts/chec...

Details

Author
MelonS
Repository
MelonS/MelonS-Agents
Created
2 months ago
Last Updated
today
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

goal

Autonomous goal loop — give it ONE goal plus how to verify it, the agent runs check→fix→check itself and comes back only with the finished result (code with audit, research with fact-check, content with critique, audit/backtest). Self-verification instead of constant supervision, with hard safety guards. Vary the loop with a verification rubric designed before it runs. Triggers — "work autonomously to the result", "don't come back until it's done", "run the loop yourself", "drive it to done".

14 Updated 3 days ago
Sanexxxx777
AI & Automation Listed

goal-skill

Load when the user wants to drive a non-trivial goal to completion under rigorous sub-agent orchestration, or invokes `/goal-skill`. Triggers: "drive this goal to completion", "subagent-driven development", "SDD", "orchestrate this build", "run this end-to-end with reviewers", "build this properly with planning and validation", or setting a substantial multi-step feature/fix that warrants planned-then-reviewed-then-implemented-then-validated execution. Use for work too large or risky for a single straight-line pass.

10 Updated today
meanllbrl
AI & Automation Listed

goal-workflow

Run a settled implementation goal as a bounded autonomous build loop — lock the goal from the conversation and any docs written this session, front-load every decision, map the terrain, write a completion-invariant contract before any code, then loop (building with explicit Agent-tool fan-out, committing at intervals, verifying at milestones with fresh-eyes against the contract) until the invariants hold, and close out. Gated on a `--confirm` flag asserting the user has manually set ultracode effort and auto-accept mode (a skill can set neither); without the flag it stops, gives the setup steps, and offers two paths — a managed `--confirm` run, or a copy-pasteable `/goal` command that hands the work to native goal + workflow orchestration. An optional `--commit` flag (default off) enables commit-at-intervals and push-at-milestones in both the managed run and the generated command; without it, nothing is committed. Use when a plan is settled and you want Claude to implement it end-to-end on its own — typically

3 Updated today
adamlinscott