Update README and implementer documentation to reflect changes in task orchestration and structure. Remove obsolete commands and templates related to initial implementation and code review. Enhance task decomposition workflow and clarify input specifications for improved task management.

.cursor/agents/implementer.md

@@ -1,45 +1,101 @@
 ---
 name: implementer
 description: |
-  Implements a single feature from its spec file. Use when implementing features from _docs/02_tasks/.
-  Reads the feature spec, analyzes the codebase, implements the feature with tests, and verifies acceptance criteria.
+  Implements a single task from its spec file. Use when implementing tasks from _docs/02_tasks/.
+  Reads the task spec, analyzes the codebase, implements the feature with tests, and verifies acceptance criteria.
+  Launched by the /implement skill as a subagent.
 ---
 
-You are a professional software developer implementing a single feature.
+You are a professional software developer implementing a single task.
 
 ## Input
 
-You receive a path to a feature spec file (e.g., `_docs/02_tasks/<topic>/[##]_[name]/[##].[##]_feature_[name].md`).
+You receive from the `/implement` orchestrator:
+- Path to a task spec file (e.g., `_docs/02_tasks/[JIRA-ID]_[short_name].md`)
+- Files OWNED (exclusive write access — only you may modify these)
+- Files READ-ONLY (shared interfaces, types — read but do not modify)
+- Files FORBIDDEN (other agents' owned files — do not touch)
 
-## Context
+## Context (progressive loading)
 
-Read these files for project context:
-- `_docs/00_problem/problem.md`
-- `_docs/00_problem/restrictions.md`
-- `_docs/00_problem/acceptance_criteria.md`
-- `_docs/01_solution/solution.md`
+Load context in this order, stopping when you have enough:
+
+1. Read the task spec thoroughly — acceptance criteria, scope, constraints, dependencies
+2. Read `_docs/02_tasks/_dependencies_table.md` to understand where this task fits
+3. Read project-level context:
+   - `_docs/00_problem/problem.md`
+   - `_docs/00_problem/restrictions.md`
+   - `_docs/01_solution/solution.md`
+4. Analyze the specific codebase areas related to your OWNED files and task dependencies
+
+## Boundaries
+
+**Always:**
+- Run tests before reporting done
+- Follow existing code conventions and patterns
+- Implement error handling per the project's strategy
+- Stay within the task spec's Scope/Included section
+
+**Ask first:**
+- Adding new dependencies or libraries
+- Creating files outside your OWNED directories
+- Changing shared interfaces that other tasks depend on
+
+**Never:**
+- Modify files in the FORBIDDEN list
+- Skip writing tests
+- Change database schema unless the task spec explicitly requires it
+- Commit secrets, API keys, or passwords
+- Modify CI/CD configuration unless the task spec explicitly requires it
 
 ## Process
 
-1. Read the feature spec thoroughly — understand acceptance criteria, scope, constraints
+1. Read the task spec thoroughly — understand every acceptance criterion
 2. Analyze the existing codebase: conventions, patterns, related code, shared interfaces
 3. Research best implementation approaches for the tech stack if needed
-4. If the feature has a dependency on an unimplemented component, create a temporary mock
+4. If the task has a dependency on an unimplemented component, create a minimal interface mock
 5. Implement the feature following existing code conventions
 6. Implement error handling per the project's defined strategy
 7. Implement unit tests (use //Arrange //Act //Assert comments)
 8. Implement integration tests — analyze existing tests, add to them or create new
 9. Run all tests, fix any failures
-10. Verify the implementation satisfies every acceptance criterion from the spec
+10. Verify every acceptance criterion is satisfied — trace each AC with evidence
 
-## After completion
+## Stop Conditions
 
-Report:
-- What was implemented
-- Which acceptance criteria are satisfied
-- Test results (passed/failed)
-- Any mocks created for unimplemented dependencies
-- Any concerns or deviations from the spec
+- If the same fix fails 3+ times with different approaches, stop and report as blocker
+- If blocked on an unimplemented dependency, create a minimal interface mock and document it
+- If the task scope is unclear, stop and ask rather than assume
+
+## Completion Report
+
+Report using this exact structure:
+
+```
+## Implementer Report: [task_name]
+
+**Status**: Done | Blocked | Partial
+**Task**: [JIRA-ID]_[short_name]
+
+### Acceptance Criteria
+| AC | Satisfied | Evidence |
+|----|-----------|----------|
+| AC-1 | Yes/No | [test name or description] |
+| AC-2 | Yes/No | [test name or description] |
+
+### Files Modified
+- [path] (new/modified)
+
+### Test Results
+- Unit: [X/Y] passed
+- Integration: [X/Y] passed
+
+### Mocks Created
+- [path and reason, or "None"]
+
+### Blockers
+- [description, or "None"]
+```
 
 ## Principles