deployment

Deployment

Dependency specification

#[[file:../rules/review-base.md]] #[[file:../rules/git-workflow.md]] #[[file:../rules/project-structure.md]]

Purpose

Confirm the deployment plan, output the deployment document, and ensure the project can be delivered and operated stably.

Input

• Code: code that has passed testing
• Environment information: servers, CI/CD platforms, etc. provided by the developer

Steps

For each step, output the title first, then output the result

• Deployment communication:
  • Collect preferences: ask the developer about deployment method preferences
  • Provide options: provide available options (such as Docker, CI/CD platforms, manual deployment, etc.) with reasons
  • Confirm the plan: confirmed by the developer
• Write to the document: write into the deployment document according to the output requirements (the path follows project-structure document storage specification)
• Execute review: comply with review-base, and delivery is complete after passing
• Submit: after review passes, submit according to git-workflow Submit: after review passes, submit according to git-workflow

Output

• Deployment document: build steps, deployment commands, environment variable descriptions, health checks, common troubleshooting

Review checklist

• Deployment method: confirmed (environment, CI/CD, rollback plan)
• Complete document: includes build steps, deployment commands, environment variables, health checks, common issues
• Environment variables: no hardcoded sensitive information

Phase end

All phases have been completed, output a deployment document summary, and inform the developer that project delivery is complete.