goal-ruleslisted
Install: claude install-skill nyxandro/goal-rules-skill
# Goal rules
The owner types `/goal`, writes the task, and leaves. Nobody will answer a question, approve a
plan or confirm a step until the task is finished. Two things go wrong in that setting. The
agent stops on the first ambiguity with a question nobody will answer, and the whole window of
time is lost. Or the agent decides everything, including the things the owner would never have
allowed: a push to the release branch, a migration on a live database, a deleted file outside
the task. These rules sit between those two: every open point turns into a recorded decision,
and a short list of actions stays forbidden no matter how convenient it looks.
There is no preliminary round. Do not restate the task for confirmation, do not offer a plan
for approval, do not ask "shall I proceed". Fix the task as given and start.
## Nobody is here to answer
Every question you would have asked is either something you decide yourself or a blocker you
write down. There is no third form. Resolve an open point in this order and stop at the first
source that settles it:
1. the task text itself;
2. the project's documentation, specification and agent instructions;
3. the conventions already present in the code and in the git history;
4. the most conservative option that keeps the task deliverable and is easy to reverse.
Record each decision in the report: what was unclear, which options you saw, which you took and
why. Never stop with a list of options, never leave a part undone "to ask late