Replace NEXT.md approach with standardized Keep a Todofile V0.0.1 format for better task management and human-AI collaboration during coding sessions. ## Todofile System Setup: - **TODO.md**: Main todofile following Keep a Todofile V0.0.1 format - **TODOFILE_GUIDE.md**: Comprehensive system documentation and workflow - **Integration**: Fully integrated with existing kaizen-agentic framework - **Agent Support**: Uses agent-keepaTodofile for maintenance ## Content Migration: - Migrated strategic priorities from NEXT.md to TODO.md [Unreleased] section - Preserved session success criteria and development milestones - Organized tasks by impact type (To Add, To Fix, To Refactor) - Archived NEXT.md to history/NEXT_archived_20251025.md ## Documentation Updates: - README.md: Updated "Next Actions" → "Current Tasks" link - agent-project-management.md: Updated workflow to use TODO.md - docs/README.md: Updated project management references - Added comprehensive TODOFILE_GUIDE.md ## Benefits: - **Standardized Format**: Industry-standard Keep a Todofile format - **Better Organization**: Impact-based task categorization - **AI-Ready**: Designed for human-AI collaboration workflows - **Context Preservation**: Maintains coding flow across session interruptions - **Integration Ready**: Works with existing agent and capability systems Active tasks now in TODO.md [Unreleased] section focusing on strategic issue resolution and capability management validation. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
101 lines
4.8 KiB
Markdown
101 lines
4.8 KiB
Markdown
# Todofile
|
|
|
|
This is a "to do next" file, particularly useful to keep the human and a coding assistant in sync.
|
|
|
|
The format is based on [Keep a Todofile V0.0.1](https://coulomb.social/open/KeepaTodofile).
|
|
|
|
The structure organizes **future tasks** by their impact, just as a changelog organizes past changes by their impact.
|
|
|
|
***
|
|
|
|
## [Unreleased] - *Active Vibe-Coding State* 💡
|
|
|
|
This section is for tasks currently being discussed with or worked on by the coding assistant. These are the ephemeral, flow-of-thought tasks.
|
|
|
|
* **To Add:**
|
|
* Complete AST Query and Analysis CLI implementation (Issue #15)
|
|
* Performance Validation CLI implementation (Issue #16)
|
|
* Enhanced discovery tools validation and refinement
|
|
* **To Refactor:**
|
|
* Update any missing links in existing documentation to new capability system
|
|
* Refine capability discovery workflow based on practical usage
|
|
* Enhance AI assistant integration with capability system
|
|
* **To Fix:**
|
|
* Validate that CAPABILITY_DOCUMENTATION_INDEX.md provides effective navigation
|
|
* Ensure all agents are aware of capability inclusion workflow
|
|
* Test automated detection prevention of code duplication
|
|
* **To Remove:**
|
|
* Retire NEXT.md file after successful todofile migration
|
|
* Clean up any outdated task management references
|
|
|
|
***
|
|
|
|
## [0.3.0] - Strategic Development Execution - *Next Planned Increment*
|
|
|
|
This version represents the next set of concrete, planned features focusing on strategic issue resolution and capability validation.
|
|
|
|
### To Add
|
|
* **AST Query and Analysis CLI** - Complete implementation of Issue #15 with full AST parsing and analysis capabilities
|
|
* **Performance Validation CLI** - Complete implementation of Issue #16 with comprehensive performance testing and metrics
|
|
* **Enhanced Discovery Tools** - Improve `make capability-search TERM=xyz` based on real-world usage patterns
|
|
* **Capability Integration Validation** - Test framework for ensuring capability inclusion workflow effectiveness
|
|
|
|
### To Refactor
|
|
* **Documentation Ecosystem** - Update any missing links to new capability system components
|
|
* **AI Assistant Integration** - Enhance capability reference utilization for informed decision-making
|
|
* **Workflow Optimization** - Refine capability-first development process based on practical experience
|
|
|
|
### To Fix
|
|
* **Documentation Navigation** - Ensure CAPABILITY_DOCUMENTATION_INDEX.md provides effective project navigation
|
|
* **Agent Workflow Integration** - Validate all agents properly utilize capability inclusion workflow
|
|
* **Duplication Prevention** - Test and improve automated detection systems
|
|
|
|
### To Secure
|
|
* **Capability Validation** - Ensure capability inclusion system maintains security best practices
|
|
* **Dependency Management** - Validate external capability references and security implications
|
|
|
|
### To Remove
|
|
* **Legacy Task Management** - Retire NEXT.md approach in favor of standardized todofile system
|
|
* **Outdated Documentation References** - Clean up any references to deprecated task management approaches
|
|
|
|
***
|
|
|
|
## [COMPLETED] - *Capability Inclusion Management System - Version 0.2.0*
|
|
|
|
### ✅ Completed: To Add
|
|
* **Complete capability documentation ecosystem** - DONE
|
|
- CAPABILITIES.md for internal capabilities with detailed descriptions
|
|
- CAPABILITY_REGISTRY.md for external capabilities and dependencies
|
|
- CAPABILITY_DOCUMENTATION_INDEX.md for navigation and discovery
|
|
- CLAUDE_CAPABILITY_REFERENCE.md for AI assistant quick reference
|
|
- CAPABILITY_INCLUSION_GUIDE.md for workflow and best practices
|
|
* **Automated discovery tools** - DONE
|
|
- `make capability-search TERM=xyz` for capability discovery
|
|
- Prevention of code duplication through automated detection
|
|
- Enhanced agent definitions with capability inclusion workflow
|
|
* **Architectural clarity** - DONE
|
|
- Clear separation of internal vs external capabilities
|
|
- Comprehensive categorization system
|
|
- Detailed capability documentation with examples
|
|
|
|
### ✅ Completed: To Refactor
|
|
* **Agent definitions** - DONE
|
|
- Enhanced all agents with capability inclusion workflow awareness
|
|
- Updated agent instructions to utilize capability references
|
|
- Improved AI assistant integration patterns
|
|
|
|
### ✅ Completed: To Fix
|
|
* **Documentation ecosystem integration** - DONE
|
|
- All capability files properly interconnected
|
|
- Navigation system functional and comprehensive
|
|
- Discovery tools working effectively
|
|
|
|
### ✅ Completed: To Secure
|
|
* **Capability validation system** - DONE
|
|
- Proper validation of capability inclusion workflow
|
|
- Security considerations for external capability references
|
|
|
|
### ✅ Completed: To Remove
|
|
* **Code duplication risks** - DONE
|
|
- Implemented prevention mechanisms
|
|
- Automated detection and discovery systems |