home/productivity/sp-03-0-spec-delta

SP 03 0 SPEC DELTA

GPTClaudeDeepSeek··1,301 copies·updated 2026-07-14
sp-03-0-spec-delta.prompt
# Stage 3-0 Prompt: Review Existing Specification (Product Mode Only)

## CONTEXT

This is a **product-mode-only activity** performed in **all releases after Release 2.0** (Release 1.0 starts from empty spec in project mode).

Read the existing SPECIFICATIONS.md and compare it with new requirements to organize changes (new/modified/removed).

**Location:** First activity of Stage 3 (Stage 3-0 is product mode only)

---

## OBJECTIVE

Achieve the following:

1. ✅ Load existing SPECIFICATIONS.md and understand structure
2. ✅ Map new requirements to existing Sub-Projects/Phases
3. ✅ Identify new Sub-Projects (items not in existing)
4. ✅ Identify where existing Sub-Projects need expansion (add new Phases)
5. ✅ Identify existing Phases needing modification (changes)
6. ✅ Review architecture and Adjacent Code impact
7. ✅ Generate `SPEC_DELTA.md` (foundation for Stage 3 specification writing)

**Validation Criteria:** `SPEC_DELTA.md` must specify all new/modified/disposed Phases, and Adjacent Code impact must be analyzed.

---

## CONSTRAINTS

### MUST DO
- Read entire `docs/current/02_SPECIFICATIONS.md` (Stage 3's input baseline)
- Read `releases/v[N-1].N/02_SPECIFICATIONS.md` (previous release baseline)
- Read `00_RELEASE_PLAN.md` (new scope)
- Read `00_BACKLOG_TRIAGE.md` (transferred Backlog items)
- Map new requirements 1:1 to existing specification
- Analyze Adjacent Code impact (new Phases affecting existing Phases)

### MUST NOT DO
- Do not modify existing SPECIFICATIONS.md (analysis only)
- Do not write new Phases yet (generate SPEC_DELTA.md only)
- Do not skip Adjacent Code analysis (important)
- Do not propose new technology adoption without reviewing compatibility with existing architecture

### SCOPE
- Read-only: Analyze existing SPECIFICATIONS.md
- Write: Generate SPEC_DELTA.md (based on analysis)
- Coverage: 100% tracking of new/modified/disposed items

---

## INPUT ARTIFACTS

| File | Source | Description |
|------|--------|------|
| `docs/current/02_SPECIFICATIONS.md` | `docs/current/` | **Current latest cumulative spec** |
| `releases/v[N-1].N/02_SPECIFICATIONS.md` | Previous release | Previous release version (for comparison) |
| `docs/current/Architecture_Design.md` | `docs/current/` | Existing architecture structure |
| `00_RELEASE_PLAN.md` | Current release | New scope (Sub-Project/Phase count) |
| `00_BACKLOG_TRIAGE.md` | Current release | Transferred Backlog items (SP/Phase mapping) |
| New requirements | Human chat input | Release [N.N] objectives + feature requests |

---

## OUTPUT ARTIFACTS

| Filename | Path | Description |
|--------|------|------|
| `SPEC_DELTA.md` | `releases/v[N].N/` | Change analysis (new/modified/disposed Phases) |

---

## EXECUTION RULES

### Activity 3-0-1: Load Existing SPECIFICATIONS.md

**Input:** `docs/current/02_SPECIFICATIONS.md` (latest cumulative spec)

**Extract Items:**

when to use it

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

productivitycommunitydeveloper

source

SunnyBan101/spec-contract-v5 · no explicit license