SP 00 3 STAGE SKIP DECISION
# Stage 0-3 Prompt: Automatic Stage 1~2 Execution Determination
## CONTEXT
This stage determines whether to re-execute Stage 1 (Project Foundation Setup) and Stage 2 (Research) in a new release.
Release 1.0 (initial) always executes Stage 1~2, but Release 2.0 onward is conditionally executed based on technology stack changes.
---
## OBJECTIVE
Compare new requirements with the existing technology stack and **automatically determine** whether Stage 1 and Stage 2 need to be executed.
**Validation Criteria:**
- Stage 1 determination: Execute/Skip specified + rationale
- Stage 2 determination: Execute/Partial execution/Skip specified + rationale
- Next Stage decision: Enter Stage 3 or Stage 1/2
---
## CONSTRAINTS
### MUST DO
- Compare new requirements (collected in 0-3) with existing CLAUDE.md
- Automatically classify based on 5 determination criteria
- Specify rationale at technical level (no abstract descriptions)
- Check dependencies (e.g., GraphQL adoption → Choose Apollo Server)
### MUST NOT DO
- Subjective determination (execute without rationale)
- Excessive scope expansion (execute only what is necessary)
- Change already confirmed technology stack
### SCOPE
- Read: New requirements, existing CLAUDE.md
- Write: `00_STAGE_SKIP_DECISION.md` (determination table + rationale)
- Coverage: Stage 1, Stage 2 determination only (other Stages are always executed)
---
## INPUT ARTIFACTS
| File | Source | Description |
|------|--------|------|
| New requirements | Human chat input | Release [N.N] objectives + feature requests |
| `current/CLAUDE.md` | `docs/current/` | Existing technology stack, hard boundaries |
| `releases/v[N-1].N/02_SPECIFICATIONS.md` | Previous release | Existing functional architecture |
---
## OUTPUT ARTIFACTS
| Filename | Path | Format |
|--------|------|--------|
| `00_STAGE_SKIP_DECISION.md` | `releases/v[N].N/` | Markdown (determination table) |
---
## EXECUTION RULES
### Determination Criterion 1: Technology Stack Changes (Stage 1)
**Stage 1 Re-execution Condition:**when to use it
Community prompt sourced from the open-source GitHub repo SunnyBan101/spec-contract-v5 (no explicit license). A "SP 00 3 STAGE SKIP DECISION" 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
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar