feat: [#1] add environment show command specification

- Add complete feature specification for 'show' command in docs/features/environment-status-command/
- Command displays environment information with state-aware details
- Includes README, questions (with answers), and detailed specification
- Documents 7-phase implementation plan with top-down approach
- Estimated duration: 14-22 hours (2-3 days)
- E2E test created in Phase 1, evolves throughout implementation
- Unit tests written at each phase for incremental validation
- Updates roadmap to reflect 'show' command (task 5.1) instead of 'status'
- Reserves 'status' for future service health checks

Key decisions documented:
- Command name: 'show' (display stored data, no remote verification)
- Read-only operation (no state modifications)
- Human-friendly output first, JSON format as future enhancement
- State-aware information (Created, Provisioned, Configured, Running, etc.)
- SSH key path included in output for Provisioned state and beyond
- Provider-specific information (LXD container ID, Hetzner server details)
- Testing strategy: Unit tests + E2E in existing workflow tests
- Target completion: January 2026

Author: josecelano

docs/features/README.md

@@ -13,12 +13,13 @@ Feature documentation serves to:
 
 ## 📁 Active Features
 
-| Feature                                                            | Status         | Priority | Created      |
-| ------------------------------------------------------------------ | -------------- | -------- | ------------ |
-| [JSON Schema Generation](./json-schema-generation/README.md)       | 📋 Specified   | High     | Dec 12, 2025 |
-| [Linter Auto-fix](./linter-auto-fix/README.md)                     | 📋 Specified   | Medium   | Oct 9, 2025  |
-| [Linter Parallel Execution](./linter-parallel-execution/README.md) | ⏸️ Deferred    | Low      | Oct 9, 2025  |
-| [Environment State Management](./environment-state-management/)    | 🔄 Refactoring | High     | Sept 9, 2025 |
+| Feature                                                              | Status         | Priority | Created      |
+| -------------------------------------------------------------------- | -------------- | -------- | ------------ |
+| [Environment Status Command](./environment-status-command/README.md) | 📋 Specified   | Medium   | Dec 16, 2025 |
+| [JSON Schema Generation](./json-schema-generation/README.md)         | 📋 Specified   | High     | Dec 12, 2025 |
+| [Linter Auto-fix](./linter-auto-fix/README.md)                       | 📋 Specified   | Medium   | Oct 9, 2025  |
+| [Linter Parallel Execution](./linter-parallel-execution/README.md)   | ⏸️ Deferred    | Low      | Oct 9, 2025  |
+| [Environment State Management](./environment-state-management/)      | 🔄 Refactoring | High     | Sept 9, 2025 |
 
 ## ✅ Completed Features
 

docs/features/environment-status-command/README.md

@@ -0,0 +1,65 @@
+# Environment Status Command
+
+A new console command to display environment information with state-aware details.
+
+## 📄 Documents
+
+### [specification.md](./specification.md)
+
+The main feature specification including:
+
+- Overview and problem statement
+- Feature goals
+- Proposed solution
+- Implementation details
+- Definition of done
+- Testing strategy
+
+### [questions.md](./questions.md)
+
+Clarifying questions that need to be answered before implementation:
+
+- Command naming decision (status vs show)
+- Output format requirements
+- State-specific information to display
+- Future extensibility for JSON output
+
+## 📋 Status
+
+**Current Phase**: Planning
+
+**Completed**:
+
+1. ✅ Create feature specification
+2. ✅ Create questions document
+3. ⏳ Answer clarifying questions
+4. ⏳ Update specification based on answers
+5. ⏳ Begin implementation
+
+**Next Steps**:
+
+1. Answer clarifying questions (command name, output format)
+2. Refine specification with detailed output format
+3. Implement application layer StatusCommand/ShowCommand
+4. Implement presentation layer console subcommand
+5. Add E2E tests
+
+## 🎯 Quick Summary
+
+Add a new console command to display environment information with state-aware details. The command will show basic information like environment name and current state, with additional details based on the state (e.g., IP address and SSH port for provisioned environments).
+
+**Key Points**:
+
+- **Problem**: Users need visibility into environment state and details without inspecting JSON files
+- **Solution**: New console command that loads environment and displays human-friendly information
+- **Status**: Planning phase - need to decide on command name and output format
+- **Command Name Options**: `status` or `show`
+- **Usage**: `torrust-tracker-deployer {status|show} <environment-name>`
+
+## 🔗 Related Documentation
+
+- [Console Commands Overview](../../console-commands.md)
+- [Command Architecture](../../codebase-architecture.md)
+- [User Guide - Commands](../../user-guide/commands.md)
+- [Development Principles](../../development-principles.md)
+- [Output Handling Guide](../../contributing/output-handling.md)