home/roleplay/sp-09-design-reflect-2

SP 09 DESIGN REFLECT

GPTClaudeGemini··887 copies·updated 2026-07-14
sp-09-design-reflect-2.prompt
# Stage 9 Prompt: Design Reflection + Re-execution Decision

> Spec-Contract v5.0 | Cycle: Assessment
> Stage Prompt ID: SP-09

---

## CONTEXT

- **Current Location:** Assessment Cycle > Stage 9 (Design Reflection + Re-execution Decision)
- **Previous Stage:** Stage 8 (Backlog + Error Log Identification) — Artifacts: 08_BACKLOG.md, 08_ERROR_LOG.md
- **Next Stage:** Stage 10 (Human Review) or Stage 4-2 (Re-entry)
- **Product Mode:** Applicable

---

## OBJECTIVE

**Goals to achieve in this Stage:**

Review **Error Log and Backlog classified in Stage 8 to make final deployment decision**, and **provide resolution methods for P0/Critical Errors or decide re-entry to Stage 4-2**.

### Success Criteria:

1. **Error Classification Verification:** Critical 0, High 1~2 (immediately manageable level) or resolved
2. **Re-execution Decision:**
   - Critical Error 0 → Deployment approved (proceed to Stage 10)
   - High Error exists and resolvable within 1 week → Conditional deployment (verify after resolution)
   - Unresolvable Error → Stage 4-2 re-entry (design change required)
3. **Design Change Necessity Decision:** If P0 Backlog found, design review and modification plan established
4. **Repetition Limit Management:** Forbid >3 Error re-occurrences, >2 Backlog carryovers (escalation required)

---

## CONSTRAINTS

### MUST DO:

- [ ] **9-1 Error Re-review:** Re-confirm severity of all items in A-081 ERROR_LOG
- [ ] **9-2 Deployment Decision:** Critical 0 → Approve deployment, High exists → Conditional or re-entry
- [ ] **9-3 Design Change Decision:** Check if P0 Backlog requires SPECIFICATIONS.md modification
- [ ] **9-4 Re-entry Plan:** If Stage 4-2 re-entry needed, specify target Phases and scope
- [ ] **9-5 Repetition Limit Confirmation:** Verify current repetition count, escalate if limit exceeded
- [ ] **09_ITERATION_PLAN.md Writing** (only if re-entry needed)

### MUST NOT DO:

- [ ] Do not force "conditional deployment" when undeployable
- [ ] Do not arbitrarily change Error classification (e.g., "High → Medium downgrade" ❌)
- [ ] Do not ignore repetition limits and continue re-entry (escalation required)
- [ ] Do not skip deployment with P0 Backlog (design review required)

### SCOPE:

- Modification Range: **A-090 (09_ITERATION_PLAN.md)** (if re-entry), **A-091~093** (design modifications, conditional)
- Reference Range: A-080 (BACKLOG), A-081 (ERROR_LOG), A-048 (SPECIFICATIONS), A-044 (ARCHITECTURE)
- **After Stage 9:** Stage 10 (deployment approval) or Stage 4-2 (re-entry)

---

## INPUT ARTIFACTS

| ID | File Path | Reference Content |
|----|----------|-------------------|
| A-081 | `docs/08_ERROR_LOG.md` | Error items (severity, fix direction) |
| A-080 | `docs/08_BACKLOG.md` | Backlog items (priority, effort) |
| A-062 | `docs/04_VERIFICATION_LOG.md` | Previous iteration records (re-entry history) |
| A-048 | `docs/02_SPECIFICATIONS.md` | User Story status |
| A-044 | `docs/Architecture_Design.md` | Architecture (design change review) |

---

## OUTPUT ARTIFACTS

| ID | File Path | Format | Grade | Description |
|----|----------|--------|:----:|-------------|
| A-090 | `docs/09_ITERATION_PLAN.md` | 📄 MD | ⚡ | Re-execution scope, target Phases, estimated effort, related document updates (re-entry only) |
| A-091 | `docs/02_SPECIFICATIONS.md` (modified) | 📄 MD | 📐 | SPECIFICATIONS update (P0 Backlog reflection, conditional) |
| A-092 | `docs/03_PROMPT_CONTRACTS.md` (added) | 📄 MD | 📐 | New Phase Contract (if design change required) |
| A-093 | `docs/Architecture_Design.md` (modified) | 📄 MD | 📐 | Architecture update (structural change, conditional) |

---

## EXECUTION RULES

### 1. Session Rules:

- **Single Session Execution:** Stage 9 completed in one Agent session

### 2. Decision Logic (Core):

when to use it

Community prompt sourced from the open-source GitHub repo SunnyBan101/spec-contract-v5 (no explicit license). A "SP 09 DESIGN REFLECT" 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