Skip to content
Raindrop Developer Hub

New Application Workflow

The new application workflow is a fully automated, comprehensive process that takes you from initial concept to fully deployed infrastructure. Once you initiate the workflow, Claude Code handles everything automatically - you simply answer questions when prompted. Each phase builds on the previous one, ensuring nothing gets missed and the final result is production-ready.

Workflow Overview

The workflow consists of 9 sequential phases, each with specific MCP tools that guide Claude Code through the process. Your only role is to kick off the workflow and answer Claude’s questions when prompted - everything else is automated:

AI-Guided Planning
💡 Idea → 🎯 Init → 👥 Team → 📋 Requirements
↓
Automated
🏗️ Architecture → 🗄️ Database → 📚 Docs → 💻 Code → 🧪 Test → 🚀 Deploy
↓
Result
🌐 Live Application
  1. Session Initialization (login)
  2. Team Setup (set_team) - Optional
  3. Requirements Definition (prd_step)
  4. Database Design (prisma_step) - If SQL databases needed
  5. Documentation Retrieval (documentation_step)
  6. Code Implementation (code_step)
  7. Testing & Validation (tests_step)
  8. Deployment (deployment_step)
  9. Endpoint Verification (endpoint_test_step)

What You Get At Each Phase

Phase 1: Session Initialization (login)

What You Achieve: You get a development session with unique tracking that enables team collaboration and resumption at any time. A permanent session ID acts as your project identity throughout development.

Your Input: None - just initiate the workflow

Phase 2: Team Setup (set_team) - Optional

What You Achieve: Team members receive email invitations and can join your development session. Everyone gets shared access to the same project context and can contribute at any phase.

Your Input: Team member emails and roles

Phase 3: Requirements Definition (prd_step)

What You Achieve: You get a comprehensive Product Requirements Document that captures every aspect of your application. Claude acts as an expert product manager, asking the right questions to uncover requirements you might not have considered.

Your Input:

  • Description of your application idea
  • Answers to clarifying questions about functionality
  • Final approval of the PRD

Phase 4: Architecture Generation

What You Achieve: Your application’s complete technical architecture is designed and your development environment is set up. You receive a Git branch, project structure, and infrastructure blueprint ready for implementation.

Your Input: Application name when prompted

Phase 5: Database Design (prisma_step) - If Needed

What You Achieve: You get production-ready database schemas with proper relationships, type safety, and migration support. Your data models are optimized and ready for scale.

Your Input: None - automated based on your PRD

Phase 6: Documentation Access (documentation_step)

What You Achieve: All technical documentation needed for your specific architecture is gathered and organized. Claude receives the knowledge needed to implement your exact requirements correctly.

Your Input: None - automated based on your architecture

Phase 7: Complete Implementation (code_step)

What You Achieve: Your entire application is implemented with production-quality code. All components work together seamlessly with proper error handling, security, and performance optimization.

Your Input: None - automated based on your PRD and architecture

Phase 8: Quality Assurance (tests_step)

What You Achieve: You gain confidence that your application will work correctly when deployed. All code compiles, types are safe, and components integrate properly.

Your Input: None - automated validation

Phase 9: Live Deployment (deployment_step)

What You Achieve: Your application is running live on cloud infrastructure with real databases, APIs, and domains. Everything is production-ready and accessible via public URLs.

Your Input: None - automated deployment

Phase 10: Production Verification (endpoint_test_step)

What You Achieve: You receive confirmation that every feature works correctly in production. Your application is thoroughly tested and ready for users.

Your Input: None - automated testing

State Management Throughout Workflow

Session State Tracking:

  • Each phase updates the workflow state (e.g., session_started → team_set → prd_created)
  • State determines which MCP tool can be called next
  • Prevents skipping phases or creating incomplete applications
  • Enables resumption from any point using reattach_to_session

Context Preservation:

  • PRD requirements maintained throughout all phases
  • Architectural decisions propagated to implementation
  • Team access and permissions preserved
  • All generated artifacts stored and versioned

Quality Gates:

  • Each phase must complete successfully before proceeding
  • Built-in validation prevents broken deployments
  • Automatic error recovery and retry mechanisms
  • Manual intervention points for approval and review

The new application workflow transforms Claude Code from a coding assistant into a complete application development platform, ensuring every project results in a fully functional, deployed application ready for production use.