plan-feature

IMPORTANT: PLANNING ONLY - NO CODE IMPLEMENTATION

This command is exclusively for PLANNING features. Do NOT:

• Write any code
• Create or modify components
• Install dependencies
• Run any bash commands
• Make any changes to the codebase

ONLY:

• Read existing files to understand context
• Create or update planning documentation in the planning/ folder
• Ask clarifying questions about requirements

You are tasked with planning a feature for the Database Analysis application following the workflow outlined in CLAUDE.md.

Instructions

1. Understand the Feature Request:

   • If a planning file path is provided (e.g., planning/feature-name.md), read it to understand the existing plan
   • If no file is provided or it doesn't exist, this is a new feature - understand requirements from the user's description
   • Identify the feature scope, goals, and success criteria

2. Follow CLAUDE.md Planning Workflow:

   • Review CLAUDE.md for project structure, tech stack, and guidelines
   • Ensure the plan respects:
     • Next.js and React best practices
     • Existing database patterns (use getPool() from @/lib/db-connections)
     • Tailwind CSS styling conventions
     • Existing UI component patterns (Shadcn/UI)
     • CamelCase naming for database tables
     • API endpoint documentation requirements

3. Create Comprehensive Plan:

   Structure the plan with these sections:

   Feature: [Feature Name]

   Overview

   • Brief description of the feature
   • Business value and goals
   • Target users

   Requirements

   • Functional requirements (numbered list)
   • Non-functional requirements (performance, security, etc.)

   Technical Design

   Database Changes

   • Schema modifications needed
   • New tables (use CamelCase naming)
   • Migrations required
   • Example SQL if applicable

   API Endpoints

   • List all new/modified endpoints
   • Request/response schemas
   • Authentication requirements
   • Error handling approach
   • API Documentation: Each feature should have a Postman collection in docs/api/
     • Create new Postman collection for the feature (e.g., docs/api/feature-name.postman_collection.json)
     • Include all endpoints with examples
     • Document request parameters, headers, and body
     • Include sample responses (success and error cases)
     • Add environment variables if needed