shancheas
0b0bdd9c4b
- Introduced backend patterns skill with guidelines on API design, database optimization, and server-side best practices. - Added coding standards skill outlining universal coding principles for TypeScript, NestJS, and Node.js development. - Implemented continuous learning skill to automatically extract reusable patterns from Cursor sessions. - Created NestJS best practices skill detailing architecture patterns, dependency injection, error handling, and security measures. - Included various rules and templates for NestJS best practices to ensure production-ready applications.
3.5 KiB
3.5 KiB
description
| description |
|---|
| Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code. |
Plan Command
This command invokes the planner agent to create a comprehensive implementation plan before writing any code.
What This Command Does
- Restate Requirements - Clarify what needs to be built
- Identify Risks - Surface potential issues and blockers
- Create Step Plan - Break down implementation into phases
- Wait for Confirmation - MUST receive user approval before proceeding
When to Use
Use /plan when:
- Starting a new feature
- Making significant architectural changes
- Working on complex refactoring
- Multiple files/components will be affected
- Requirements are unclear or ambiguous
How It Works
The planner agent will:
- Analyze the request and restate requirements in clear terms
- Break down into phases with specific, actionable steps
- Identify dependencies between components
- Assess risks and potential blockers
- Estimate complexity (High/Medium/Low)
- Present the plan and WAIT for your explicit confirmation
Example Usage
User: /plan I need to add real-time notifications when markets resolve
Agent (planner):
# Implementation Plan: Real-Time Market Resolution Notifications
## Requirements Restatement
- Send notifications to users when markets they're watching resolve
- Support multiple notification channels (in-app, email, webhook)
- Ensure notifications are delivered reliably
- Include market outcome and user's position result
## Implementation Phases
### Phase 1: Database Schema
- Add notifications table with columns: id, user_id, market_id, type, status, created_at
- Add user_notification_preferences table for channel preferences
- Create indexes on user_id and market_id for performance
### Phase 2: Notification Service
- Create NotificationsModule under src/modules/notifications/
- Implement notification queue using BullMQ/Redis
- Add retry logic for failed deliveries
- Create notification templates
### Phase 3: Integration Points
- Hook into market resolution logic (when status changes to "resolved")
- Query all users with positions in market
- Enqueue notifications for each user
### Phase 4: API
- Expose notification endpoints on NotificationsController
- Add NestJS WebSocket gateway for live updates
- Add notification preferences endpoints
## Dependencies
- Redis (for queue)
- Email service (SendGrid/Resend)
- NestJS WebSockets (or Redis pub/sub)
## Risks
- HIGH: Email deliverability (SPF/DKIM required)
- MEDIUM: Performance with 1000+ users per market
- MEDIUM: Notification spam if markets resolve frequently
- LOW: Real-time subscription overhead
## Estimated Complexity: MEDIUM
- Backend: 4-6 hours
- Frontend: 3-4 hours
- Testing: 2-3 hours
- Total: 9-13 hours
**WAITING FOR CONFIRMATION**: Proceed with this plan? (yes/no/modify)
Important Notes
CRITICAL: The planner agent will NOT write any code until you explicitly confirm the plan with "yes" or "proceed" or similar affirmative response.
If you want changes, respond with:
- "modify: [your changes]"
- "different approach: [alternative]"
- "skip phase 2 and do phase 3 first"
Integration with Other Commands
After planning:
- Use
/tddto implement with test-driven development - Use
/build-and-fixif build errors occur - Use
/code-reviewto review completed implementation
Related Agents
This command invokes the planner agent located at:
.cursor/agents/planner.md