-
Notifications
You must be signed in to change notification settings - Fork 0
Description
PKS CLI Development Roadmap 🎯
This roadmap outlines the strategic development path for PKS CLI, an agentic development platform that simplifies .NET development through AI-powered automation and intelligent tooling.
🎯 Project Vision
PKS CLI aims to be a comprehensive agentic development platform that enables developers to work more efficiently by leveraging AI agents, sophisticated automation, and intelligent project orchestration. The tool follows a "simulate → build/mock → real" development principle with extensive AI assistance.
🏗️ Core Architecture Milestones
1️⃣ Hooks Command & Integration System
Priority: High | Status: Planning
-
Research & Design
- Study Claude Code hooks system (docs)
- Implement smart dispatcher pattern to optimize expensive tool calls
- Reference implementation: claudelog.com/mechanics/hooks
-
Implementation
- Create
pks hookscommand for Claude Code integration - Develop hooks initializer (similar to CLAUDE.md and .mcp.json)
- Implement intelligent hook dispatching
- Create
-
Testing & Validation
- Unit tests for hook system
- Integration tests with Claude Code
- Performance benchmarking for dispatcher
2️⃣ Enhanced MCP (Model Context Protocol) Server
Priority: High | Status: In Development
-
Core MCP Server
- Implement .NET MCP server using C# SDK
- Support both stdio and HTTP transport modes
- Reference: Microsoft MCP Guide
- Stateless HTTP server configuration for devcontainer access
-
Resource & Tool Exposure
- Expose agent status and availability as MCP resources
- Create current tasks resource for active agents
- Implement tools for task creation/queueing
- Example prompts for GitHub issue triage workflows
-
Integration Features
- Slash command prompts for Claude Code
- Task management through MCP interface
- Agent orchestration tools
3️⃣ Agent Framework & Communication System
Priority: High | Status: Design Phase
-
Agent Structure
- Design
.pks/agentsfolder structure:.pks/agents/ ├── agent-name/ │ ├── knowledge.md │ └── persona.md - Implement
pks agents loadcommand - Agent state management in MCP server
- Design
-
Orchestration System
- Coordinator/swarm lead functionality in CLAUDE.md
- Task delegation system (no self-execution)
- Agent knowledge/persona loading via MCP
-
Inter-Agent Communication
- Message queue implementation in MCP server
- Automatic agent spawning for pending messages
- Orchestrator monitoring of message queue
- Communication context injection into initializers
4️⃣ PRD (Product Requirements Document) Tools
Priority: Medium | Status: Planning
-
CLI Commands
-
pks prd "idea description"- Generate PRD.md files -
pks prd load- Parse and structure existing PRDs
-
-
MCP Integration
- PRD tools in MCP server for requirements management
- Product Owner agent integration
- Next-task recommendation system
-
Workflow Integration
- PRD-driven development workflows
- Requirements tracking and validation
5️⃣ Enhanced Documentation System
Priority: Medium | Status: Enhancement
-
Modular CLAUDE.md
- Inspiration from SuperClaude Framework
- Implement file inclusion system:
@COMMANDS.md @FLAGS.md @PRINCIPLES.md @RULES.md @MCP.md @PERSONAS.md @ORCHESTRATOR.md @MODES.md - Project-specific documentation integration
-
Documentation Automation
- Automated documentation generation
- Context-aware documentation updates
- Version-controlled documentation workflows
6️⃣ GitHub Integration & Project Management
Priority: Medium | Status: Research
-
GitHub Integration
- Project-scoped Personal Access Token (PAT) generation
- API integration for repository management
- MCP server GitHub resource exposure
-
Project Identity System
- Project ID assignment and management
-
pks mcp --project-id xxxwith auto-creation - Authentication flow integration
- Project selection and switching
-
Development Workflow Tools
- GitHub issues and PR management
- MCP prompts for development flows
- Bridge between local commands and MCP prompts
- Support for multiple AI tools (Claude Code, GitHub Copilot, Gemini CLI)
🎨 Branding & Naming
Priority: Low | Status: Open Discussion
Current: PKS (Poul Kjeldager Sørensen)
- Explore alternative meanings that align with agentic development
- Consider: "Professional [X] Simplifier" where X relates to AI/automation
- Community input and feedback collection
📚 Documentation & Communication
Priority: Ongoing | Status: Active
-
Developer Onboarding
- Explain agentic development methodology
- Document simulate → build/mock → real principle
- Extensive AI usage disclosure and practices
-
Quality Assurance
- Enterprise-ready evaluation frameworks
- Comprehensive testing strategies
- Mock-to-real transition validation
-
Issue-Driven Development
- Use GitHub issues for all feature tracking
- Community contribution guidelines
- Release planning and communication
🔄 Development Methodology
Agentic Development Principles
- AI-First Development: Extensive use of LLMs and AI for code generation
- Iterative Validation: Simulate → Mock → Real progression
- Quality Gates: Comprehensive testing before production releases
- Transparency: Clear documentation of AI-generated vs. human-reviewed code
Testing Strategy
- Test-Driven Development (TDD) for core features
- Mock implementations for rapid prototyping
- Integration testing for real-world scenarios
- Performance benchmarking for enterprise readiness
📈 Success Metrics
- Developer Experience: Time-to-productivity measurements
- AI Integration: Agent task completion rates
- Enterprise Adoption: Production deployment success rates
- Community Growth: Contributor and user engagement metrics
🚀 Getting Started
To contribute to this roadmap:
- Review the current objectives in
/objectives.md - Check existing issues for detailed task breakdowns
- Follow the agentic development principles
- Ensure all changes align with the enterprise-ready quality standards
Next Immediate Actions:
- Begin hooks command research and implementation
- Enhance MCP server with resource exposure
- Design agent framework architecture
- Create detailed task breakdown issues for each milestone
This roadmap is a living document that evolves with the project. All major changes should be discussed through GitHub issues to maintain transparency and community input.