Remove UAV frame material documentation and update README with detailed project requirements. Refactor skills documentation to clarify modes of operation and enhance input specifications. Delete unused E2E test infrastructure template.

.cursor/skills/decompose/SKILL.md

@@ -3,7 +3,7 @@ name: decompose
 description: |
   Decompose planned components into atomic implementable features with bootstrap structure plan.
   4-step workflow: bootstrap structure plan, feature decomposition, cross-component verification, and Jira task creation.
-  Supports project mode (_docs/ structure), single component mode, and standalone mode (@file.md).
+  Supports full decomposition (_docs/ structure) and single component mode.
   Trigger phrases:
   - "decompose", "decompose features", "feature decomposition"
   - "task decomposition", "break down components"
@@ -27,7 +27,7 @@ Decompose planned components into atomic, implementable feature specs with a boo
 
 Determine the operating mode based on invocation before any other logic runs.
 
-**Full project mode** (no explicit input file provided):
+**Default** (no explicit input file provided):
 - PLANS_DIR: `_docs/02_plans/`
 - TASKS_DIR: `_docs/02_tasks/`
 - Reads from: `_docs/00_problem/`, `_docs/01_solution/`, PLANS_DIR
@@ -36,36 +36,28 @@ Determine the operating mode based on invocation before any other logic runs.
 **Single component mode** (provided file is within `_docs/02_plans/` and inside a `components/` subdirectory):
 - PLANS_DIR: `_docs/02_plans/`
 - TASKS_DIR: `_docs/02_tasks/`
-- Derive `<topic>`, component number, and component name from the file path
+- Derive component number and component name from the file path
 - Ask user for the parent Epic ID
 - Runs Step 2 (that component only) + Step 4 (Jira)
 - Overwrites existing feature files in that component's TASKS_DIR subdirectory
 
-**Standalone mode** (explicit input file provided, not within `_docs/02_plans/`):
-- INPUT_FILE: the provided file (treated as a component spec)
-- Derive `<topic>` from the input filename (without extension)
-- TASKS_DIR: `_standalone/<topic>/tasks/`
-- Guardrails relaxed: only INPUT_FILE must exist and be non-empty
-- Ask user for the parent Epic ID
-- Runs Step 2 (that component only) + Step 4 (Jira)
-
 Announce the detected mode and resolved paths to the user before proceeding.
 
 ## Input Specification
 
 ### Required Files
 
-**Full project mode:**
+**Default:**
 
 | File | Purpose |
 |------|---------|
 | `_docs/00_problem/problem.md` | Problem description and context |
-| `_docs/00_problem/restrictions.md` | Constraints and limitations (if available) |
-| `_docs/00_problem/acceptance_criteria.md` | Measurable acceptance criteria (if available) |
+| `_docs/00_problem/restrictions.md` | Constraints and limitations |
+| `_docs/00_problem/acceptance_criteria.md` | Measurable acceptance criteria |
 | `_docs/01_solution/solution.md` | Finalized solution |
-| `PLANS_DIR/<topic>/architecture.md` | Architecture from plan skill |
-| `PLANS_DIR/<topic>/system-flows.md` | System flows from plan skill |
-| `PLANS_DIR/<topic>/components/[##]_[name]/description.md` | Component specs from plan skill |
+| `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 |
 
 **Single component mode:**
 
@@ -74,34 +66,23 @@ 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 |
 
-**Standalone mode:**
-
-| File | Purpose |
-|------|---------|
-| INPUT_FILE (the provided file) | Component spec to decompose |
-
 ### Prerequisite Checks (BLOCKING)
 
-**Full project mode:**
-1. At least one `<topic>/` directory exists under PLANS_DIR with `architecture.md` and `components/` — **STOP if missing**
-2. If multiple topics exist, ask user which one to decompose
-3. Create TASKS_DIR if it does not exist
-4. If `TASKS_DIR/<topic>/` already exists, ask user: **resume from last checkpoint or start fresh?**
+**Default:**
+1. PLANS_DIR contains `architecture.md` and `components/` — **STOP if missing**
+2. Create TASKS_DIR if it does not exist
+3. If TASKS_DIR already contains artifacts, ask user: **resume from last checkpoint or start fresh?**
 
 **Single component mode:**
 1. The provided component file exists and is non-empty — **STOP if missing**
 2. Create the component's subdirectory under TASKS_DIR if it does not exist
 
-**Standalone mode:**
-1. INPUT_FILE exists and is non-empty — **STOP if missing**
-2. Create TASKS_DIR if it does not exist
-
 ## Artifact Management
 
 ### Directory Structure
 
 ```
-TASKS_DIR/<topic>/
+TASKS_DIR/
 ├── initial_structure.md                        (Step 1, full mode only)
 ├── cross_dependencies.md                       (Step 3, full mode only)
 ├── SUMMARY.md                                  (final)
@@ -126,7 +107,7 @@ TASKS_DIR/<topic>/
 
 ### Resumability
 
-If `TASKS_DIR/<topic>/` already contains artifacts:
+If TASKS_DIR already contains artifacts:
 
 1. List existing files and match them to the save timing table
 2. Identify the last completed component based on which feature files exist
@@ -139,7 +120,7 @@ At the start of execution, create a TodoWrite with all applicable steps. Update
 
 ## Workflow
 
-### Step 1: Bootstrap Structure Plan (full project mode only)
+### Step 1: Bootstrap Structure Plan (default mode only)
 
 **Role**: Professional software architect
 **Goal**: Produce `initial_structure.md` describing the project skeleton for implementation
@@ -191,7 +172,7 @@ For each component (or the single provided component):
 
 ---
 
-### Step 3: Cross-Component Verification (full project mode only)
+### Step 3: Cross-Component Verification (default mode only)
 
 **Role**: Professional software architect and analyst
 **Goal**: Verify feature consistency across all components
@@ -223,8 +204,7 @@ For each component (or the single provided component):
 1. For each feature spec, create a Jira task following the parsing rules and field mapping from `gen_jira_task_and_branch.md` (skip branch creation and file renaming — those happen during implementation)
 2. In full mode: search Jira for epics matching component names/labels to find parent epic IDs
 3. In single component mode: use the Epic ID obtained during context resolution
-4. In standalone mode: use the Epic ID obtained during context resolution
-5. Do NOT create git branches or rename files — that happens during implementation
+4. Do NOT create git branches or rename files — that happens during implementation
 
 **Self-verification**:
 - [ ] Every feature has a corresponding Jira task
@@ -265,7 +245,7 @@ After all steps complete, write `SUMMARY.md` using `templates/summary.md` as str
 ┌────────────────────────────────────────────────────────────────┐
 │            Feature Decomposition (4-Step Method)               │
 ├────────────────────────────────────────────────────────────────┤
-│ CONTEXT: Resolve mode (full / single component / standalone)   │
+│ CONTEXT: Resolve mode (default / single component)             │
 │ 1. Bootstrap Structure  → initial_structure.md (full only)     │
 │    [BLOCKING: user confirms structure]                         │
 │ 2. Feature Decompose    → [##]_[name]/[##].[##]_feature_*     │