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/decompose/SKILL.md

@@ -2,12 +2,14 @@
 name: decompose
 description: |
   Decompose planned components into atomic implementable tasks with bootstrap structure plan.
-  3-step workflow: bootstrap structure plan, task decomposition with inline Jira ticket creation, and cross-task verification.
+  4-step workflow: bootstrap structure plan, component task decomposition, integration test task decomposition, and cross-task verification.
   Supports full decomposition (_docs/ structure) and single component mode.
   Trigger phrases:
   - "decompose", "decompose features", "feature decomposition"
   - "task decomposition", "break down components"
   - "prepare for implementation"
+category: build
+tags: [decomposition, tasks, dependencies, jira, implementation-prep]
 disable-model-invocation: true
 ---
 
@@ -33,7 +35,7 @@ Determine the operating mode based on invocation before any other logic runs.
 - PLANS_DIR: `_docs/02_plans/`
 - TASKS_DIR: `_docs/02_tasks/`
 - Reads from: `_docs/00_problem/`, `_docs/01_solution/`, PLANS_DIR
-- Runs Step 1 (bootstrap) + Step 2 (all components) + Step 3 (cross-verification)
+- Runs Step 1 (bootstrap) + Step 2 (all components) + Step 3 (integration tests) + Step 4 (cross-verification)
 
 **Single component mode** (provided file is within `_docs/02_plans/` and inside a `components/` subdirectory):
 - PLANS_DIR: `_docs/02_plans/`
@@ -59,6 +61,7 @@ Announce the detected mode and resolved paths to the user before proceeding.
 | `PLANS_DIR/architecture.md` | Architecture from plan skill |
 | `PLANS_DIR/system-flows.md` | System flows from plan skill |
 | `PLANS_DIR/components/[##]_[name]/description.md` | Component specs from plan skill |
+| `PLANS_DIR/integration_tests/` | Integration test specs from plan skill |
 
 **Single component mode:**
 
@@ -97,8 +100,9 @@ TASKS_DIR/
 | Step | Save immediately after | Filename |
 |------|------------------------|----------|
 | Step 1 | Bootstrap structure plan complete + Jira ticket created + file renamed | `[JIRA-ID]_initial_structure.md` |
-| Step 2 | Each task decomposed + Jira ticket created + file renamed | `[JIRA-ID]_[short_name].md` |
-| Step 3 | Cross-task verification complete | `_dependencies_table.md` |
+| Step 2 | Each component task decomposed + Jira ticket created + file renamed | `[JIRA-ID]_[short_name].md` |
+| Step 3 | Each integration test task decomposed + Jira ticket created + file renamed | `[JIRA-ID]_[short_name].md` |
+| Step 4 | Cross-task verification complete | `_dependencies_table.md` |
 
 ### Resumability
 
@@ -176,7 +180,35 @@ For each component (or the single provided component):
 
 ---
 
-### Step 3: Cross-Task Verification (default mode only)
+### Step 3: Integration Test Task Decomposition (default mode only)
+
+**Role**: Professional Quality Assurance Engineer
+**Goal**: Decompose integration test specs into atomic, implementable task specs
+**Constraints**: Behavioral specs only — describe what, not how. No test code.
+
+**Numbering**: Continue sequential numbering from where Step 2 left off.
+
+1. Read all test specs from `PLANS_DIR/integration_tests/` (functional_tests.md, non_functional_tests.md)
+2. Group related test scenarios into atomic tasks (e.g., one task per test category or per component under test)
+3. Each task should reference the specific test scenarios it implements and the environment/test_data specs
+4. Dependencies: integration test tasks depend on the component implementation tasks they exercise
+5. Write each task spec using `templates/task.md`
+6. Estimate complexity per task (1, 2, 3, 5 points); no task should exceed 5 points — split if it does
+7. Note task dependencies (referencing Jira IDs of already-created dependency tasks)
+8. **Immediately after writing each task file**: create a Jira ticket under the "Integration Tests" epic, write the Jira ticket ID and Epic ID back into the task header, then rename the file from `[##]_[short_name].md` to `[JIRA-ID]_[short_name].md`.
+
+**Self-verification**:
+- [ ] Every functional test scenario from `integration_tests/functional_tests.md` is covered by a task
+- [ ] Every non-functional test scenario from `integration_tests/non_functional_tests.md` is covered by a task
+- [ ] No task exceeds 5 complexity points
+- [ ] Dependencies correctly reference the component tasks being tested
+- [ ] Every task has a Jira ticket linked to the "Integration Tests" epic
+
+**Save action**: Write each `[##]_[short_name].md` (temporary numeric name), create Jira ticket inline, then rename to `[JIRA-ID]_[short_name].md`.
+
+---
+
+### Step 4: Cross-Task Verification (default mode only)
 
 **Role**: Professional software architect and analyst
 **Goal**: Verify task consistency and produce `_dependencies_table.md`
@@ -227,13 +259,14 @@ For each component (or the single provided component):
 
 ```
 ┌────────────────────────────────────────────────────────────────┐
-│          Task Decomposition (3-Step Method)                     │
+│          Task Decomposition (4-Step Method)                     │
 ├────────────────────────────────────────────────────────────────┤
 │ CONTEXT: Resolve mode (default / single component)             │
 │ 1. Bootstrap Structure  → [JIRA-ID]_initial_structure.md       │
 │    [BLOCKING: user confirms structure]                         │
-│ 2. Task Decompose       → [JIRA-ID]_[short_name].md each      │
-│ 3. Cross-Verification   → _dependencies_table.md              │
+│ 2. Component Tasks      → [JIRA-ID]_[short_name].md each      │
+│ 3. Integration Tests    → [JIRA-ID]_[short_name].md each      │
+│ 4. Cross-Verification   → _dependencies_table.md              │
 │    [BLOCKING: user confirms dependencies]                      │
 ├────────────────────────────────────────────────────────────────┤
 │ Principles: Atomic tasks · Behavioral specs · Flat structure   │