Orchestrate end-to-end feature development from requirements to production deployment:
[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.]
epic: Major architectural changes, multiple teams (2+ weeks)
simple: 单一服务，集成度低（1-2天）
medium: 多服务，中等集成度（3-5天）
complex: 跨领域，高集成度（1-2周）
epic: 重大架构变更，涉及多团队（2周以上）
Deployment Strategy
部署策略
direct: Immediate rollout to all users
canary: Gradual rollout starting with 5% of traffic
feature-flag: Controlled activation via feature toggles
blue-green: Zero-downtime deployment with instant rollback
a-b-test: Split traffic for experimentation and metrics
direct: 立即全量发布给所有用户
canary: 渐进式发布，初始流量占比5%
feature-flag: 通过功能开关控制激活
blue-green: 零停机部署，支持即时回滚
a-b-test: 流量拆分用于实验和指标分析
Phase 1: Discovery & Requirements Planning
阶段1：需求发现与规划
Business Analysis & Requirements
Use Task tool with subagent_type="business-analytics::business-analyst"
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."
Expected output: Requirements document with user stories, success metrics, risk assessment
Context: Initial feature request and business context
Technical Architecture Design
Use Task tool with subagent_type="comprehensive-review::architect-review"
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."
Expected output: Technical design document with architecture diagrams, API specifications, data models
Context: Business requirements, existing system architecture
Feasibility & Risk Assessment
Use Task tool with subagent_type="security-scanning::security-auditor"
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."
Use Task tool with subagent_type="backend-architect"
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."
Expected output: Backend services with APIs, business logic, database integration, feature flags
Context: Technical design, API contracts, data models
Frontend Implementation
Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"
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."
Expected output: Frontend components with API integration, state management, analytics
Context: Backend APIs, UI/UX designs, user stories
Data Pipeline & Integration
Use Task tool with subagent_type="data-engineering::data-engineer"
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."
Expected output: Data pipelines, analytics events, data quality checks
Context: Data requirements, analytics needs, existing data infrastructure
Use Task tool with subagent_type="unit-testing::test-automator"
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."
Expected output: Test suites with unit, integration, E2E, and performance tests
Context: Implementation code, acceptance criteria, test requirements
Security Validation
Use Task tool with subagent_type="security-scanning::security-auditor"
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."
Expected output: Security test results, vulnerability report, remediation actions
Context: Test suites, infrastructure requirements, deployment strategy
Observability & Monitoring
Use Task tool with subagent_type="observability-monitoring::observability-engineer"
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."
Use Task tool with subagent_type="documentation-generation::docs-architect"
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."
Expected output: API docs, user guides, runbooks, architecture documentation