plan-release-cycle

Plan a structured software release cycle by defining strategy (calendar-based or feature-based), setting milestones with target dates, establishing feature freeze criteria, managing release candidates, defining go/no-go checklists, and documenting rollback plans. Produces a RELEASE-PLAN.md artifact that guides the team from development through release.

For most projects, a hybrid approach works well: set a target date with a defined scope, but allow a 1-2 week buffer. If scope is not met by the buffer deadline, defer remaining features.

Expected: Release strategy documented with rationale matching project context.

規劃軟體發布週期，包括里程碑、功能凍結、候選發布以及通過/不通過標準。涵蓋基於日曆和基於功能的發布策略。在開始規劃主要或次要版本發布、從臨時發布節奏過渡到結構化發布節奏、協調多個團隊或組件之間的發布、為受監管項目定義品質關卡或規劃項目的首次公開發布 (v1.0.0) 時使用。 來源：pjt222/development-guides。