Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/ijoka:add-featureThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /add-feature Add a new feature to the Ijoka graph database. ## Usage **Categories:** functional, ui, security, performance, documentation, testing, infrastructure, refactoring, planning, meta ## Instructions When this command is invoked: 1. **Parse the arguments** from: $ARGUMENTS - First word = category - Remaining words = description 2. **Validate category** - Must be one of: - functional, ui, security, performance, documentation - testing, infrastructure, refactoring, planning, meta 3. **Check for duplicates** - Run `ijoka status` - Use fuzzy matching on descri...
Add a new feature to the Ijoka graph database.
/add-feature <category> <description>
Categories: functional, ui, security, performance, documentation, testing, infrastructure, refactoring, planning, meta
When this command is invoked:
Parse the arguments from: $ARGUMENTS
Validate category - Must be one of:
Check for duplicates - Run ijoka status
Create the feature:
ijoka feature create --category "<category>" --priority 50 "<description>"
Confirm creation - Show:
/next-feature if no active feature/add-feature functional User can export data to CSV format
Creates feature:
/add-feature security Implement rate limiting on API endpoints
Creates feature:
To specify priority, include it after category:
/add-feature security:90 Implement rate limiting
This creates the feature with priority 90 (higher = more urgent).
npx claudepluginhub shakestzd/ijoka --plugin ijoka/add-featureAdds a new feature module (CRUD resource, service, middleware, CLI command, or UI component) to the project, generating files, tests, wiring routes/middleware, and updating docs per conventions.
/add-featureAdds new features to existing codebase through analysis, design, backend/frontend implementation, testing (unit/integration/E2E), quality checks, and integration.