Step: Refactor task command to delegate work.

Author: apiad

.gemini/commands/task.toml

@@ -1,4 +1,4 @@
-description = "Manage project tasks: create, work on, report, or update roadmap."
+description = "Manage the project roadmap (TASKS.md) and implement tasks via a strict, agent-delegated TCR loop."
 
 prompt = """
 You are an expert project manager. Your goal is to manage the project's roadmap in `TASKS.md`.
@@ -7,41 +7,38 @@ Depending on the user's intent or arguments, perform one of the following action
 ### **Action: Create**
 Add a new task to `TASKS.md`.
 1. Read `TASKS.md` to understand the current structure and existing tasks.
-2. If the user provided a task description in the arguments, use it. Otherwise, infer the task from the recent conversation context.
+2. If the user provided a task description in the arguments, use it. Otherwise, identify the task from the recent conversation context.
 3. Identify the appropriate section for the new task or create a new one if necessary.
 4. Add the task with a clear description and status 'Todo' [ ].
 5. Ensure the task follows the existing formatting conventions and verify the file after the update.
 
 ### **Action: Work**
-Implement a task using a strict Test-Commit-Revert (TCR) protocol on a feature branch.
+Implement a task using a strict, agent-delegated Test-Commit-Revert (TCR) protocol on a feature branch.
 1. **Pre-flight Verification:**
    - Verify `git status --porcelain` is empty (clean tree).
    - Verify `git branch --show-current` is `main`.
    - Run `make test` and ensure all tests pass. If any fail, notify the user and stop.
 2. **Task Setup:**
    - Identify the target task from arguments or context.
-   - Mark it as `[/] In Progress (@!{{ git config user.email | cut -d'@' -f1 }})` in `TASKS.md`.
+   - Mark it as `[/] In Progress (@apiad)` in `TASKS.md`.
    - Generate a descriptive kebab-case branch name (e.g., `feature/task-description`).
    - Create and switch to the branch: `git checkout -b <branch-name>`.
-3. **The TCR Loop:**
-   - Break the task into granular, testable steps.
-   - For each step:
-     - **Red:** Write a failing test. Run `make test` to confirm it fails specifically for the new case.
-     - **Green:** Implement the minimal code needed to pass the test.
-     - **Verify:** Run `make test`.
-       - **If Pass:** Run `git add . && git commit -m "Step: <description of changes>"`.
-       - **If Fail:** Attempt one quick fix. If it still fails, run `git checkout .` to revert to the last green state.
-     - **Check-in:** Use `ask_user` to report the step's result (Commit or Revert) and confirm the next step.
+3. **The TCR Loop (Delegation):**
+   - Break the task into granular, testable steps based on the project plan (if one exists).
+   - For each step, **delegate the implementation to the specialized `coder` subagent**:
+     - Instruct the `coder` to follow its Red-Green-Verify mantra (write test, implement code, verify).
+     - **If the `coder` reports success:** Run `git add . && git commit -m "Step: <description of changes>"`.
+     - **If the `coder` reports failure:** Run `git checkout .` to revert the current step to the last green state.
+   - Use `ask_user` to report each step's result and confirm before proceeding to the next one.
 4. **Integration & Finalization:**
    - Once all steps are complete, run a full `make test`.
    - Use `ask_user` to request permission to merge back to `main`.
    - If approved:
      - Switch to `main`: `git checkout main`.
-     - Merge/Rebase the branch: `git merge <branch-name>`.
+     - Merge the branch: `git merge <branch-name>`.
      - Run `make test` on `main`.
      - Delete the feature branch: `git branch -d <branch-name>`.
-   - Update `TASKS.md` to reflect the current state (mark as `[x] Done` if complete).
-5. **Note:** If a task already has a plan in `plans/`, use it as the roadmap for the TCR loop steps.
+   - Update `TASKS.md` to reflect the final state (mark as `[x] Done`).
 
 ### **Action: Report**
 Produce a strategic report of current tasks.
@@ -58,7 +55,5 @@ Synchronize `TASKS.md` with the project's progress.
 5. Verify the file after the update.
 
 ---
-**Note:** If the intent is unclear, ask the user for clarification.
-
-If no clear intent is provided, default to "Report" to give an overview of current tasks and priorities, and ask the user if they want to create a new task or work on an existing one.
+**Note:** If the intent is unclear, ask for clarification. Default to "Report" if no action is specified.
 """

journal/2026-03-23.md

@@ -21,3 +21,4 @@
 [2026-03-23T07:41:37] - Finalize release v0.20.0.
 [2026-03-23T07:48:09] - Commit coder agent implementation plan.
 [2026-03-23T07:49:10] - Implement coder subagent for granular implementation delegation.
+[2026-03-23T07:49:55] - Refactor /task command to delegate granular steps to the coder subagent.

tests/test_task_command.py

@@ -0,0 +1,11 @@
+import toml
+
+def test_task_command_delegates_to_coder():
+    with open(".gemini/commands/task.toml", "r") as f:
+        config = toml.loads(f.read())
+    
+    prompt = config["prompt"]
+    # Check that the "work" action (usually in the prompt) mentions delegation to the coder
+    assert "coder" in prompt.lower()
+    assert "subagent" in prompt.lower()
+    assert "delegate" in prompt.lower()