Add comprehensive analysis and development templates for CLAUDE workflows

- Introduced new analysis templates for architecture, implementation patterns, performance, quality, and security.
- Created detailed development templates for component creation, debugging, feature implementation, refactoring, testing, and migration planning.
- Established structured documentation guidelines for root, domain, module, and sub-module levels to enhance clarity and organization.
- Implemented a hierarchy analysis template to optimize project structure and documentation depth.
- Updated codex-unified documentation to reflect new command structures, template usage, and best practices for autonomous development workflows.

.claude/workflows/cli-templates/prompts/analysis/architecture.txt

@@ -0,0 +1,16 @@
+Analyze system architecture and design decisions:
+
+## Required Analysis:
+1. Identify main architectural patterns and design principles
+2. Map module dependencies and component relationships
+3. Assess integration points and data flow patterns
+4. Evaluate scalability and maintainability aspects
+5. Document architectural trade-offs and design decisions
+
+## Output Requirements:
+- Architectural diagrams or textual descriptions
+- Dependency mapping with specific file references
+- Integration point documentation with examples
+- Scalability assessment and bottleneck identification
+
+Focus on high-level design patterns and system-wide architectural concerns.

.claude/workflows/cli-templates/prompts/analysis/pattern.txt

@@ -0,0 +1,16 @@
+Analyze implementation patterns and code structure:
+
+## Required Analysis:
+1. Identify common code patterns and architectural decisions
+2. Extract reusable utilities and shared components
+3. Document existing conventions and coding standards
+4. Assess pattern consistency and identify anti-patterns
+5. Suggest improvements and optimization opportunities
+
+## Output Requirements:
+- Specific file:line references for all findings
+- Code snippets demonstrating identified patterns
+- Clear recommendations for pattern improvements
+- Standards compliance assessment
+
+Focus on actionable insights and concrete implementation guidance.

.claude/workflows/cli-templates/prompts/analysis/performance.txt

@@ -0,0 +1,16 @@
+Analyze performance characteristics and optimization opportunities:
+
+## Required Analysis:
+1. Identify performance bottlenecks and resource usage patterns
+2. Assess algorithm efficiency and data structure choices
+3. Evaluate caching strategies and optimization techniques
+4. Review memory management and resource cleanup
+5. Document performance metrics and improvement opportunities
+
+## Output Requirements:
+- Performance bottleneck identification with specific locations
+- Algorithm complexity analysis and optimization suggestions
+- Caching pattern documentation and recommendations
+- Memory usage patterns and optimization opportunities
+
+Focus on measurable performance improvements and concrete optimization strategies.

.claude/workflows/cli-templates/prompts/analysis/quality.txt

@@ -0,0 +1,16 @@
+Analyze code quality and maintainability aspects:
+
+## Required Analysis:
+1. Assess code organization and structural quality
+2. Evaluate naming conventions and readability standards
+3. Review error handling and logging practices
+4. Analyze test coverage and testing strategies
+5. Document technical debt and improvement priorities
+
+## Output Requirements:
+- Code quality metrics and specific improvement areas
+- Naming convention consistency analysis
+- Error handling pattern documentation
+- Test coverage assessment with gap identification
+
+Focus on maintainability improvements and long-term code health.

.claude/workflows/cli-templates/prompts/analysis/security.txt

@@ -0,0 +1,16 @@
+Analyze security implementation and potential vulnerabilities:
+
+## Required Analysis:
+1. Identify authentication and authorization mechanisms
+2. Assess input validation and sanitization practices
+3. Review data encryption and secure storage methods
+4. Evaluate API security and access control patterns
+5. Document security risks and compliance considerations
+
+## Output Requirements:
+- Security vulnerability findings with file:line references
+- Authentication/authorization pattern documentation
+- Input validation examples and gaps
+- Encryption usage patterns and recommendations
+
+Focus on identifying security gaps and providing actionable remediation steps.