SP 00 RELEASE PLANNING
# Stage 0 Prompt: Release Planning (Product Mode Only)
## CONTEXT
This Stage is performed in **all releases after Release 2.0** (Release 1.0 starts from Stage 1 in project mode).
After the previous release is completed, this is the stage where we review past results and determine the new scope for planning a new release.
**Location:** Starting point of the product lifecycle
---
## OBJECTIVE
Achieve the following:
1. ✅ Comprehensive evaluation of the previous release's deployment status, quality, and feedback
2. ✅ Determine priority-based transfer/carryover/disposal of remaining Backlog items
3. ✅ Collect new requirements list
4. ✅ Automatically determine if Stage 1~2 re-execution is necessary (based on technology stack changes)
5. ✅ Confirm release scope, expected number of Phases, and execution path
**Validation Criteria:** `00_RELEASE_PLAN.md` must specify the release name, objectives, scope (number of items), Stage execution path, and expected number of Phases.
---
## CONSTRAINTS
### MUST DO
- Read previous release's `11_DEPLOY_LOG.md`, `07_EVALUATION_REPORT.md`, `08_BACKLOG.md` (required)
- Extract new requirements and release objectives from human input
- Execute activities 0-1 through 0-5 sequentially
- Generate `00_RELEASE_REVIEW.md`, `00_STAGE_SKIP_DECISION.md`, `00_RELEASE_PLAN.md`
### MUST NOT DO
- Do not start Stage 1~3 before completing Stage 0
- Do not finalize "recommendations" without human approval (determinations must be evidence-based only)
- Do not carry over Backlog P0 unresolved items externally
### SCOPE
- Read previous release artifacts
- Generate 3 decision-making output artifacts
- Establish new release plan
---
## INPUT ARTIFACTS
| ID | File Path | Reference Content |
|----|----------|----------|
| A-111 | `releases/v[N-1].N/11_DEPLOY_LOG.md` | Previous release deployment log |
| A-070 | `releases/v[N-1].N/07_EVALUATION_REPORT.md` | Previous release quality evaluation |
| A-080 | `releases/v[N-1].N/08_BACKLOG.md` | Previous release unresolved Backlog |
| A-081 | `releases/v[N-1].N/08_ERROR_LOG.md` | Previous release unfixed defects (if any) |
| — | Human input: Release [N.N] Requirements | New features, improvement objectives |
---
## OUTPUT ARTIFACTS
| ID | File Path | Format | Grade | Description |
|----|----------|--------|:----:|------|
| A-001 | `releases/v[N].N/00_RELEASE_REVIEW.md` | 📄 MD | ⚡ | Comprehensive review of previous deployment/quality/feedback |
| A-002 | `releases/v[N].N/00_STAGE_SKIP_DECISION.md` | 📄 MD | ⚡ | Stage 1~2 execution determination + rationale |
| A-003 | `releases/v[N].N/00_RELEASE_PLAN.md` | 📄 MD | ⚡ | Release objectives/scope/Phases/timeline |
---
## EXECUTION RULES
### Activity 0-1: Review Previous Release
**Input:** `11_DEPLOY_LOG.md`, `07_EVALUATION_REPORT.md`, `08_BACKLOG.md`
**Output:** `00_RELEASE_REVIEW.md`when to use it
Community prompt sourced from the open-source GitHub repo SunnyBan101/spec-contract-v5 (no explicit license). A "SP 00 RELEASE PLANNING" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
SunnyBan101/spec-contract-v5 · no explicit license