planner

A staged deployment plan is generated by providing a concise project description. The planner detects whether the project is Greenfield or Brownfield and builds a multi-stage Plan/ directory covering local design, coding, testing, cloud deploy, and validation steps.

Session resumability works by storing captured sensitive values in a .env.secrets file. Plan files track milestone progress without exposing credentials, enabling you to pause and resume deployment execution across multiple sessions seamlessly.

You need a Greenfield or Brownfield deployment plan depending on your project's existing state. The planner detects this automatically from user input and app.yaml to tailor the Plan/ directory structure for new versus existing projects.

Yes, you can use a staged plan for existing App Platform projects. The planner detects Brownfield state from app.yaml and generates a tailored Plan/ directory with appropriate milestones and checklists for existing infrastructure.

The best way to track multi-stage deployment progress is through generated Plan files that record milestone completion. Sensitive values are kept separate in .env.secrets, ensuring progress tracking does not expose credentials.