Task: Extended Configuration Wizard

Description

Extend the existing /oden:init wizard to configure new productivity features during project setup. Add configuration options for bug resolution preferences, pipeline stages, export formats, dashboard settings, and team collaboration features.

Functional Requirements

• Feature Selection: Configure which new productivity features to enable
• Bug Resolution Preferences: Choose auto-fix vs manual approval settings
• Pipeline Configuration: Set default stages and specialized agents
• Export Preferences: Configure client branding and default formats
• Dashboard Settings: Auto-start preferences and monitoring options
• Team Configuration: Shared settings via .oden-config.json

Technical Implementation

Files to Modify:

• .claude/commands/oden/init.md - Enhanced wizard definition
• lib/commands/init.js - Extended configuration logic
• lib/init/feature-config.js - New feature configuration system
• lib/init/team-config.js - Team configuration sharing logic
• templates/.oden-config.json - Configuration file template

Architecture:

1. Wizard Extension: Add new configuration steps to existing flow
2. Feature Detection: Determine which features are available/relevant
3. Configuration Generation: Create comprehensive .oden-config.json
4. Team Integration: Support git-committable team configurations
5. Validation: Ensure configuration consistency and validity

Acceptance Criteria

Core Functionality:

• Enhanced /oden:init includes new feature configuration steps
• Wizard asks about productivity feature preferences
• Generates comprehensive .oden-config.json with all settings
• Maintains backward compatibility with existing init workflow
• Supports both individual and team configuration modes

Configuration Options:

Bug Resolution Preferences:

• Auto-fix vs manual approval for common issues
• Backup creation before applying fixes
• Notification preferences for fix attempts
• Rollback policy configuration

Pipeline and Agent Settings:

• Default pipeline stages (pre-commit, pre-PR, pre-deploy)
• Enabled specialized agents (security, performance, accessibility)
• Agent execution timeouts and resource limits
• Report format and notification preferences

Export and Documentation:

• Default export formats (PDF, Notion, Confluence, DOCX)
• Client branding settings (logo, colors, company name)
• Template preferences for different document types
• Auto-sync preferences for external platforms

Dashboard and Monitoring:

• Auto-start dashboard with /oden:work sessions
• Default port and network settings
• Performance metric collection preferences
• Historical data retention policies

Team and Collaboration:

• Team name and member identification
• Shared vs individual configuration preferences
• Git integration for configuration sharing
• Conflict resolution strategies

Configuration File Structure:

{
  "project": {
    "name": "project-name",
    "type": "web-app",
    "team": "team-name"
  },
  "features": {
    "bug_diagnosis": {
      "enabled": true,
      "auto_fix": false,
      "backup_before_fix": true
    },
    "brainstorming": {
      "enabled": true,
      "question_depth": "enhanced"
    },
    "pipeline": {
      "enabled": true,
      "stages": ["pre-commit", "pre-PR"],
      "agents": ["security", "performance"]
    },
    "dashboard": {
      "enabled": true,
      "auto_start": true,
      "port": 3333
    },
    "export": {
      "enabled": true,
      "default_format": "pdf",
      "branding": {
        "company": "Acme Corp",
        "logo_path": "./assets/logo.png"
      }
    }
  },
  "team": {
    "shared_config": true,
    "conflict_resolution": "prompt"
  }
}

Team Configuration:

• Supports team-wide configuration sharing via Git
• Handles configuration conflicts gracefully
• Allows individual overrides of team settings
• Provides migration path for existing projects

Dependencies

• Internal: Existing /oden:init wizard infrastructure
• External: Git for team configuration sharing
• Integration: All new productivity features for configuration validation

Implementation Notes

• Add configuration steps incrementally to avoid overwhelming users
• Provide sensible defaults for all new options
• Implement configuration validation to prevent invalid combinations
• Create migration utilities for existing projects
• Document team configuration sharing workflows

Configuration Wizard Flow

New Steps Addition:

1. Feature Selection: "Which productivity features do you want to enable?"
2. Bug Resolution: "How should bug fixes be handled?" (auto/manual/prompt)
3. Agent Pipeline: "Which code quality agents should run?" (multi-select)
4. Export Setup: "Configure documentation export preferences"
5. Team Settings: "Is this a team project?" (individual/team configuration)

User Experience:

• Clear explanations of what each feature does
• Examples of how settings affect workflow
• Option to skip advanced configuration
• Preview of generated configuration file
• Validation feedback for configuration conflicts

Risks

• Medium: Configuration complexity might overwhelm new users
• Medium: Team configuration conflicts could cause confusion
• Low: Integration with existing projects might be challenging

Mitigation Strategies

• Progressive disclosure: basic setup first, advanced options later
• Comprehensive documentation and examples
• Clear conflict resolution UI and workflows
• Extensive testing with various project types and team structures