deploy

Generate a deployment checklist by providing a target service, environment, and optional rollout strategy to automate pre-flight validation, rollout planning, and verification steps into a structured note.

Pre-flight validation is the automated analysis of code changes, manifests, and environment configurations to document required infrastructure checks and dependencies before executing a production release.

Yes, specify blue-green, canary, or rolling as an optional strategy preference to tailor the deployment plan, capturing necessary checks for feature flags, migrations, and rollback procedures.

Plan a canary rollout by setting the target service and environment, then selecting canary as the strategy to generate a tailored plan covering pre-flight checks, incremental rollout, and post-deployment verification.

Yes, the deployment planner analyzes your target scope and configurations to produce an Obsidian-ready deployment note, structuring the pre-flight checks and rollout strategy for immediate publishing.

You need to specify the target service, environment, and release scope, ensuring your code changes and environment configurations are available for the analysis to infer required infrastructure checks.