IDE Command Support Investigation for Claude Code and Cursor

[SergK]

Current Functionality

The KubeRocketAI framework currently requires users to manually activate agents and execute tasks through external interfaces or copy-paste workflows. Developers need to:

• Switch between IDE and external tools to access framework capabilities
• Remember specific agent activation commands and task syntax
• Manually manage framework task dependencies and templates
• Context switch between development environment and framework execution

Current Limitations

• Context Switching Overhead: Developers must leave their coding environment to access framework capabilities
• Manual Task Execution: No streamlined way to execute the top 10 most-used commands (create-story, create-github-issues, review-story, implement, plan-implementation, create-prd, create-project-brief, plan, create-sad, update-story)
• IDE Integration Gap: No native integration with primary development IDEs (Claude Code and Cursor)
• Framework Accessibility: Existing .krci-ai/tasks/ and agent definitions not easily accessible from development context

Proposed Improvement

Investigate and design IDE command integration for Claude Code and Cursor that enables developers to access KubeRocketAI framework capabilities directly within their coding environment.

Key Investigation Areas:

• Claude Code Integration: Research slash command implementation using .claude/commands/krci-ai/{agents,tasks}/ structure
• Cursor Integration: Research rules-based command implementation using .cursor/rules/krci-ai/{agents,tasks}/ structure
• Task Reference Methods: Investigate approaches for referencing framework task files and dependencies
• Agent Context Delivery: Explore methods for providing appropriate persona context within IDE environments
• Directory Organization: Design optimal structure mirroring framework's core agent/task separation

Expected Benefits

• Reduced Context Switching: Developers can execute framework commands without leaving their IDE
• Improved Productivity: Quick access to the 10 most frequently used framework commands
• Better Framework Adoption: Seamless integration encourages more consistent framework usage
• Maintained Framework Integrity: Commands leverage existing .krci-ai/tasks/ and agent definitions
• Scalable Organization: Clear agent-level and task-level command separation for future expansion

Implementation Examples

Claude Code Command Structure:

.claude/commands/krci-ai/
├── agents/po.md          # Full PO agent capabilities  
├── agents/dev.md         # Full Dev agent capabilities
└── tasks/create-story.md # Individual task execution

Cursor Rules Structure:

.cursor/rules/krci-ai/
├── agents/po.md          # Full PO agent capabilities
├── agents/dev.md         # Full Dev agent capabilities  
└── tasks/create-story.md # Individual task execution

Testing Considerations

• Feasibility Assessment: Validate technical approach for task file referencing and dependency inclusion
• User Experience Testing: Ensure IDE integration feels natural and maintains framework quality
• Cross-Platform Compatibility: Test command functionality across macOS/Linux/Windows environments
• Framework Integrity: Verify commands properly leverage existing framework capabilities without duplication

---

Relates to: Epic 99

[SergK]

https://alirezarezvani.medium.com/claude-code-2-0-13-be2c0a723856 and https://claudecodemarketplace.com/