- plan.md: Compress from 307 to 183 lines while preserving all core functionality
- Add project structure analysis with get_modules_by_depth.sh integration
- Implement 5-field JSON schema compliance with workflow-architecture.md
- Add detailed context acquisition strategy with tool templates
- Include comprehensive file cohesion principles and variable system
- Maintain 10-task limit enforcement and pre-planning analysis requirements
- execute.md: Compress from 380 to 220 lines with enhanced agent context
- Preserve complete Task execution patterns with full flow control context
- Maintain comprehensive session context, implementation guidance, and error handling
- Streamline discovery process while keeping all critical execution details
- Keep complete agent assignment and status management functionality
- workflow-architecture.md: Minor structural updates for consistency
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Simplified argument hints and examples in plan.md
- Enhanced input detection logic for files, issues, and text
- Introduced analysis levels for improved context analysis
- Updated core rules for task limits and decomposition strategies
- Improved session management with active session marker system
- Expanded file structure reference and naming conventions
- Clarified task hierarchy and status rules
- Added detailed validation and error handling procedures
- Streamlined document templates for implementation plans and task summaries
- Update unified file structure to stress on-demand creation principle
- Add creation strategy section with explicit guidance:
- Initial setup creates only required files (session.json, IMPL_PLAN.md, TODO_LIST.md, .task/)
- Optional directories (.brainstorming/, .chat/, .summaries/) created when first needed
- Update core design principles to include on-demand file creation
- Add session initialization and directory creation examples in Data Operations
This ensures workflows start lean and expand only as functionality is used.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Replace separate Main Tasks/Subtasks sections with unified hierarchical list
- Use ▸ symbol for container tasks (with subtasks) instead of checkboxes
- Maintain standard - [ ]/- [x] for executable leaf tasks
- Add 2-space indentation to show task hierarchy clearly
- Include status legend for better user understanding
Benefits:
- Eliminates confusion about non-executable main tasks
- Provides clear visual hierarchy in single list
- Reduces TODO_LIST complexity and improves usability
- Aligns container task concept with execution model
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add 'paths' field to task JSON schema with semicolon-separated concrete paths
- Create read-task-paths.sh script to convert paths to Gemini @ format
- Update all agents to use task-specific paths instead of --all-files
- Integrate get_modules_by_depth.sh for project structure discovery
- Update workflow planning to populate paths field automatically
- Enhance execute command to pass task-specific paths to agents
- Update documentation for new path management system
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
## Major Changes
- Add --AM flag to /workflow:plan command for analysis method selection
- Support both Gemini CLI (pattern-based) and Codex CLI (autonomous) analysis
- Implement dual marker system: [GEMINI_CLI_REQUIRED] and [CODEX_CLI_REQUIRED]
- Update all 4 agents to handle both analysis markers
- Create analysis method templates for standardized CLI usage
## Files Modified
- workflow-architecture.md: Add Analysis Method Integration section
- plan.md: Add --AM flag and bilingual rule standardization
- execute.md: Update marker mapping logic and standardize to English
- 4 agent files: Add dual CLI support with usage guidelines
- New: analysis-methods/ templates for Gemini and Codex CLI
## Backward Compatibility
- Gemini CLI remains default analysis method
- Existing workflows continue to work unchanged
- Progressive enhancement for autonomous development scenarios
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- 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.
