refactor: remove command registry pattern

1. Remove command registry implementation
2. Update CLI to use direct command instantiation
3. Add ADR-008 documenting the decision
4. Update ADR index

This change simplifies our code by removing unnecessary abstraction.
See ADR-008 for detailed rationale.

Author: ritwik-g

docs/ADRs/008-remove-command-registry.md

@@ -0,0 +1,74 @@
+# 8. Remove Command Registry Pattern
+
+Date: 2025-02-26
+
+## Status
+
+Accepted
+
+## Context
+
+We initially implemented a Command Registry pattern to manage and discover commands in our Helm plugin. The registry was designed to:
+- Register commands with unique names
+- Retrieve command instances by name
+- Potentially support future features like plugins, middleware, and dynamic command loading
+
+However, our current implementation shows that:
+1. Commands are statically defined in CLI functions using Typer
+2. Each CLI function directly knows which command to instantiate
+3. We don't have requirements for:
+   - Plugin system or third-party extensions
+   - Dynamic command loading/discovery
+   - Command aliasing or middleware
+   - Runtime command configuration
+
+The registry adds an unnecessary layer of indirection:
+```python
+# Current approach with registry
+registry = CommandRegistry()
+registry.register("init", InitCommand)
+command = registry.get_command("init")()
+
+# Simplified to
+command = InitCommand()
+```
+
+## Decision
+
+We will remove the Command Registry pattern and use direct command instantiation because:
+1. It simplifies the code by removing unnecessary abstraction
+2. It follows YAGNI (You Ain't Gonna Need It) principle
+3. Our commands are fixed and well-defined as part of the Helm plugin
+4. Typer handles CLI command registration and discovery
+5. We don't have current or planned requirements that would benefit from a registry
+
+## Consequences
+
+### Positive
+1. Simpler, more maintainable code
+2. Less indirection and complexity
+3. Easier to understand command flow
+4. Reduced testing surface
+5. Better alignment with Typer's design
+
+### Negative
+1. If we need these features in the future, we'll need to:
+   - Reimplement the registry pattern
+   - Update all command instantiation points
+   - Add command discovery mechanism
+
+### Neutral
+1. Command implementation and interface remain unchanged
+2. CLI functionality remains the same
+3. User experience is unaffected
+
+## Future Considerations
+
+If we need registry features in the future, we should consider:
+1. Plugin system requirements
+2. Command discovery needs
+3. Middleware requirements
+4. Integration with Helm plugin system
+
+## Related
+- [ADR-001] Initial Architecture Decision

docs/ADRs/README.md

@@ -55,6 +55,12 @@ An Architecture Decision Record (ADR) is a document that captures an important a
 - **Impact**: Ensures security while maintaining flexibility and traceability
 - **Dependencies**: ADR-005
 
+### [ADR-008: Remove Command Registry](008-remove-command-registry.md)
+- **Status**: Accepted
+- **Context**: Command Registry pattern adds unnecessary complexity
+- **Decision**: Remove registry in favor of direct command instantiation
+- **Impact**: Simplifies code and aligns better with Typer's design
+
 ## ADR Template
 For new ADRs, use this template:
 ```markdown

helm_values_manager/cli.py

@@ -3,7 +3,6 @@
 import typer
 
 from helm_values_manager.commands.init_command import InitCommand
-from helm_values_manager.commands.registry import CommandRegistry
 from helm_values_manager.utils.logger import HelmLogger
 
 COMMAND_INFO = "helm values-manager"
@@ -35,10 +34,7 @@ def init(
 ):
     """Initialize a new values manager configuration."""
     try:
-        # Initialize command registry and register commands
-        registry = CommandRegistry()
-        registry.register("init", InitCommand)
-        command = registry.get_command("init")()
+        command = InitCommand()
         result = command.execute(release_name=release_name)
         typer.echo(result)
     except Exception as e: