howarewoo woostack-change
Implement one small, bounded, non-bug enhancement or refactor from the user's request through one isolated worktree and Graphite branch, ending in at most one complete reviewable PR. Change owns delivery through the shared bounded-delivery contract. It makes no provider call and invokes no other woostack workflow. The accepted scope is the authority; Git, Graphite, and GitHub are the delivery evidence.
Command
/woostack-change <goal>
Admit the request before mutation
Clarify only what is needed to identify the target, outcome, allowed paths, non-goals, acceptance criteria, and a focused verification plus changed-path smoke scenario. State the interpreted bounded scope and derive one stable task identity. Do not create a branch, worktree, or file change while classifying or clarifying.
Reject or reroute before any mutation:
- a bug, regression, incident, production fault, or root-cause investigation goes to
woostack-fix; - work that needs multiple PRs, dependency increments, or coordinated phases goes to
woostack-build; and - genuinely greenfield creation goes to
woostack-bootstrap.
Proceed only when the complete safe scope is a non-bug change that fits one PR. If the request expands later, stop and reroute rather than silently widening it.
Deliver the accepted scope
Follow the shared bounded-delivery contract for the active task contract, isolated worktree creation/resume, implementation, focused verification and smoke, independent review, Graphite submission, read-back, retention, and return evidence. Change adds no approval gate or persisted plan. It remains a non-bug command; shared mechanics do not admit Fix work through Change.