Claude-Code-Workflow/.claude/workflows/ANALYSIS_RESULTS.md

# Analysis Results Documentation

## Metadata
- **Generated by**: `/workflow:plan` command
- **Session**: `WFS-[session-id]`
- **Task Context**: `[task-description]`
- **Analysis Date**: `[timestamp]`

## 1. Verified Project Assets

### Confirmed Documentation Files
```bash
# Verified file existence with full paths:
✓ [/absolute/path/to/CLAUDE.md] - [file size] - Contains: [key sections found]
✓ [/absolute/path/to/README.md] - [file size] - Contains: [technical info]
✓ [/absolute/path/to/package.json] - [file size] - Dependencies: [list]
```

### Confirmed Technical Stack
- **Package Manager**: [npm/yarn/pnpm] (confirmed via `[specific file path]`)
- **Framework**: [React/Vue/Angular/etc] (version: [x.x.x])
- **Build Tool**: [webpack/vite/etc] (config: `[config file path]`)
- **Test Framework**: [jest/vitest/etc] (config: `[config file path]`)

## 2. Verified Code Structure

### Confirmed Directory Structure
```
[project-root]/
├── [actual-folder-name]/        # [purpose - verified]
│   ├── [actual-file.ext]       # [size] [last-modified]
│   └── [actual-file.ext]       # [size] [last-modified]
└── [actual-folder-name]/        # [purpose - verified]
    ├── [actual-file.ext]       # [size] [last-modified]
    └── [actual-file.ext]       # [size] [last-modified]
```

### Confirmed Key Modules
- **Module 1**: `[/absolute/path/to/module]`
  - **Entry Point**: `[actual-file.js]` (exports: [verified-exports])
  - **Key Methods**: `[method1()]`, `[method2()]` (line numbers: [X-Y])
  - **Dependencies**: `[import statements verified]`

- **Module 2**: `[/absolute/path/to/module]`
  - **Entry Point**: `[actual-file.js]` (exports: [verified-exports])
  - **Key Methods**: `[method1()]`, `[method2()]` (line numbers: [X-Y])
  - **Dependencies**: `[import statements verified]`

## 3. Confirmed Implementation Standards

### Verified Coding Patterns
- **Naming Convention**: [verified pattern from actual files]
  - Files: `[example1.js]`, `[example2.js]` (pattern: [pattern])
  - Functions: `[actualFunction()]` from `[file:line]`
  - Classes: `[ActualClass]` from `[file:line]`

### Confirmed Build Commands
```bash
# Verified commands (tested successfully):
✓ [npm run build] - Output: [build result]
✓ [npm run test] - Framework: [test framework found]
✓ [npm run lint] - Tool: [linter found]
```

## 4. Task Decomposition Results

### Task Count Determination
- **Identified Tasks**: [exact number] (based on functional boundaries)
- **Structure**: [Flat ≤5 | Hierarchical 6-10 | Re-scope >10]
- **Merge Rationale**: [specific reasons for combining related files]

### Confirmed Task Breakdown
- **IMPL-001**: `[Specific functional description]`
  - **Target Files**: `[/absolute/path/file1.js]`, `[/absolute/path/file2.js]` (verified)
  - **Key Methods to Implement**: `[method1()]`, `[method2()]` (signatures defined)
  - **Size**: [X files, ~Y lines] (measured from similar existing code)
  - **Dependencies**: Uses `[existingModule.method()]` from `[verified-path]`

- **IMPL-002**: `[Specific functional description]`
  - **Target Files**: `[/absolute/path/file3.js]`, `[/absolute/path/file4.js]` (verified)
  - **Key Methods to Implement**: `[method3()]`, `[method4()]` (signatures defined)
  - **Size**: [X files, ~Y lines] (measured from similar existing code)
  - **Dependencies**: Uses `[existingModule.method()]` from `[verified-path]`

### Verified Dependency Chain
```bash
# Confirmed execution order (based on actual imports):
IMPL-001 → Uses: [existing-file:method]
IMPL-002 → Depends: IMPL-001.[method] → Uses: [existing-file:method]
```

## 5. Implementation Execution Plan

### Confirmed Integration Points
- **Existing Entry Points**:
  - `[actual-file.js:line]` exports `[verified-method]`
  - `[actual-config.json]` contains `[verified-setting]`
- **Integration Methods**:
  - Hook into `[existing-method()]` at `[file:line]`
  - Extend `[ExistingClass]` from `[file:line]`

### Validated Commands
```bash
# Commands verified to work in current environment:
✓ [exact build command] - Tested: [timestamp]
✓ [exact test command] - Tested: [timestamp]
✓ [exact lint command] - Tested: [timestamp]
```

## 6. Success Validation Criteria

### Testable Outcomes
- **IMPL-001 Success**:
  - `[specific test command]` passes
  - `[integration point]` correctly calls `[new method]`
  - No regression in `[existing test suite]`

- **IMPL-002 Success**:
  - `[specific test command]` passes
  - Feature accessible via `[verified UI path]`
  - Performance: `[measurable criteria]`

### Quality Gates
- **Code Standards**: Must pass `[verified lint command]`
- **Test Coverage**: Maintain `[current coverage %]` (measured by `[tool]`)
- **Build**: Must complete `[verified build command]` without errors

---

## Template Instructions

**CRITICAL**: Every bracketed item MUST be filled with verified, existing information:
- File paths must be confirmed with `ls` or `find`
- Method names must be found in actual source code
- Commands must be tested and work
- Line numbers should reference actual code locations
- Dependencies must trace to real imports/requires

**Verification Required Before Use**:
1. All file paths exist and are readable
2. All referenced methods/classes exist in specified locations
3. All commands execute successfully
4. All integration points are actual, not assumed