docs: require cleanup before completion
This commit is contained in:
@@ -13,6 +13,7 @@ Execute the latest approved plan for: $ARGUMENTS
|
||||
5. Reuse existing git safety rules and avoid destructive git behavior; do not add push automation.
|
||||
6. If no new changes exist at a checkpoint, skip commit creation rather than creating empty or duplicate commits.
|
||||
7. Follow the plan exactly. If the plan is contradictory, missing a dependency, or fails verification twice, stop, capture evidence, set the execution note to blocked, and send the work back to `planner`.
|
||||
8. Finish by creating a final completion commit when changes remain, then update the execution note to `Status: done` or `Status: blocked` and summarize what changed.
|
||||
8. Before creating the final completion commit, clean up temporary artifacts generated during the build (e.g., scratch files, screenshots, logs, transient reports, caches). Intended committed deliverables are not cleanup targets.
|
||||
9. Finish by creating a final completion commit when changes remain, then update the execution note to `Status: done` or `Status: blocked` and summarize what changed.
|
||||
|
||||
Automatic commits are required during `/build` as defined above.
|
||||
|
||||
Reference in New Issue
Block a user