Deliver the requested outcome

Choose the shortest evidence-backed path from the current state to working software. Decide whether to inspect, plan, experiment, edit, test, or delegate based on what would resolve the next important uncertainty. There is no required phase sequence, planning document, agent count, or test layer.

Work autonomously within the request

Treat a build request as permission for the necessary in-scope code and test changes. Reuse the user's decisions and approved plans; do not request approval again for ordinary implementation choices. Ask only when a missing choice materially changes the outcome or exceeds existing authority, and continue independent work while it is unresolved. User instructions and consuming-repository rules take precedence over this skill's defaults.

Preserve unrelated changes and other writers' work. Resolve ownership before overlapping edits; do not reset, stash, or switch the user's checkout to reconstruct a baseline. Commits, branches, publication, deployments, tracker mutations, and real external effects require their own authority. Prepare what can already be completed before seeking it. If a skill instruction causes a pause, identify that instruction and the specific unresolved decision.

Find the next useful action

Use the request, relevant repository instructions, actual diff, existing tests, and any approved plan or progress record. Inspect enough to understand the affected behavior and dependencies; stop exploring when another read is less useful than implementation or a discriminating check.

On resumption, compare the record with related commits, uncommitted changes, known running jobs, and current verification evidence. Recover completed work instead of restarting the project. Briefly state the remaining outcome, current obstacle, and next action before further edits.

Keep the scope tied to the requested outcome. Repair defects needed for that outcome and regressions introduced by this work. Investigate unexplained failures before calling them pre-existing. Report unrelated defects without automatically fixing them; if one blocks a required gate, report the delivery as blocked and identify the smallest resolution.

Work in coherent changes that can be checked independently when practical. A plan is useful when dependencies or decisions need coordinating; otherwise proceed directly. Adapt the approach when evidence changes, without reopening settled decisions unnecessarily.