Update README to reflect changes in test infrastructure organization and task decomposition workflow. Remove obsolete E2E test templates and clarify input specifications for integration tests. Enhance documentation for planning and implementation phases, including new directory structures and task management processes.

.cursor/skills/implement/SKILL.md

@@ -8,6 +8,8 @@ description: |
   Trigger phrases:
   - "implement", "start implementation", "implement tasks"
   - "run implementers", "execute tasks"
+category: build
+tags: [implementation, orchestration, batching, parallel, code-review]
 disable-model-invocation: true
 ---
 
@@ -71,7 +73,11 @@ For each task in the batch:
 - Determine: files OWNED (exclusive write), files READ-ONLY (shared interfaces, types), files FORBIDDEN (other agents' owned files)
 - If two tasks in the same batch would modify the same file, schedule them sequentially instead of in parallel
 
-### 5. Launch Implementer Subagents
+### 5. Update Jira Status → In Progress
+
+For each task in the batch, transition its Jira ticket status to **In Progress** via Jira MCP before launching the implementer.
+
+### 6. Launch Implementer Subagents
 
 For each task in the batch, launch an `implementer` subagent with:
 - Path to the task spec file
@@ -81,39 +87,47 @@ For each task in the batch, launch an `implementer` subagent with:
 
 Launch all subagents immediately — no user confirmation.
 
-### 6. Monitor
+### 7. Monitor
 
 - Wait for all subagents to complete
 - Collect structured status reports from each implementer
 - If any implementer reports "Blocked", log the blocker and continue with others
 
-### 7. Code Review
+### 8. Code Review
 
 - Run `/code-review` skill on the batch's changed files + corresponding task specs
 - The code-review skill produces a verdict: PASS, PASS_WITH_WARNINGS, or FAIL
 
-### 8. Gate
+### 9. Gate
 
 - If verdict is **FAIL**: present findings to user (**BLOCKING**). User must confirm fixes or accept before proceeding.
 - If verdict is **PASS** or **PASS_WITH_WARNINGS**: show findings as info, continue automatically.
 
-### 9. Test
+### 10. Test
 
 - Run the full test suite
 - If failures: report to user with details
 
-### 10. Commit and Push
+### 11. Commit and Push
 
 - After user confirms the batch (explicitly for FAIL, implicitly for PASS/PASS_WITH_WARNINGS):
   - `git add` all changed files from the batch
-  - `git commit` with a batch-level message summarizing what was implemented
+  - `git commit` with a message that includes ALL JIRA-IDs of tasks implemented in the batch, followed by a summary of what was implemented. Format: `[JIRA-ID-1] [JIRA-ID-2] ... Summary of changes`
   - `git push` to the remote branch
 
-### 11. Loop
+### 12. Update Jira Status → In Testing
+
+After the batch is committed and pushed, transition the Jira ticket status of each task in the batch to **In Testing** via Jira MCP.
+
+### 13. Loop
 
 - Go back to step 2 until all tasks are done
 - When all tasks are complete, report final summary
 
+## Batch Report Persistence
+
+After each batch completes, save the batch report to `_docs/03_implementation/batch_[NN]_report.md`. Create the directory if it doesn't exist. When all tasks are complete, produce `_docs/03_implementation/FINAL_implementation_report.md` with a summary of all batches.
+
 ## Batch Report
 
 After each batch, produce a structured report:
@@ -147,6 +161,14 @@ After each batch, produce a structured report:
 | All tasks complete | Report final summary, suggest final commit |
 | `_dependencies_table.md` missing | STOP — run `/decompose` first |
 
+## Recovery
+
+Each batch commit serves as a rollback checkpoint. If recovery is needed:
+
+- **Tests fail after a batch commit**: `git revert <batch-commit-hash>` using the hash from the batch report in `_docs/03_implementation/`
+- **Resuming after interruption**: Read `_docs/03_implementation/batch_*_report.md` files to determine which batches completed, then continue from the next batch
+- **Multiple consecutive batches fail**: Stop and escalate to user with links to batch reports and commit hashes
+
 ## Safety Rules
 
 - Never launch tasks whose dependencies are not yet completed