full-stack-orchestration-full-stack-feature

Full-Stack Orchestration Feature Development

Skill Overview

Coordinates multiple specialized agents to deliver full-stack feature development from architecture design through production deployment. Uses an API-first approach to enable parallel delivery of both front-end and back-end.

Suitable Scenarios

End-to-end development of new features

Build a complete full-stack feature from scratch, covering the entire workflow: database design, back-end services, front-end UI, test validation, and deployment go-live.

Architecture upgrade for large full-stack projects

Requires systematic cross-layer architectural design, standardized development processes, and the establishment of automated testing and deployment systems for enterprise-level projects.

Front-end and back-end team collaboration

In multi-role collaboration scenarios, development driven by API contracts ensures that front-end and back-end progress in parallel and integrates seamlessly.

Core Capabilities

Four-phase architecture and design workflow

- Database architecture design (ER diagrams, indexing strategy, migration plan)
- Back-end service architecture (OpenAPI specifications, authentication and authorization, caching strategy)
- Front-end component architecture (component tree, state management, accessibility)
- Infrastructure and CI/CD (containerization, orchestration, monitoring)

Parallel implementation and integration testing

- Back-end service implementation (REST/GraphQL, validation, logging, observability)
- Front-end component implementation (React/Next.js, Storybook, WCAG 2.1)
- Database optimization (migration scripts, query optimization, security constraints)
- Contract testing (Pact/Dredd), E2E testing (Playwright/Cypress)

Security audits and operations delivery

- OWASP Top 10 security audit, vulnerability scanning, penetration testing
- Observability stack (OpenTelemetry, Prometheus, ELK)
- Performance optimization (caching strategy, CDN, code splitting)
- Blue-green deployments, feature flags, SLI/SLO definition

Common Questions

What types of projects are suitable for full-stack orchestration feature development?

Suitable for medium to large projects that need to build complete features from scratch—especially scenarios where front-end and back-end must work closely together and have clear API contract requirements. For simple CRUD operations or small utility projects, this approach may be too heavy.

What are the advantages of API-first development?

API-first allows the team to define service contracts first, enabling parallel development on both sides and reducing dependency wait times. Contract testing ensures the implementation matches the design, lowering integration risk. OpenAPI specifications can also automatically generate documentation and SDKs.

How do you coordinate parallel front-end and back-end development?

Use API contracts (OpenAPI/GraphQL Schema) as the collaboration foundation: back-end focuses on business logic and the data layer, while front-end develops the UI using mocked data. Contract testing (e.g., Pact) verifies interface compatibility, and integration testing merges and validates everything. Use feature flags to control gradual rollout (gray releases).

What tech stack is needed for full-stack development?

Supports multiple combinations of technologies, such as React/FastAPI/PostgreSQL, Next.js/Django/MongoDB, Vue/Node.js/MySQL, etc. The choice depends on team skills and project needs, but the core workflow (architecture design, contract testing, CI/CD) remains consistent.

How do you implement front-end/back-end contract testing?

Write consumer-driven contract tests using tools like Pact and Dredd. The front-end defines the expected API response formats, and the back-end validates whether they satisfy the contract. Integrate contract tests into the CI/CD pipeline to ensure that code changes do not break existing API agreements.

How do you conduct security audits for full-stack projects?

Cover multiple dimensions: API security (authentication/authorization, rate limiting), code scanning (OWASP Top 10 vulnerabilities), front-end security (XSS, CSRF protection), dependency auditing (npm audit, pip-audit), and infrastructure security (key management, network isolation). Penetration testing is recommended periodically.

How should a CI/CD pipeline be designed?

A typical pipeline includes: code checks → unit tests → contract tests → build images → integration tests → security scans → deploy to staging → E2E tests → production deployment. Each stage should include quality gates; if a stage fails, it blocks the pipeline. Supports blue-green deployments or canary releases.

How do you achieve zero-downtime deployments?

Use blue-green deployments to maintain two environments: after deploying the new version, switch traffic; or use canary releases to gradually increase traffic. With health checks and automatic rollback mechanisms, failures can be recovered quickly. Database migrations should be backward compatible to support rolling updates.