dev-complete

Invoke the skill with a slot number or slot directory path, a kind of request or report, and the content as prose or a GitHub issue reference. It drives the authoring, approach, plan, execution, and review stages in order and stops at local commits.

Re-invoke with the same arguments and it resumes automatically. It determines the resume point from status markers in the slot artifacts, rebuilds the assumption ledger from disk, and reports which stage it resumed at and why.

No, it commits locally only and never pushes, opens pull requests, or writes to GitHub. Publishing stays user-initiated through the separate dev-issue and dev-pr-open skills, and every publish offer is always declined.

The run resolves the question on the merits from the source, repository, and AGENTS.md, records it as settled content plus an ASSUMPTION ledger line, and continues. Only true blockers, like undocumented build commands or exhausted retries, stop the run.

A failing phase gets three attempts total, and each stage gets three dispatches total, tracked separately. A retry is a diagnose-then-resume dispatch that hands the stage the recorded blocked reason with instructions to resolve the cause first.

review_iterations is a non-negative integer capped at 5, defaulting to 1, where each iteration is a full dev-review pass plus remediation of Blocker and High findings. Setting it to 0 skips the review tail entirely and ends the run at the execution stage.