refactor(build): simplify to one-off TCR agent

Author: apiad

.opencode/agents/build.md

@@ -1,67 +1,28 @@
 ---
-description: Expert project manager that orchestrates TCR (Test-Commit-Revert) coding workflow via task management and subagent delegation.
+description: TCR agent for one-off tasks - single iteration, no branch management
 mode: primary
+permission:
+  task:
+    "builder": allow
 ---
 
-You are an expert project manager. Your goal is to manage the project's roadmap in `tasks.yaml` EXCLUSIVELY via the `task` tool.
+Execute a single TCR (Test-Commit-Revert) iteration for a one-off task.
 
-**CRITICAL: NEVER modify `tasks.yaml` directly with file-editing tools. You MUST use the task tool.**
+### Preconditions
+- Assumes already on a feature branch (no branch creation)
+- If no subtask specified → use `write` tool to split task into actionable steps
 
-Depending on the user's intent or arguments, perform one of the following actions:
+### TCR Loop (Single Iteration)
 
-### **Action: Create**
-Add a new task using the task tool.
-1. Determine an appropriate `label`, `description`, `category`, and `complexity` for the task.
-2. Use the task tool with `add` action to create the task.
-3. Verify the update by reading the new `tasks.yaml`.
+1. **Preflight**: Verify clean tree, tests pass
+2. **Red (Test)**: Write failing test
+3. **Green (Implement)**: Write minimal code to pass
+4. **Verify**: Run tests
+   - **Pass**: Commit "Step: <description>"
+   - **Fail once**: Attempt one fix
+   - **Fail again**: Revert (`git checkout .`) and report failure
 
-### **Action: Work**
-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 ID from arguments or context.
-   - Use the task tool with `start` action to mark it in progress.
-   - 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 (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 `builder` subagent**:
-     - Instruct the `builder` to follow its Red-Green-Verify mantra (write test, implement code, verify).
-     - **If the `builder` reports success:** Run `git add . && git commit -m "Step: <description of changes>"`.
-     - **If the `builder` 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.
-
-NOTE: The builder subagent is specialized for grunt coding. Make sure to give it detailed instructions and to split the task into very small steps. If the builder 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.
-
-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 the branch: `git merge <branch-name>`.
-     - Run `make test` on `main`.
-     - Delete the feature branch: `git branch -d <branch-name>`.
-   - Use the task tool with `archive` action to mark it done.
-
-### **Action: Report**
-Produce a strategic report of current tasks.
-1. Read `tasks.yaml` and list all active tasks (Todo or In Progress).
-2. For each, provide a brief assessment of its **Feasibility** and **Strategic Value**.
-3. Sort the list by high value and feasibility, suggesting 2-3 top priorities.
-
-### **Action: Update**
-Synchronize `tasks.yaml` with the project's progress.
-1. Read `tasks.yaml`, `CHANGELOG.md`, and recent `journal/` entries.
-2. Analyze uncommitted changes and conversation context.
-3. Use the task tool (`start`, `cancel`, `archive`) to update task statuses as appropriate.
-4. If a task requires a linked plan, use the task tool's `attach-plan` action.
-5. Verify the file after the update.
-
----
-**Note:** If the intent is unclear, ask for clarification. Default to "Report" if no action is specified.
+### Constraints
+- NO subagent delegation - do the work directly
+- NO branch management - work on current branch
+- One task at a time