You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
5. Verify the update by reading the new `TASKS.md`.
14
16
15
17
### **Action: Work**
16
18
Implement a task using a strict, agent-delegated Test-Commit-Revert (TCR) protocol on a feature branch.
19
+
17
20
1. **Pre-flight Verification:**
18
21
- Verify `git status --porcelain` is empty (clean tree).
19
22
- Verify `git branch --show-current` is `main`.
20
23
- Run `make test` and ensure all tests pass. If any fail, notify the user and stop.
24
+
21
25
2. **Task Setup:**
22
-
- Identify the target task from arguments or context.
23
-
- Mark it as `[/] In Progress (@apiad)` in `TASKS.md`.
26
+
- Identify the target task ID from arguments or context.
27
+
- Run `python .gemini/scripts/task.py start --task-id <ID>` to mark it in progress.
24
28
- Generate a descriptive kebab-case branch name (e.g., `feature/task-description`).
25
29
- Create and switch to the branch: `git checkout -b <branch-name>`.
30
+
26
31
3. **The TCR Loop (Delegation):**
27
32
- Break the task into granular, testable steps based on the project plan (if one exists).
28
33
- For each step, **delegate the implementation to the specialized `coder` subagent**:
29
34
- Instruct the `coder` to follow its Red-Green-Verify mantra (write test, implement code, verify).
30
35
- **If the `coder` reports success:** Run `git add . && git commit -m "Step: <description of changes>"`.
31
36
- **If the `coder` reports failure:** Run `git checkout .` to revert the current step to the last green state.
32
37
- Use `ask_user` to report each step's result and confirm before proceeding to the next one.
38
+
39
+
NOTE: The coder subagent is very dumb, only for grunt coding. Make sure to give it detailed instructions and to split the task into very small steps. If the coder keeps failing and the task explanation cannot be simplified further, then fix it yourself. If that doesn't work, ask the user for clarification and possibly update the task plan.
40
+
33
41
4. **Integration & Finalization:**
34
42
- Once all steps are complete, run a full `make test`.
35
43
- Use `ask_user` to request permission to merge back to `main`.
@@ -38,20 +46,20 @@ Implement a task using a strict, agent-delegated Test-Commit-Revert (TCR) protoc
38
46
- Merge the branch: `git merge <branch-name>`.
39
47
- Run `make test` on `main`.
40
48
- Delete the feature branch: `git branch -d <branch-name>`.
41
-
- Update `TASKS.md` to reflect the final state (mark as `[x] Done`).
49
+
- Run `python .gemini/scripts/task.py archive --task-id <ID>` to mark it done.
42
50
43
51
### **Action: Report**
44
52
Produce a strategic report of current tasks.
45
-
1. Analyze `TASKS.md` and list all [ ] Todo or [/] In Progress tasks.
53
+
1. Read `TASKS.md` and list all active tasks (Todo or In Progress).
46
54
2. For each, provide a brief assessment of its **Feasibility** and **Strategic Value**.
47
55
3. Sort the list by high value and feasibility, suggesting 2-3 top priorities.
48
56
49
57
### **Action: Update**
50
58
Synchronize `TASKS.md` with the project's progress.
51
59
1. Read `TASKS.md`, `CHANGELOG.md`, and recent `journal/` entries.
52
60
2. Analyze uncommitted changes and conversation context.
53
-
3. Update task statuses: mark completed as [x] Done, move current work to [/] In Progress, and add new high-level features if missing.
54
-
4. If a task was implemented differently, update its description.
61
+
3. Use the script subcommands (`start`, `cancel`, `archive`) to update task statuses as appropriate.
62
+
4. If a task requires a linked plan, use `python .gemini/scripts/task.py attach-plan --task-id <ID> --plan-path <path>`.
0 commit comments