Plow Ahead
Proceed through ordinary ambiguity. Make reasonable assumptions, keep momentum,
validate as you go, and make the final recap strong enough that the user can see
what decisions were made while they were away.
Autonomy Contract
Treat the user's instruction as permission to continue through normal
uncertainty:
- Turn routine questions into explicit assumptions.
- Prefer the smallest reversible choice that satisfies the request.
- Use repo conventions, nearby patterns, local docs, tests, and existing product
behavior as the decision source.
- Keep working through normal test failures, missing context, implementation
choices, and minor ambiguity.
- Use subagents for independent research, implementation, or verification when
parallel work can reduce idle time or improve coverage.
- Do not pause merely to ask which reasonable option the user prefers. Pick one,
record why, and keep going.
Stop Conditions
Stop and ask only for true blockers:
- Required credentials, secrets, accounts, paid services, or private data are
unavailable.
- The next step would be destructive, irreversible, or production-mutating.
- The task requires an explicit branch operation, history rewrite, force push, or
deletion that the user did not directly request.
- Legal, safety, privacy, or security risk is high and cannot be reduced by a
conservative local choice.
- The user explicitly reserved a decision for themselves.
- A verification failure repeats after reasonable investigation and the next fix
would be speculative or broad.
If blocked, leave a self-contained handoff: what was done, what blocks progress,
what exact input is needed, and the next command or file to inspect.
Decision Rules
When choosing without the user:
- Reuse existing patterns before inventing new ones.
- Prefer local, reversible, low-blast-radius changes.
- Keep scope tight to the user's request.
- Choose correctness and maintainability over cleverness.
- Validate with the smallest meaningful test first, then broaden only when the
risk justifies it.
- If two options are close, choose the one that is easier for the user or a
reviewer to understand later.
Maintain a lightweight decision log while working. It can live in notes, the
plan, or your final answer, but do not create a new repo artifact unless the task
needs one.
Work Loop
- Restate the goal internally and identify likely acceptance criteria.
- Inspect the real files, docs, issue, PR, screenshots, or runtime behavior
before editing.
- Make assumptions explicit, then act on them.
- Implement in small coherent steps.
- Run targeted validation and fix issues found by validation.
- Repeat until the requested work is complete or a stop condition applies.
- Before final response, review the diff and verification evidence against the
original request.
Final Recap
End with a recap that makes autonomous decisions auditable:
Goal
- What you completed.
Key decisions
- Assumptions and choices made without stopping, with short reasons.
Changes
- Files, behavior, docs, or configuration changed.
Validation
- Commands, tests, screenshots, CI, or manual checks run and their result.
Remaining risk
- Anything not verified, deferred, or blocked.
Keep the recap factual. Do not hide uncertainty, skipped validation, or judgment
calls.
1---2name: plow-ahead3description: >-4 Use when the user explicitly wants autonomous progress without routine5 clarification stops: "plow ahead", "do not stop", "use your best judgment",6 "keep going until done", "finish while I am away", "do not ask questions7 unless truly blocked", or similar. Convert ordinary ambiguity into stated8 assumptions, proceed through implementation and validation, stop only for true9 blockers, and end with a clear recap of decisions, changes, verification, and10 residual risk.11metadata:12 source: https://skillmd.com/skills/builderio/plow-ahead13---1415# Plow Ahead1617Proceed through ordinary ambiguity. Make reasonable assumptions, keep momentum,18validate as you go, and make the final recap strong enough that the user can see19what decisions were made while they were away.2021## Autonomy Contract2223Treat the user's instruction as permission to continue through normal24uncertainty:2526- Turn routine questions into explicit assumptions.27- Prefer the smallest reversible choice that satisfies the request.28- Use repo conventions, nearby patterns, local docs, tests, and existing product29 behavior as the decision source.30- Keep working through normal test failures, missing context, implementation31 choices, and minor ambiguity.32- Use subagents for independent research, implementation, or verification when33 parallel work can reduce idle time or improve coverage.34- Do not pause merely to ask which reasonable option the user prefers. Pick one,35 record why, and keep going.3637## Stop Conditions3839Stop and ask only for true blockers:4041- Required credentials, secrets, accounts, paid services, or private data are42 unavailable.43- The next step would be destructive, irreversible, or production-mutating.44- The task requires an explicit branch operation, history rewrite, force push, or45 deletion that the user did not directly request.46- Legal, safety, privacy, or security risk is high and cannot be reduced by a47 conservative local choice.48- The user explicitly reserved a decision for themselves.49- A verification failure repeats after reasonable investigation and the next fix50 would be speculative or broad.5152If blocked, leave a self-contained handoff: what was done, what blocks progress,53what exact input is needed, and the next command or file to inspect.5455## Decision Rules5657When choosing without the user:58591. Reuse existing patterns before inventing new ones.602. Prefer local, reversible, low-blast-radius changes.613. Keep scope tight to the user's request.624. Choose correctness and maintainability over cleverness.635. Validate with the smallest meaningful test first, then broaden only when the64 risk justifies it.656. If two options are close, choose the one that is easier for the user or a66 reviewer to understand later.6768Maintain a lightweight decision log while working. It can live in notes, the69plan, or your final answer, but do not create a new repo artifact unless the task70needs one.7172## Work Loop73741. Restate the goal internally and identify likely acceptance criteria.752. Inspect the real files, docs, issue, PR, screenshots, or runtime behavior76 before editing.773. Make assumptions explicit, then act on them.784. Implement in small coherent steps.795. Run targeted validation and fix issues found by validation.806. Repeat until the requested work is complete or a stop condition applies.817. Before final response, review the diff and verification evidence against the82 original request.8384## Final Recap8586End with a recap that makes autonomous decisions auditable:8788```md89Goal90- What you completed.9192Key decisions93- Assumptions and choices made without stopping, with short reasons.9495Changes96- Files, behavior, docs, or configuration changed.9798Validation99- Commands, tests, screenshots, CI, or manual checks run and their result.100101Remaining risk102- Anything not verified, deferred, or blocked.103```104105Keep the recap factual. Do not hide uncertainty, skipped validation, or judgment106calls.