aidp 0.5.0 → 0.8.0

data/lib/aidp/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Aidp
-  VERSION = "0.5.0"
+  VERSION = "0.8.0"
 end

data/lib/aidp.rb

@@ -1,44 +1,65 @@
 # frozen_string_literal: true
 
 # Core extensions
-require "aidp/core_ext/class_attribute"
+require_relative "aidp/core_ext/class_attribute"
 
 # Shared modules
-require "aidp/version"
-require "aidp/config"
-require "aidp/workspace"
-require "aidp/util"
-require "aidp/cli"
-require "aidp/cli/jobs_command"
-require "aidp/project_detector"
-require "aidp/sync"
-
-# Database
-require "aidp/database_connection"
-
-# Job infrastructure
-require "aidp/job_manager"
-require "aidp/jobs/base_job"
-require "aidp/jobs/provider_execution_job"
+require_relative "aidp/version"
+require_relative "aidp/config"
+require_relative "aidp/util"
+require_relative "aidp/cli"
+require_relative "aidp/cli/jobs_command"
 
 # Providers
-require "aidp/providers/base"
-require "aidp/providers/cursor"
-require "aidp/providers/anthropic"
-require "aidp/providers/gemini"
-require "aidp/providers/macos_ui"
-require "aidp/provider_manager"
-
-# Analyze mode
-require "aidp/analyze/error_handler"
-require "aidp/analyze/parallel_processor"
-require "aidp/analyze/repository_chunker"
-require "aidp/analyze/ruby_maat_integration"
-require "aidp/analyze/runner"
-require "aidp/analyze/steps"
-require "aidp/analyze/progress"
+require_relative "aidp/providers/base"
+require_relative "aidp/providers/cursor"
+require_relative "aidp/providers/anthropic"
+require_relative "aidp/providers/gemini"
+require_relative "aidp/providers/macos_ui"
+# Supervised providers removed - using direct execution model
+require_relative "aidp/provider_manager"
+
+# Simple file-based storage
+require_relative "aidp/storage/json_storage"
+require_relative "aidp/storage/csv_storage"
+require_relative "aidp/storage/file_manager"
+
+# Analyze mode (simplified - file-based storage only)
+require_relative "aidp/analyze/json_file_storage"
+require_relative "aidp/analyze/error_handler"
+require_relative "aidp/analyze/ruby_maat_integration"
+require_relative "aidp/analyze/runner"
+require_relative "aidp/analyze/steps"
+require_relative "aidp/analyze/progress"
+
+# Tree-sitter analysis
+require_relative "aidp/analysis/tree_sitter_grammar_loader"
+require_relative "aidp/analysis/seams"
+require_relative "aidp/analysis/tree_sitter_scan"
+require_relative "aidp/analysis/kb_inspector"
 
 # Execute mode
-require "aidp/execute/steps"
-require "aidp/execute/runner"
-require "aidp/execute/progress"
+require_relative "aidp/execute/steps"
+require_relative "aidp/execute/runner"
+require_relative "aidp/execute/progress"
+
+# Harness mode
+require_relative "aidp/harness/configuration"
+require_relative "aidp/harness/config_schema"
+require_relative "aidp/harness/config_validator"
+require_relative "aidp/harness/config_loader"
+require_relative "aidp/harness/config_manager"
+require_relative "aidp/harness/condition_detector"
+require_relative "aidp/harness/user_interface"
+require_relative "aidp/harness/provider_manager"
+require_relative "aidp/harness/provider_config"
+require_relative "aidp/harness/provider_factory"
+require_relative "aidp/harness/state_manager"
+require_relative "aidp/harness/error_handler"
+require_relative "aidp/harness/status_display"
+require_relative "aidp/harness/runner"
+
+# UI components
+require_relative "aidp/harness/ui/spinner_helper"
+
+# CLI commands

data/templates/ANALYZE/06a_tree_sitter_scan.md

@@ -0,0 +1,217 @@
+# Tree-sitter Static Analysis Template
+
+You are a **Tree-sitter Static Analysis Expert**, specializing in advanced static code analysis using Tree-sitter parsers. Your role is to analyze the codebase using Tree-sitter-powered static analysis, build a comprehensive knowledge base, and provide insights based on Michael Feathers' "Working Effectively with Legacy Code" strategies.
+
+## Your Expertise
+
+- Tree-sitter parser technology and AST analysis
+- Static code analysis and metrics calculation
+- Legacy code refactoring strategies (Feathers' techniques)
+- Seam detection and dependency analysis
+- Code complexity and hotspot identification
+- Test coverage analysis and characterization test recommendations
+
+## Analysis Objectives
+
+1. **Knowledge Base Construction**: Build a comprehensive machine-readable knowledge base of the codebase structure
+2. **Seam Detection**: Identify integration points and dependency injection opportunities using Feathers' strategies
+3. **Hotspot Analysis**: Identify high-change, high-complexity areas that need attention
+4. **Dependency Mapping**: Map import/require relationships and detect cycles
+5. **Test Gap Analysis**: Identify untested public APIs and recommend characterization tests
+6. **Refactoring Opportunities**: Provide specific, actionable refactoring recommendations
+
+## Required Analysis Steps
+
+### 1. Tree-sitter Knowledge Base Generation
+
+Run the Tree-sitter analysis to generate the knowledge base:
+
+```bash
+aidp analyze code --langs ruby,js,ts,py --threads 4
+```
+
+This will generate the following KB files in `.aidp/kb/`:
+
+- `symbols.json` - Classes, modules, methods with metadata
+- `imports.json` - Require/import statements and dependencies
+- `calls.json` - Method call relationships
+- `metrics.json` - Complexity and size metrics
+- `seams.json` - Integration points and dependency injection opportunities
+- `hotspots.json` - High-change, high-complexity areas
+- `tests.json` - Test coverage mapping
+- `cycles.json` - Import/dependency cycles
+
+### 2. Seam Analysis and Feathers' Strategy Application
+
+Analyze the seams data to identify refactoring opportunities:
+
+#### I/O Integration Seams
+
+- **File Operations**: `File.*`, `IO.*`, `Dir.*` calls
+- **Network Operations**: `Net::HTTP.*`, `Socket.*` calls
+- **System Operations**: `Kernel.system`, `Process.*` calls
+- **Database Operations**: `ActiveRecord.*`, `Sequel.*` calls
+
+**Feathers' Recommendations**:
+
+- Extract I/O operations to separate service classes
+- Use dependency injection for external dependencies
+- Create adapter interfaces for external services
+
+#### Global State and Singleton Seams
+
+- **Global Variables**: `$var`, `@@var` usage
+- **Singleton Patterns**: `include Singleton`, `extend Singleton`
+- **Module-level State**: Mutable state in modules
+
+**Feathers' Recommendations**:
+
+- Replace singletons with dependency injection
+- Encapsulate global state in configuration objects
+- Use constructor injection for dependencies
+
+#### Constructor with Work Seams
+
+- **Complex Initialization**: Constructors with significant logic
+- **External Dependencies**: I/O or service calls in constructors
+- **High Complexity**: Constructors with multiple branches
+
+**Feathers' Recommendations**:
+
+- Extract initialization logic to factory methods
+- Use builder pattern for complex object creation
+- Separate construction from initialization
+
+### 3. Hotspot Analysis and Prioritization
+
+Analyze the hotspots data to prioritize refactoring efforts:
+
+#### Hotspot Scoring
+
+- **Change Frequency**: Number of times files have been modified
+- **Complexity**: Cyclomatic complexity and nesting depth
+- **Size**: Lines of code and method count
+- **Dependencies**: Fan-in and fan-out metrics
+
+#### Top 20 Hotspots Analysis
+
+For each hotspot, provide:
+
+- **Rationale**: Why this area is a hotspot
+- **Risk Assessment**: Potential impact of changes
+- **Refactoring Strategy**: Specific Feathers' techniques to apply
+- **Test Strategy**: Characterization test recommendations
+
+### 4. Dependency Cycle Detection
+
+Analyze import cycles and provide breaking strategies:
+
+#### Cycle Types
+
+- **Import Cycles**: Circular require/import dependencies
+- **Call Cycles**: Circular method call dependencies
+- **Inheritance Cycles**: Circular class inheritance
+
+#### Breaking Strategies
+
+- **Dependency Inversion**: Extract interfaces and invert dependencies
+- **Event-Driven Architecture**: Use events to decouple components
+- **Facade Pattern**: Create facades to break direct dependencies
+
+### 5. Test Coverage Analysis
+
+Analyze untested public APIs and recommend characterization tests:
+
+#### Characterization Test Strategy
+
+- **Public API Mapping**: Identify all public methods and classes
+- **Test Coverage**: Map existing tests to public APIs
+- **Gap Analysis**: Identify untested public APIs
+- **Test Recommendations**: Suggest specific characterization tests
+
+#### Test Implementation Guidelines
+
+- **Golden Master Tests**: Capture current behavior before refactoring
+- **Parameterized Tests**: Test with various inputs
+- **Integration Tests**: Test with real dependencies
+- **Mock Tests**: Test with controlled dependencies
+
+## Output Requirements
+
+### 1. Knowledge Base Summary
+
+- Total files analyzed
+- Symbol counts by type (classes, modules, methods)
+- Import/dependency statistics
+- Complexity metrics summary
+
+### 2. Seam Analysis Report
+
+- **I/O Integration Seams**: List with file locations and refactoring suggestions
+- **Global State Seams**: List with specific global usage and encapsulation strategies
+- **Constructor Work Seams**: List with complexity metrics and extraction recommendations
+
+### 3. Hotspot Analysis Report
+
+- **Top 20 Hotspots**: Ranked list with scores and rationale
+- **Refactoring Priorities**: Recommended order for addressing hotspots
+- **Risk Assessment**: Impact analysis for each hotspot
+
+### 4. Dependency Analysis Report
+
+- **Import Graph**: Visualization of file dependencies
+- **Cycle Detection**: List of detected cycles with breaking strategies
+- **Coupling Analysis**: High-coupling areas and decoupling recommendations
+
+### 5. Test Strategy Report
+
+- **Untested APIs**: List of public APIs without tests
+- **Characterization Test Plan**: Specific test recommendations
+- **Test Implementation Guide**: Step-by-step test creation process
+
+### 6. Refactoring Roadmap
+
+- **Phase 1**: Address highest-priority seams and hotspots
+- **Phase 2**: Break dependency cycles
+- **Phase 3**: Implement characterization tests
+- **Phase 4**: Apply systematic refactoring techniques
+
+## Technical Implementation Notes
+
+### Tree-sitter Integration
+
+- Use `aidp analyze code` command to generate KB
+- Leverage `aidp kb show` commands for data inspection
+- Generate graphs with `aidp kb graph` for visualization
+
+### Feathers' Techniques Application
+
+- **Sprout Method**: Extract small methods from large ones
+- **Sprout Class**: Extract new classes for specific responsibilities
+- **Extract Interface**: Create interfaces for dependency injection
+- **Move Method**: Move methods to appropriate classes
+- **Extract Method**: Break down large methods
+
+### Quality Metrics
+
+- **Cyclomatic Complexity**: Target < 10 per method
+- **Lines of Code**: Target < 20 per method
+- **Fan-out**: Target < 7 per method
+- **Nesting Depth**: Target < 4 levels
+
+## Success Criteria
+
+1. **Complete KB Generation**: All source files parsed and analyzed
+2. **Seam Identification**: All integration points identified with specific recommendations
+3. **Hotspot Prioritization**: Top 20 hotspots identified with actionable strategies
+4. **Cycle Detection**: All dependency cycles identified with breaking strategies
+5. **Test Gap Analysis**: All untested public APIs identified with test recommendations
+6. **Refactoring Roadmap**: Prioritized, actionable refactoring plan provided
+
+## Deliverables
+
+1. **Knowledge Base Files**: Complete `.aidp/kb/` directory with all JSON files
+2. **Analysis Report**: Comprehensive markdown report with all findings
+3. **Visualization Files**: Graph files for dependency visualization
+4. **Refactoring Plan**: Detailed, prioritized refactoring roadmap
+5. **Test Strategy**: Specific characterization test recommendations

data/templates/COMMON/AGENT_BASE.md

@@ -20,6 +20,17 @@ This template provides common capabilities and guidelines for AI agents in both
 - **Contextual Relevance**: Ensure recommendations are relevant to the project
 - **Professional Tone**: Maintain a helpful, professional demeanor
 
+### User Interaction Guidelines
+
+#### TUI-Based Interaction
+
+- **Interactive Questions**: Present questions through the harness TUI system for real-time user input
+- **Validation**: Use built-in validation for user responses (required fields, format validation, etc.)
+- **Error Handling**: Provide clear error messages and allow users to correct invalid input
+- **Progress Feedback**: Show progress indicators and status updates during long operations
+- **Rich Interface**: Utilize CLI UI components for beautiful, interactive terminal experience
+- **STDOUT Integration**: Ensure all output flows through the harness system for proper display
+
 ### Quality Standards
 
 - **Accuracy**: Ensure information is correct and up-to-date

data/templates/EXECUTE/00_PRD.md

@@ -4,10 +4,10 @@ You are a product strategist. Produce a **concise, complete PRD**.
 
 ## Important Instructions
 
-- If you need additional information to create a complete PRD, create a file called `PRD_QUESTIONS.md` with specific questions for the user.
-- If `PRD_QUESTIONS.md` already exists, read the existing questions and answers to understand the user's responses.
-- Otherwise, proceed to create the complete PRD document.
-- Only ask for clarifications at this PRD step. For subsequent steps, proceed with available information.
+- If you need additional information to create a complete PRD, present questions interactively through the harness TUI system
+- Users will answer questions directly in the terminal with validation and error handling
+- If you have sufficient information, proceed directly to create the complete PRD document
+- Only ask for clarifications at this PRD step. For subsequent steps, proceed with available information
 
 ## Input
 

data/templates/EXECUTE/02_ARCHITECTURE.md

@@ -5,10 +5,11 @@ and **hexagonal structure**.
 
 ## Important Instructions
 
-- If you need additional information to create a complete architecture, create a file called `ARCH_QUESTIONS.md` with specific questions for the user (see `02A_ARCH_GATE_QUESTIONS.md` for suggested questions).
-- If `ARCH_QUESTIONS.md` already exists, read the existing questions and answers to understand the user's responses.
-- Otherwise, proceed to create the complete architecture document.
-- Only ask for clarifications at this Architecture step. For subsequent steps, proceed with available information.
+- If you need additional information to create a complete architecture, present questions interactively through the harness TUI system
+- Users will answer questions directly in the terminal with validation and error handling
+- See `02A_ARCH_GATE_QUESTIONS.md` for suggested questions to ask
+- If you have sufficient information, proceed directly to create the complete architecture document
+- Only ask for clarifications at this Architecture step. For subsequent steps, proceed with available information
 
 ## Inputs
 

data/templates/EXECUTE/07_TEST_PLAN.md

@@ -9,15 +9,18 @@ You are a test strategist.
 ## Process
 
 - Derive acceptance tests from user stories.
+- Give each test a clear and descriptive title, so that running tests in "documentation" format will create a clear specification of behavior.
 - Define the **test pyramid** (unit, contract, component, e2e) and
   **property-based** tests for core logic.
+- Avoid mocking non-external dependencies unless necessary.
 - Establish coverage & mutation-testing thresholds.
 - Follow Sandi Metz's rules for unit testing.
+- Tests should be written for maximum understandability, maintainability, and reviewability. Assume the reviewer is not familiar with the codebase.
 
 ## Output
 
 - `docs/TestPlan.md`
-- `golden/` fixtures directory plan
+- `spec/fixtures/` fixtures directory plan
 
 ## Regeneration Policy
 

data/templates/EXECUTE/08_TASKS.md

@@ -4,10 +4,10 @@ You are a planner.
 
 ## Important Instructions
 
-- If you need additional information to create a complete task plan, create a file called `TASKS_QUESTIONS.md` with specific questions for the user.
-- If `TASKS_QUESTIONS.md` already exists, read the existing questions and answers to understand the user's responses.
-- Otherwise, proceed to create the complete task plan.
-- Only ask for clarifications at this Tasks step. For subsequent steps, proceed with available information.
+- If you need additional information to create a complete task plan, present questions interactively through the harness TUI system
+- Users will answer questions directly in the terminal with validation and error handling
+- If you have sufficient information, proceed directly to create the complete task plan
+- Only ask for clarifications at this Tasks step. For subsequent steps, proceed with available information
 
 ## Inputs
 

data/templates/EXECUTE/10_IMPLEMENTATION_AGENT.md

@@ -4,10 +4,10 @@ You are a senior engineer writing **implementation guidance** for domain agents.
 
 ## Important Instructions
 
-- If you need additional information to create a complete implementation guide, create a file called `IMPL_QUESTIONS.md` with specific questions for the user.
-- If `IMPL_QUESTIONS.md` already exists, read the existing questions and answers to understand the user's responses.
-- Otherwise, proceed to create the complete implementation guide.
-- Only ask for clarifications at this Implementation step. For subsequent steps, proceed with available information.
+- If you need additional information to create a complete implementation guide, present questions interactively through the harness TUI system
+- Users will answer questions directly in the terminal with validation and error handling
+- If you have sufficient information, proceed directly to create the complete implementation guide
+- Only ask for clarifications at this Implementation step. For subsequent steps, proceed with available information
 
 ## Inputs