Add detailed file index and enhance skill documentation for autopilot, decompose, deploy, plan, and research skills. Introduce tests-only mode in decompose skill, clarify required files for deploy and plan skills, and improve prerequisite checks across skills for better user guidance and workflow efficiency.

2026-04-22 09:06:31 +00:00 · 2026-03-22 16:15:49 +02:00
parent 60ebe686ff
commit 3165a88f0b
60 changed files with 6324 additions and 1550 deletions
@@ -3,11 +3,12 @@ name: decompose
 description: |
  Decompose planned components into atomic implementable tasks with bootstrap structure plan.
  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.
+  Supports full decomposition (_docs/ structure), single component mode, and tests-only mode.
  Trigger phrases:
  - "decompose", "decompose features", "feature decomposition"
  - "task decomposition", "break down components"
  - "prepare for implementation"
+  - "decompose tests", "test decomposition"
 category: build
 tags: [decomposition, tasks, dependencies, jira, implementation-prep]
 disable-model-invocation: true
@@ -44,6 +45,14 @@ Determine the operating mode based on invocation before any other logic runs.
 - Ask user for the parent Epic ID
 - Runs Step 2 (that component only, appending to existing task numbering)

+**Tests-only mode** (provided file/directory is within `integration_tests/`, or `DOCUMENT_DIR/integration_tests/` exists and input explicitly requests test decomposition):
+- DOCUMENT_DIR: `_docs/02_document/`
+- TASKS_DIR: `_docs/02_tasks/`
+- TESTS_DIR: `DOCUMENT_DIR/integration_tests/`
+- Reads from: `_docs/00_problem/`, `_docs/01_solution/`, TESTS_DIR
+- Runs Step 1t (test infrastructure bootstrap) + Step 3 (integration test decomposition) + Step 4 (cross-verification against test coverage)
+- Skips Step 1 (project bootstrap) and Step 2 (component decomposition) — the codebase already exists
+
 Announce the detected mode and resolved paths to the user before proceeding.

 ## Input Specification
@@ -70,6 +79,19 @@ Announce the detected mode and resolved paths to the user before proceeding.
 | The provided component `description.md` | Component spec to decompose |
 | Corresponding `tests.md` in the same directory (if available) | Test specs for context |

+**Tests-only mode:**
+
+| File | Purpose |
+|------|---------|
+| `TESTS_DIR/environment.md` | Test environment specification (Docker services, networks, volumes) |
+| `TESTS_DIR/test_data.md` | Test data management (seed data, mocks, isolation) |
+| `TESTS_DIR/functional_tests.md` | Functional test scenarios (positive + negative) |
+| `TESTS_DIR/non_functional_tests.md` | Non-functional test scenarios (perf, resilience, security, limits) |
+| `TESTS_DIR/traceability_matrix.md` | AC/restriction coverage mapping |
+| `_docs/00_problem/problem.md` | Problem context |
+| `_docs/00_problem/restrictions.md` | Constraints for test design |
+| `_docs/00_problem/acceptance_criteria.md` | Acceptance criteria being verified |
+
 ### Prerequisite Checks (BLOCKING)

 **Default:**
@@ -80,6 +102,12 @@ Announce the detected mode and resolved paths to the user before proceeding.
 **Single component mode:**
 1. The provided component file exists and is non-empty — **STOP if missing**

+**Tests-only mode:**
+1. `TESTS_DIR/functional_tests.md` exists and is non-empty — **STOP if missing**
+2. `TESTS_DIR/environment.md` exists — **STOP if missing**
+3. Create TASKS_DIR if it does not exist
+4. If TASKS_DIR already contains task files, ask user: **resume from last checkpoint or start fresh?**
+
 ## Artifact Management

 ### Directory Structure
@@ -100,6 +128,7 @@ TASKS_DIR/
 | Step | Save immediately after | Filename |
 |------|------------------------|----------|
 | Step 1 | Bootstrap structure plan complete + Jira ticket created + file renamed | `[JIRA-ID]_initial_structure.md` |
+| Step 1t | Test infrastructure bootstrap complete + Jira ticket created + file renamed | `[JIRA-ID]_test_infrastructure.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` |
@@ -118,6 +147,42 @@ At the start of execution, create a TodoWrite with all applicable steps. Update

 ## Workflow

+### Step 1t: Test Infrastructure Bootstrap (tests-only mode only)
+
+**Role**: Professional Quality Assurance Engineer
+**Goal**: Produce `01_test_infrastructure.md` — the first task describing the test project scaffold
+**Constraints**: This is a plan document, not code. The `/implement` skill executes it.
+
+1. Read `TESTS_DIR/environment.md` and `TESTS_DIR/test_data.md`
+2. Read problem.md, restrictions.md, acceptance_criteria.md for domain context
+3. Document the test infrastructure plan using `templates/test-infrastructure-task.md`
+
+The test infrastructure bootstrap must include:
+- Test project folder layout (`e2e/` directory structure)
+- Mock/stub service definitions for each external dependency
+- `docker-compose.test.yml` structure from environment.md
+- Test runner configuration (framework, plugins, fixtures)
+- Test data fixture setup from test_data.md seed data sets
+- Test reporting configuration (format, output path)
+- Data isolation strategy
+
+**Self-verification**:
+- [ ] Every external dependency from environment.md has a mock service defined
+- [ ] Docker Compose structure covers all services from environment.md
+- [ ] Test data fixtures cover all seed data sets from test_data.md
+- [ ] Test runner configuration matches the consumer app tech stack from environment.md
+- [ ] Data isolation strategy is defined
+
+**Save action**: Write `01_test_infrastructure.md` (temporary numeric name)
+
+**Jira action**: Create a Jira ticket for this task under the "Integration Tests" epic. Write the Jira ticket ID and Epic ID back into the task header.
+
+**Rename action**: Rename the file from `01_test_infrastructure.md` to `[JIRA-ID]_test_infrastructure.md`. Update the **Task** field inside the file to match the new filename.
+
+**BLOCKING**: Present test infrastructure plan summary to user. Do NOT proceed until user confirms.
+
+---
+
 ### Step 1: Bootstrap Structure Plan (default mode only)

 **Role**: Professional software architect
@@ -166,7 +231,7 @@ The bootstrap structure plan must include:

 ---

-### Step 2: Task Decomposition (all modes)
+### Step 2: Task Decomposition (default and single component modes)

 **Role**: Professional software architect
 **Goal**: Decompose each component into atomic, implementable task specs — numbered sequentially starting from 02
@@ -200,18 +265,22 @@ For each component (or the single provided component):

 ---

-### Step 3: Integration Test Task Decomposition (default mode only)
+### Step 3: Integration Test Task Decomposition (default and tests-only modes)

 **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.
+**Numbering**:
+- In default mode: continue sequential numbering from where Step 2 left off.
+- In tests-only mode: start from 02 (01 is the test infrastructure bootstrap from Step 1t).

 1. Read all test specs from `DOCUMENT_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
+4. Dependencies:
+   - In default mode: integration test tasks depend on the component implementation tasks they exercise
+   - In tests-only mode: integration test tasks depend on the test infrastructure bootstrap task (Step 1t)
 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)
@@ -221,31 +290,41 @@ For each component (or the single provided component):
 - [ ] 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
+- [ ] Dependencies correctly reference the dependency tasks (component tasks in default mode, test infrastructure in tests-only mode)
 - [ ] 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)
+### Step 4: Cross-Task Verification (default and tests-only modes)

 **Role**: Professional software architect and analyst
 **Goal**: Verify task consistency and produce `_dependencies_table.md`
 **Constraints**: Review step — fix gaps found, do not add new tasks

 1. Verify task dependencies across all tasks are consistent
-2. Check no gaps: every interface in architecture.md has tasks covering it
-3. Check no overlaps: tasks don't duplicate work across components
+2. Check no gaps:
+   - In default mode: every interface in architecture.md has tasks covering it
+   - In tests-only mode: every test scenario in `traceability_matrix.md` is covered by a task
+3. Check no overlaps: tasks don't duplicate work
 4. Check no circular dependencies in the task graph
 5. Produce `_dependencies_table.md` using `templates/dependencies-table.md`

 **Self-verification**:
+
+Default mode:
 - [ ] Every architecture interface is covered by at least one task
 - [ ] No circular dependencies in the task graph
 - [ ] Cross-component dependencies are explicitly noted in affected task specs
 - [ ] `_dependencies_table.md` contains every task with correct dependencies

+Tests-only mode:
+- [ ] Every test scenario from traceability_matrix.md "Covered" entries has a corresponding task
+- [ ] No circular dependencies in the task graph
+- [ ] Test task dependencies reference the test infrastructure bootstrap
+- [ ] `_dependencies_table.md` contains every task with correct dependencies
+
 **Save action**: Write `_dependencies_table.md`

 **BLOCKING**: Present dependency summary to user. Do NOT proceed until user confirms.
@@ -279,15 +358,27 @@ For each component (or the single provided component):

 ```
 ┌────────────────────────────────────────────────────────────────┐
-│          Task Decomposition (4-Step Method)                     │
+│          Task Decomposition (Multi-Mode)                        │
 ├────────────────────────────────────────────────────────────────┤
-│ CONTEXT: Resolve mode (default / single component)             │
-│ 1. Bootstrap Structure  → [JIRA-ID]_initial_structure.md       │
-│    [BLOCKING: user confirms structure]                         │
-│ 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]                      │
+│ CONTEXT: Resolve mode (default / single component / tests-only)│
+│                                                                │
+│ DEFAULT MODE:                                                   │
+│  1.  Bootstrap Structure  → [JIRA-ID]_initial_structure.md     │
+│      [BLOCKING: user confirms structure]                       │
+│  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]                    │
+│                                                                │
+│ TESTS-ONLY MODE:                                                │
+│  1t. Test Infrastructure  → [JIRA-ID]_test_infrastructure.md   │
+│      [BLOCKING: user confirms test scaffold]                   │
+│  3.  Integration Tests    → [JIRA-ID]_[short_name].md each    │
+│  4.  Cross-Verification   → _dependencies_table.md            │
+│      [BLOCKING: user confirms dependencies]                    │
+│                                                                │
+│ SINGLE COMPONENT MODE:                                          │
+│  2.  Component Tasks      → [JIRA-ID]_[short_name].md each    │
 ├────────────────────────────────────────────────────────────────┤
 │ Principles: Atomic tasks · Behavioral specs · Flat structure   │
 │   Jira inline · Rename to Jira ID · Save now · Ask don't assume│