Backend Development Feature Development

1---
2name: backend-development-feature-development
3description: "Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services."
4---
5 
6Orchestrate end-to-end feature development from requirements to production deployment:
7 
8[Extended thinking: This workflow orchestrates specialized agents through comprehensive feature development phases - from discovery and planning through implementation, testing, and deployment. Each phase builds on previous outputs, ensuring coherent feature delivery. The workflow supports multiple development methodologies (traditional, TDD/BDD, DDD), feature complexity levels, and modern deployment strategies including feature flags, gradual rollouts, and observability-first development. Agents receive detailed context from previous phases to maintain consistency and quality throughout the development lifecycle.]
9 
10## Use this skill when
11 
12- Coordinating end-to-end feature delivery across backend, frontend, and data
13- Managing requirements, architecture, implementation, testing, and rollout
14- Planning multi-service changes with deployment and monitoring needs
15- Aligning teams on scope, risks, and success metrics
16 
17## Do not use this skill when
18 
19- The task is a small, isolated backend change or bug fix
20- You only need a single specialist task, not a full workflow
21- There is no deployment or cross-team coordination involved
22 
23## Instructions
24 
251. Confirm feature scope, success metrics, and constraints.
262. Select a methodology and define phase outputs.
273. Orchestrate implementation, testing, and security validation.
284. Prepare rollout, monitoring, and documentation plans.
29 
30## Safety
31 
32- Avoid production changes without approvals and rollback plans.
33- Validate data migrations and feature flags in staging first.
34 
35## Configuration Options
36 
37### Development Methodology
38 
39- **traditional**: Sequential development with testing after implementation
40- **tdd**: Test-Driven Development with red-green-refactor cycles
41- **bdd**: Behavior-Driven Development with scenario-based testing
42- **ddd**: Domain-Driven Design with bounded contexts and aggregates
43 
44### Feature Complexity
45 
46- **simple**: Single service, minimal integration (1-2 days)
47- **medium**: Multiple services, moderate integration (3-5 days)
48- **complex**: Cross-domain, extensive integration (1-2 weeks)
49- **epic**: Major architectural changes, multiple teams (2+ weeks)
50 
51### Deployment Strategy
52 
53- **direct**: Immediate rollout to all users
54- **canary**: Gradual rollout starting with 5% of traffic
55- **feature-flag**: Controlled activation via feature toggles
56- **blue-green**: Zero-downtime deployment with instant rollback
57- **a-b-test**: Split traffic for experimentation and metrics
58 
59## Phase 1: Discovery & Requirements Planning
60 
611. **Business Analysis & Requirements**
62   - Use Task tool with subagent_type="business-analytics::business-analyst"
63   - Prompt: "Analyze feature requirements for: $ARGUMENTS. Define user stories, acceptance criteria, success metrics, and business value. Identify stakeholders, dependencies, and risks. Create feature specification document with clear scope boundaries."
64   - Expected output: Requirements document with user stories, success metrics, risk assessment
65   - Context: Initial feature request and business context
66 
672. **Technical Architecture Design**
68   - Use Task tool with subagent_type="comprehensive-review::architect-review"
69   - Prompt: "Design technical architecture for feature: $ARGUMENTS. Using requirements: [include business analysis from step 1]. Define service boundaries, API contracts, data models, integration points, and technology stack. Consider scalability, performance, and security requirements."
70   - Expected output: Technical design document with architecture diagrams, API specifications, data models
71   - Context: Business requirements, existing system architecture
72 
733. **Feasibility & Risk Assessment**
74   - Use Task tool with subagent_type="security-scanning::security-auditor"
75   - Prompt: "Assess security implications and risks for feature: $ARGUMENTS. Review architecture: [include technical design from step 2]. Identify security requirements, compliance needs, data privacy concerns, and potential vulnerabilities."
76   - Expected output: Security assessment with risk matrix, compliance checklist, mitigation strategies
77   - Context: Technical design, regulatory requirements
78 
79## Phase 2: Implementation & Development
80 
814. **Backend Services Implementation**
82   - Use Task tool with subagent_type="backend-architect"
83   - Prompt: "Implement backend services for: $ARGUMENTS. Follow technical design: [include architecture from step 2]. Build RESTful/GraphQL APIs, implement business logic, integrate with data layer, add resilience patterns (circuit breakers, retries), implement caching strategies. Include feature flags for gradual rollout."
84   - Expected output: Backend services with APIs, business logic, database integration, feature flags
85   - Context: Technical design, API contracts, data models
86 
875. **Frontend Implementation**
88   - Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"
89   - Prompt: "Build frontend components for: $ARGUMENTS. Integrate with backend APIs: [include API endpoints from step 4]. Implement responsive UI, state management, error handling, loading states, and analytics tracking. Add feature flag integration for A/B testing capabilities."
90   - Expected output: Frontend components with API integration, state management, analytics
91   - Context: Backend APIs, UI/UX designs, user stories
92 
936. **Data Pipeline & Integration**
94   - Use Task tool with subagent_type="data-engineering::data-engineer"
95   - Prompt: "Build data pipelines for: $ARGUMENTS. Design ETL/ELT processes, implement data validation, create analytics events, set up data quality monitoring. Integrate with product analytics platforms for feature usage tracking."
96   - Expected output: Data pipelines, analytics events, data quality checks
97   - Context: Data requirements, analytics needs, existing data infrastructure
98 
99## Phase 3: Testing & Quality Assurance
100 
1017. **Automated Test Suite**
102   - Use Task tool with subagent_type="unit-testing::test-automator"
103   - Prompt: "Create comprehensive test suite for: $ARGUMENTS. Write unit tests for backend: [from step 4] and frontend: [from step 5]. Add integration tests for API endpoints, E2E tests for critical user journeys, performance tests for scalability validation. Ensure minimum 80% code coverage."
104   - Expected output: Test suites with unit, integration, E2E, and performance tests
105   - Context: Implementation code, acceptance criteria, test requirements
106 
1078. **Security Validation**
108   - Use Task tool with subagent_type="security-scanning::security-auditor"
109   - Prompt: "Perform security testing for: $ARGUMENTS. Review implementation: [include backend and frontend from steps 4-5]. Run OWASP checks, penetration testing, dependency scanning, and compliance validation. Verify data encryption, authentication, and authorization."
110   - Expected output: Security test results, vulnerability report, remediation actions
111   - Context: Implementation code, security requirements
112 
1139. **Performance Optimization**
114   - Use Task tool with subagent_type="application-performance::performance-engineer"
115   - Prompt: "Optimize performance for: $ARGUMENTS. Analyze backend services: [from step 4] and frontend: [from step 5]. Profile code, optimize queries, implement caching, reduce bundle sizes, improve load times. Set up performance budgets and monitoring."
116   - Expected output: Performance improvements, optimization report, performance metrics
117   - Context: Implementation code, performance requirements
118 
119## Phase 4: Deployment & Monitoring
120 
12110. **Deployment Strategy & Pipeline**
122    - Use Task tool with subagent_type="deployment-strategies::deployment-engineer"
123    - Prompt: "Prepare deployment for: $ARGUMENTS. Create CI/CD pipeline with automated tests: [from step 7]. Configure feature flags for gradual rollout, implement blue-green deployment, set up rollback procedures. Create deployment runbook and rollback plan."
124    - Expected output: CI/CD pipeline, deployment configuration, rollback procedures
125    - Context: Test suites, infrastructure requirements, deployment strategy
126 
12711. **Observability & Monitoring**
128    - Use Task tool with subagent_type="observability-monitoring::observability-engineer"
129    - Prompt: "Set up observability for: $ARGUMENTS. Implement distributed tracing, custom metrics, error tracking, and alerting. Create dashboards for feature usage, performance metrics, error rates, and business KPIs. Set up SLOs/SLIs with automated alerts."
130    - Expected output: Monitoring dashboards, alerts, SLO definitions, observability infrastructure
131    - Context: Feature implementation, success metrics, operational requirements
132 
13312. **Documentation & Knowledge Transfer**
134    - Use Task tool with subagent_type="documentation-generation::docs-architect"
135    - Prompt: "Generate comprehensive documentation for: $ARGUMENTS. Create API documentation, user guides, deployment guides, troubleshooting runbooks. Include architecture diagrams, data flow diagrams, and integration guides. Generate automated changelog from commits."
136    - Expected output: API docs, user guides, runbooks, architecture documentation
137    - Context: All previous phases' outputs
138 
139## Execution Parameters
140 
141### Required Parameters
142 
143- **--feature**: Feature name and description
144- **--methodology**: Development approach (traditional|tdd|bdd|ddd)
145- **--complexity**: Feature complexity level (simple|medium|complex|epic)
146 
147### Optional Parameters
148 
149- **--deployment-strategy**: Deployment approach (direct|canary|feature-flag|blue-green|a-b-test)
150- **--test-coverage-min**: Minimum test coverage threshold (default: 80%)
151- **--performance-budget**: Performance requirements (e.g., <200ms response time)
152- **--rollout-percentage**: Initial rollout percentage for gradual deployment (default: 5%)
153- **--feature-flag-service**: Feature flag provider (launchdarkly|split|unleash|custom)
154- **--analytics-platform**: Analytics integration (segment|amplitude|mixpanel|custom)
155- **--monitoring-stack**: Observability tools (datadog|newrelic|grafana|custom)
156 
157## Success Criteria
158 
159- All acceptance criteria from business requirements are met
160- Test coverage exceeds minimum threshold (80% default)
161- Security scan shows no critical vulnerabilities
162- Performance meets defined budgets and SLOs
163- Feature flags configured for controlled rollout
164- Monitoring and alerting fully operational
165- Documentation complete and approved
166- Successful deployment to production with rollback capability
167- Product analytics tracking feature usage
168- A/B test metrics configured (if applicable)
169 
170## Rollback Strategy
171 
172If issues arise during or after deployment:
173 
1741. Immediate feature flag disable (< 1 minute)
1752. Blue-green traffic switch (< 5 minutes)
1763. Full deployment rollback via CI/CD (< 15 minutes)
1774. Database migration rollback if needed (coordinate with data team)
1785. Incident post-mortem and fixes before re-deployment
179 
180Feature description: $ARGUMENTS
181