goal-lock
SolidA 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.
Install
Quality Score: 86/100
Skill Content
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
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".
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.
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