From e3630acc146a641f29fdf23f9c28d5d9cdf945b8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mois=C3=A9s=20Gana=20Obreg=C3=B3n?= Date: Sat, 3 Jan 2026 00:40:27 +0000 Subject: [PATCH 1/3] fix(conductor): ensure track completion and doc sync are committed automatically This adds explicit commit steps to the implement command for: - Track completion status updates in tracks.md - Project documentation synchronization - Track cleanup (archiving or deleting) BUG=16 --- commands/conductor/implement.toml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/commands/conductor/implement.toml b/commands/conductor/implement.toml index 18e256b..48e9f7f 100644 --- a/commands/conductor/implement.toml +++ b/commands/conductor/implement.toml @@ -76,6 +76,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai 5. **Finalize Track:** - After all tasks in the track's local `plan.md` are completed, you MUST update the track's status in the tracks file. - This requires finding the specific heading for the track (e.g., `## [~] Track: `) and replacing it with the completed status (e.g., `## [x] Track: `). + - **Commit Changes:** Stage `conductor/tracks.md` and commit with the message `conductor(track): Mark track '' as complete`. - Announce that the track is fully complete and the tracks file has been updated. --- @@ -127,6 +128,9 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai 6. **Final Report:** Announce the completion of the synchronization process and provide a summary of the actions taken. - **Construct the Message:** Based on the records of which files were changed, construct a summary message. + - **Commit Changes:** + - If any files were changed (`product.md`, `tech-stack.md`, or `product-guidelines.md`), you MUST stage them and commit them. + - **Commit Message:** `conductor(docs): Synchronize docs for track ''` - **Example (if product.md was changed, but others were not):** > "Documentation synchronization is complete. > - **Changes made to `product.md`:** The user-facing description of the product was updated to include the new feature. @@ -154,7 +158,8 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai i. **Create Archive Directory:** Check for the existence of `conductor/archive/`. If it does not exist, create it. ii. **Archive Track Folder:** Move the track's folder from `conductor/tracks/` to `conductor/archive/`. iii. **Remove from Tracks File:** Read the content of `conductor/tracks.md`, remove the entire section for the completed track (the part that starts with `---` and contains the track description), and write the modified content back to the file. - iv. **Announce Success:** Announce: "Track '' has been successfully archived." + iv. **Commit Changes:** Stage `conductor/tracks.md` and `conductor/archive/`. Commit with the message `conductor(track): Archive track ''`. + v. **Announce Success:** Announce: "Track '' has been successfully archived." * **If user chooses "B" (Delete):** i. **CRITICAL WARNING:** Before proceeding, you MUST ask for a final confirmation due to the irreversible nature of the action. > "WARNING: This will permanently delete the track folder and all its contents. This action cannot be undone. Are you sure you want to proceed? (yes/no)" @@ -162,7 +167,8 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai - **If 'yes'**: a. **Delete Track Folder:** Permanently delete the track's folder from `conductor/tracks/`. b. **Remove from Tracks File:** Read the content of `conductor/tracks.md`, remove the entire section for the completed track, and write the modified content back to the file. - c. **Announce Success:** Announce: "Track '' has been permanently deleted." + c. **Commit Changes:** Stage `conductor/tracks.md` and the deletion of `conductor/tracks/`. Commit with the message `conductor(track): Delete track ''`. + d. **Announce Success:** Announce: "Track '' has been permanently deleted." - **If 'no' (or anything else)**: a. **Announce Cancellation:** Announce: "Deletion cancelled. The track has not been changed." * **If user chooses "C" (Skip) or provides any other input:** From e5815448e01b23e4a55b7f629d559f4c7bcdccf5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mois=C3=A9s=20Gana=20Obreg=C3=B3n?= Date: Sun, 4 Jan 2026 08:23:00 +0000 Subject: [PATCH 2/3] correct step numbers --- commands/conductor/implement.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/commands/conductor/implement.toml b/commands/conductor/implement.toml index 48e9f7f..9c0eaf3 100644 --- a/commands/conductor/implement.toml +++ b/commands/conductor/implement.toml @@ -81,7 +81,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai --- -## 6.0 SYNCHRONIZE PROJECT DOCUMENTATION +## 4.0 SYNCHRONIZE PROJECT DOCUMENTATION **PROTOCOL: Update project-level documentation based on the completed track.** 1. **Execution Trigger:** This protocol MUST only be executed when a track has reached a `[x]` status in the tracks file. DO NOT execute this protocol for any other track status changes. @@ -141,7 +141,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai --- -## 7.0 TRACK CLEANUP +## 5.0 TRACK CLEANUP **PROTOCOL: Offer to archive or delete the completed track.** 1. **Execution Trigger:** This protocol MUST only be executed after the current track has been successfully implemented and the `SYNCHRONIZE PROJECT DOCUMENTATION` step is complete. From dd1cd1c651a25cadadedeb2c6c78590c945aeaeb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mois=C3=A9s=20Gana=20Obreg=C3=B3n?= Date: Mon, 5 Jan 2026 22:24:13 +0000 Subject: [PATCH 3/3] chore(conductor): Update commit message templates to follow Conventional Commits --- commands/conductor/implement.toml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/commands/conductor/implement.toml b/commands/conductor/implement.toml index 9c0eaf3..d1536bd 100644 --- a/commands/conductor/implement.toml +++ b/commands/conductor/implement.toml @@ -76,7 +76,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai 5. **Finalize Track:** - After all tasks in the track's local `plan.md` are completed, you MUST update the track's status in the tracks file. - This requires finding the specific heading for the track (e.g., `## [~] Track: `) and replacing it with the completed status (e.g., `## [x] Track: `). - - **Commit Changes:** Stage `conductor/tracks.md` and commit with the message `conductor(track): Mark track '' as complete`. + - **Commit Changes:** Stage `conductor/tracks.md` and commit with the message `chore(conductor): Mark track '' as complete`. - Announce that the track is fully complete and the tracks file has been updated. --- @@ -130,7 +130,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai - **Construct the Message:** Based on the records of which files were changed, construct a summary message. - **Commit Changes:** - If any files were changed (`product.md`, `tech-stack.md`, or `product-guidelines.md`), you MUST stage them and commit them. - - **Commit Message:** `conductor(docs): Synchronize docs for track ''` + - **Commit Message:** `docs(conductor): Synchronize docs for track ''` - **Example (if product.md was changed, but others were not):** > "Documentation synchronization is complete. > - **Changes made to `product.md`:** The user-facing description of the product was updated to include the new feature. @@ -158,7 +158,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai i. **Create Archive Directory:** Check for the existence of `conductor/archive/`. If it does not exist, create it. ii. **Archive Track Folder:** Move the track's folder from `conductor/tracks/` to `conductor/archive/`. iii. **Remove from Tracks File:** Read the content of `conductor/tracks.md`, remove the entire section for the completed track (the part that starts with `---` and contains the track description), and write the modified content back to the file. - iv. **Commit Changes:** Stage `conductor/tracks.md` and `conductor/archive/`. Commit with the message `conductor(track): Archive track ''`. + iv. **Commit Changes:** Stage `conductor/tracks.md` and `conductor/archive/`. Commit with the message `chore(conductor): Archive track ''`. v. **Announce Success:** Announce: "Track '' has been successfully archived." * **If user chooses "B" (Delete):** i. **CRITICAL WARNING:** Before proceeding, you MUST ask for a final confirmation due to the irreversible nature of the action. @@ -167,7 +167,7 @@ CRITICAL: You must validate the success of every tool call. If any tool call fai - **If 'yes'**: a. **Delete Track Folder:** Permanently delete the track's folder from `conductor/tracks/`. b. **Remove from Tracks File:** Read the content of `conductor/tracks.md`, remove the entire section for the completed track, and write the modified content back to the file. - c. **Commit Changes:** Stage `conductor/tracks.md` and the deletion of `conductor/tracks/`. Commit with the message `conductor(track): Delete track ''`. + c. **Commit Changes:** Stage `conductor/tracks.md` and the deletion of `conductor/tracks/`. Commit with the message `chore(conductor): Delete track ''`. d. **Announce Success:** Announce: "Track '' has been permanently deleted." - **If 'no' (or anything else)**: a. **Announce Cancellation:** Announce: "Deletion cancelled. The track has not been changed."