Document commit and milestone steps in the agent workflow
This commit is contained in:
1 parent
da876e3545
commit
d7b0203502
1 file changed
+4
@@ -145,6 +145,10 @@ For each task:
|
|||||||
5. Update documentation and `MEMORY.md` if the change creates lasting context.
|
5. Update documentation and `MEMORY.md` if the change creates lasting context.
|
||||||
6. Mark the task complete.
|
6. Mark the task complete.
|
||||||
7. Move its section to `DONE.md` when the entire section is complete.
|
7. Move its section to `DONE.md` when the entire section is complete.
|
||||||
|
8. Commit the changes to the version control system with a descriptive message.
|
||||||
|
9. If a section from `TODO.md` has been fully completed, create a new version or tag in the version control system to mark the milestone.
|
||||||
|
10. Push the committed changes to the shared repository if applicable.
|
||||||
|
11. Note the new version or tag created in the version control system in any relevant documentation or handoff summary.
|
||||||
|
|
||||||
Avoid unrelated refactors unless they are required for the task or explicitly approved.
|
Avoid unrelated refactors unless they are required for the task or explicitly approved.
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user