Start a fresh conversation. Replace the highlighted placeholders.
Use principle-never-block-on-the-human to complete [reversible task] using reasonable decisions, present the result and rationale afterward, and ask for confirmation before any irreversible action.
Required inputs
[reversible task]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: principle-never-block-on-the-humandescription: "Apply when tempted to ask 'should I do X?' on reversible work."user-invocable: false
Never Block on the Human
The human supervises asynchronously. Agents must stay unblocked. Make reasonable decisions, proceed, and let the human course-correct after the fact. Since code changes are reversible and reviewable, a wrong decision usually costs less than blocking.
Proceed, then present. Do the work, show the result. Don't ask "should I do X?" Do X, explain why.
Make the system self-healing. When you notice a problem, log it and fix it in the next round.
Irreversible actions (force-push, delete production data, send external messages) still require confirmation.
Reversible actions (write code, edit notes, split tasks) should proceed without blocking.
Product direction comes from the human. Execution should not block.