Use when executing Patchmill implementation plans that require one plan implementation subagent and final full-worktree readiness review before landing
Use when executing Patchmill implementation plans that require final full-worktree readiness review before landing
Use when executing Patchmill implementation plans with Superpowers task-level development plus final validation and pull-request readiness, without extra Codex or thermo-nuclear full-worktree reviews
Decide when Patchmill may direct-land and when it must open a PR.
Use when Patchmill run-once changes visible UI and needs committed reference screenshot evidence in the final pr-created JSON.
Use for Patchmill run-once spec and plan creation. Wraps sibling Superpowers brainstorming and writing-plans skills with Patchmill worktree, artifact path, and test-value policy.
Use when creating, editing, reviewing, or refactoring code modules to keep files focused, readable, and maintainable as code grows.
Use when Patchmill dogfoods its own development stage.