Orchestrate End-to-End Software Development

Development Workflow Bundle is a consolidated workflow for end-to-end software development across web, mobile, and backend, orchestrating a sequence of named sub-skills from scaffolding to deployment rather than doing the work itself.

It runs seven phases, each naming the specific skills to invoke: project setup and scaffolding (app-builder, senior-fullstack, environment-setup-guide, concise-planning - choosing a project type and stack, scaffolding structure, configuring the dev environment and CI/CD); frontend development (frontend-developer, frontend-design, react-patterns, typescript-pro, tailwind-patterns, nextjs-app-router-patterns - component architecture, state management, routing, styling, responsive design); backend development (backend-architect, backend-dev-guidelines, nodejs-backend-patterns, fastapi-pro, api-design-principles, auth-implementation-patterns - API architecture, REST/GraphQL endpoints, database connections, auth, middleware, error handling); database development (database-architect, database-design, prisma-expert, postgresql, neon-postgres - schema design, migrations, ORM setup, query optimization, connection pooling); testing (test-driven-development, javascript-testing-patterns, python-testing-patterns, e2e-testing-patterns, playwright-skill - unit, integration, and E2E tests plus CI test runners and coverage targets); code quality and review (code-reviewer, clean-code, lint-and-validate, security-scanning-security-sast - linting, code review, quality fixes, security scans); and build and deployment (deployment-engineer, docker-expert, vercel-deployment, github-actions-templates, cicd-automation-workflow-automate - Dockerfiles, build pipelines, deployment workflows, production deploy).

It also maps out technology-specific skill sets - React/Next.js, Python/FastAPI, Node.js/Express, full-stack, and mobile (React Native/Flutter/iOS) - and a quality-gate checklist to clear before moving to the next phase: all tests passing, code review completed, security scan passed, linting clean, and documentation updated.

Use it as a phase map for a new web/mobile/full-stack build, a feature addition to an existing app, or a legacy modernization effort, when you want a structured sequence of which specialized skill to invoke at each stage rather than working ad hoc. It is not itself an implementation skill - it names other skills to do the actual scaffolding, coding, testing, and deploying, so using it well means having (or invoking) those named skills, not expecting this bundle to write code directly.

Input is the kind of development task (new build, feature, refactor) and its target stack. Output is a phase-by-phase plan naming which skill to invoke next, the concrete actions for that phase, and a quality gate to clear before advancing.

It orchestrates a large named set of other skills - app-builder, frontend-developer, backend-architect, database-architect, test-driven-development, code-reviewer, docker-expert, vercel-deployment, github-actions-templates, and more - and cross-references sibling workflow bundles for WordPress-specific development, security auditing, comprehensive QA, and documentation generation.

Developers and teams who want a structured, phase-based map through a full development lifecycle - setup, frontend, backend, database, testing, review, and deployment - naming the right specialized skill for each stage instead of guessing what to reach for next.