fix: Adjust reasoning effort level to medium in developer agent and update tester model reference

2026-08-28 22:09:10 -04:00
parent ef30931b20
commit ad08e6d9f5
3 changed files with 6 additions and 5 deletions
@@ -7,7 +7,7 @@ description: "Executes the full dev-to-docs pipeline: Developer -> Tester -> Wri

 I orchestrate a sequential feature implementation and verification pipeline:

-1. **Architect**: Explores codebase, asks clarifying questions, and drafts the spec. \*_Waits for user approval before handoff._
+1. **Architect**: Explores codebase, asks clarifying questions, and drafts the spec. *Waits for user approval before handoff.*
 2. **Developer**: Implements the feature based on the spec.
 3. **Tester**: Runs full unit test suites; repairs failures if found.
 4. **Writer**: After updating README and API docs, review `docs/tech_debt_and_optimizations.md` for formatting consistency and ensure no duplicate entries exist.
@@ -15,10 +15,11 @@ I orchestrate a sequential feature implementation and verification pipeline:
 ## Execution Rules

 - **Architect Gate**: Stop after Phase 3 and wait for user approval on the spec before calling `@developer`.
+- **Tester Repair Limit**: Allow `@tester` a maximum of 2 auto-repair attempts for failing test suites. If tests still fail after 2 attempts, hand the error context back to `@developer` to fix the underlying implementation.
 - Stop and ask the user for clarification if any step fails or is ambiguous.
 - Use `@` mentions to trigger subagents sequentially.
- Pass context from each completed stage to the next stage
+- Pass context from each completed stage to the next stage.

 ## When to use me

-Invoke me when you are ready to begin a new feature/fix or when the Architect has finished a specification.
+Invoke me when you are ready to begin a new feature/fix or when the Architect has finished a specification.