
Full-Stack Feature Development Workflow
Plan and execute full-stack features end-to-end with structured methodology
What You Can Do
You'll transform high-level feature requirements into a complete development plan covering API design, frontend implementation, testing strategy, and documentation. The skill helps you identify dependencies, parallelize work across frontend and backend teams, and establish quality gates that ensure features ship bug-free with proper error handling and logging.
Features
Structured format for requirements, acceptance criteria, and edge cases
Define endpoints, request/response schemas, error codes, and validation rules
Split frontend and backend tasks with clear contracts and dependencies
Unit tests for backends, Playwright E2E for frontends, with concrete test scenarios
Schema changes with rollback strategies and zero-downtime deployment
Field-level validation rules, error responses, and logging patterns
Feature specs, API references, test plans with cross-linked markdown
Definition of done criteria covering code, tests, logs, and documentation
Example Output
Feature Plan Output:
Feature: User Authentication Flow
API Endpoints:
- POST /auth/register → Creates user, validates email format
- POST /auth/login → Returns JWT token
- GET /auth/me → Requires Bearer token
Frontend Tasks:
- Login form component with client-side validation
- Protected route wrapper
- Token persistence in localStorage
Backend Tasks:
- User schema migration (email unique, password hashed)
- JWT token generation and verification
- Email verification workflow
Testing:
- Unit: All endpoints with valid/invalid inputs
- E2E: Register → Verify Email → Login → Navigate to Protected Page
QA Checklist:
- ✓ All endpoints validated on server
- ✓ No console errors in browser logs
- ✓ Migration tested against prod DB schema
- ✓ README with setup instructions
What's Included
- SKILL.md: Full development workflow with decision trees and quality gates
- Feature Template: Spec format for requirements and acceptance criteria
- API Design Checklist: Endpoint planning, schema validation, error responses
- Testing Strategy Guide: When to use unit tests vs E2E, test structure examples
- QA Criteria Checklist: Definition of done for backend, frontend, and documentation
- Database Migration Playbook: Schema changes, rollback strategies, zero-downtime deployment
- Documentation Templates: Feature specs, API references, test plans
Who It's For
- Full-stack engineers planning multi-week features
- Engineering leads designing feature workflows for teams
- Backend developers coordinating with frontend teams
- QA engineers establishing quality gates and test plans
- Startup CTOs defining development methodology
Best For
- Planning features that span multiple systems (frontend, backend, database)
- Setting up parallel development workflows for teams
- Establishing testing and QA processes
- Designing API contracts between frontend and backend
- Writing feature specifications with acceptance criteria
- Creating database migration strategies






