f66718122a
**Planning Structure:** - TODO.md - Sprint planning and current tasks - ROADMAP.md - Long-term vision and milestones - .github/ISSUE_TEMPLATE/ - Issue templates for features and MCP tools **TODO.md:** - 5 phases: Core (done), Enhancement, Advanced, Docs, Integrations - Current sprint tasks clearly defined - Progress tracking with checkboxes **ROADMAP.md:** - Vision and milestones - v1.0 (done), v1.1 (in progress), v1.2-3.0 (planned) - Feature ideas categorized by priority - Metrics and goals - Release schedule **Issue Templates:** - feature_request.md - General features - mcp_tool.md - New MCP tools specifically Next: Fix tests, test MCP with Claude Code, document setup 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
1.5 KiB
1.5 KiB
Skill Seeker MCP Development Plan
Phase 1: MCP Core ✅ DONE
- Refactor to monorepo structure
- Create MCP server skeleton
- Implement 6 basic tools
- Update tests for new structure
Phase 2: MCP Enhancement 🚧 IN PROGRESS
- Fix remaining 3 test failures
- Add MCP configuration examples
- Test MCP server with Claude Code
- Add error handling improvements
- Add logging to MCP tools
Phase 3: Advanced MCP Features 📋 PLANNED
- Interactive config generation (wizard-style)
- Real-time progress updates
- Parallel terminal support for enhancement
- Batch operations (multiple configs at once)
- Config templates for popular frameworks
Phase 4: Documentation & Polish 📋 PLANNED
- Update main README for monorepo
- Create MCP setup guide with screenshots
- Add video tutorial
- Create example workflows
- Performance optimization
Phase 5: Advanced Integrations 💭 IDEAS
- Web interface for config generation
- GitHub Actions integration
- Auto-discovery of documentation patterns
- Skill quality metrics
- Community config repository
Current Sprint (Week of Oct 19)
Priority Tasks
- Fix 3 test failures (warnings vs errors)
- Create
.claude/mcp_config.jsonexample - Test MCP with actual Claude Code
- Document MCP setup process
Blockers
- None
Notes
- MCP server uses stdio protocol
- All CLI tools work via subprocess
- Tests at 95.8% (68/71 passing)