Feature Development Workflow Command
End-to-end feature implementation workflow covering planning, backend API development, frontend UI, database migrations, testing, and documentation. Guides you through the full lifecycle from requirements to PR-ready code.
Command
/feature
Description
Orchestrates a complete feature development workflow from requirements through implementation, testing, and PR creation. Follows a structured approach that covers backend, frontend, database, and testing concerns systematically.
Behavior
Arguments
$ARGUMENTS-- Feature description (e.g., "user profile page with avatar upload")
Workflow Phases
Phase 1: Planning
- Analyze requirements: Break down the feature description into specific tasks
- Identify affected areas: List files, APIs, database tables, and UI components
- Define the data model: Schema changes, migrations, types/interfaces
- Design the API: Endpoints, request/response shapes, error handling
- Plan the UI: Components, state management, user flows
- Estimate scope: Present a task list for approval before coding
## Feature Plan: User Profile Page ### Tasks - [ ] Database: Add `avatar_url` column to users table - [ ] Backend: POST /api/users/:id/avatar (upload endpoint) - [ ] Backend: GET /api/users/:id/profile (profile data) - [ ] Frontend: ProfilePage component - [ ] Frontend: AvatarUpload component - [ ] Tests: API endpoint tests - [ ] Tests: Component tests Proceed with implementation? (yes/no)
Phase 2: Database & Backend
- Create database migration (if needed)
- Define TypeScript types/interfaces
- Implement service layer (business logic)
- Implement API route handlers
- Add input validation and error handling
- Write backend tests
Phase 3: Frontend
- Create page/component structure
- Implement API client functions
- Build UI components with proper state management
- Handle loading, error, and empty states
- Add form validation
- Write component tests
Phase 4: Integration & Polish
- Run the full test suite
- Check for TypeScript errors (
tsc --noEmit) - Run linter (
eslint,prettier) - Test the happy path end-to-end
- Test error scenarios
- Update relevant documentation
Phase 5: PR Preparation
- Create a descriptive branch name
- Make atomic commits with clear messages
- Generate PR description with changes summary
- List testing steps for reviewers
Output Format
After each phase, provide a status update:
## Phase 2 Complete: Backend ### Created Files - src/migrations/20250325_add_avatar_url.sql - src/services/profileService.ts - src/routes/profile.ts - tests/routes/profile.test.ts ### API Endpoints - GET /api/users/:id/profile -- Returns user profile data - POST /api/users/:id/avatar -- Uploads avatar (multipart/form-data) ### Tests: 6 passing, 0 failing Proceeding to Phase 3: Frontend...
Examples
# Implement a complete feature /feature user profile page with avatar upload and bio editing # Backend-only feature /feature webhook processing for Stripe payment events --backend-only # Frontend-only feature /feature dashboard analytics charts --frontend-only
Reviews
No reviews yet. Be the first to review this template!
Similar Templates
Git Commit Message Generator
Generates well-structured conventional commit messages by analyzing staged changes. Follows Conventional Commits spec with scope detection.
React Component Scaffolder
Scaffolds a complete React component with TypeScript types, Tailwind styles, Storybook stories, and unit tests. Follows project conventions automatically.
CI/CD Pipeline Generator
Generates GitHub Actions workflows for CI/CD including linting, testing, building, and deploying. Detects project stack automatically.