home/roleplay/sp-04-2-checkpoint

SP 04 2 CHECKPOINT

GPTClaudeGemini··1,192 copies·updated 2026-07-14
sp-04-2-checkpoint.prompt
# Stage 4-2 Prompt: Checkpoint and Plan Lock Verification

> Spec-Contract v5.0 | Cycle: Development Planning Verification
> Stage Prompt ID: SP-04-2

---

## CONTEXT

- **Current Location:** Development Cycle > Stage 4-2
- **Previous Stage:** Stage 4-1 Contract Writing (Output: `03_PROMPT_CONTRACTS.md`)
- **Next Stage:** Stage 4-3 Code Generation (Output: project implementation code)
- **Purpose:** Finalize Prompt Contract and set Git checkpoint

---

## OBJECTIVE

**Final validate** `03_PROMPT_CONTRACTS.md` and record **checkpoint commit** in Git so that Stage 4-3 code generation starts from clear criteria.

**Success Criteria:**
1. All Contracts completely include 5-Clause structure
2. "think hard" quantitative criteria correctly applied
3. Verify FC-00a~e automated validation CLI commands from COMMON_FAILURE_CONDITIONS.md
4. Git checkpoint commit completed (`[CHECKPOINT-Stage4-2]` message)

---

## CONSTRAINTS

**MUST DO:**
- [ ] Review all Contracts in `03_PROMPT_CONTRACTS.md`
  - Is GOAL verifiable within 1 minute?
  - Are FORMAT and ADJACENT CODE clear?
  - Do all include FC-00a~e?
  - Is "think hard" determination quantitative?
- [ ] Verify FC-00a~e definitions in COMMON_FAILURE_CONDITIONS.md
  - Specify automated validation CLI command for each FC
- [ ] Final verification of Plan Lock Directive (PLAN_LOCK_DIRECTIVE.md)
- [ ] Git checkpoint commit:
  ```bash
  git add -A
  git commit -m "[CHECKPOINT-Stage4-2] Prompt Contracts v5.0 finalized with Plan Lock"
  ```
- [ ] Perform handshake protocol (verify CLAUDE.md in new session)

**MUST NOT DO:**
- [ ] Do not modify Contract contents in this stage (already finalized)
- [ ] Do not add additional Phases to Contracts
- [ ] Do not add/modify FAILURE CONDITIONS

**SCOPE:**
- Review and final verification of `03_PROMPT_CONTRACTS.md`
- Verify FC-00a~e automated validation CLI commands in `COMMON_FAILURE_CONDITIONS.md`
- Git checkpoint commit

---

## INPUT ARTIFACTS

| ID | File Path | Reference Content |
|----|----------|----------|
| A-301 | `/docs/03_PROMPT_CONTRACTS.md` | Output from Stage 4-1 (validation target) |
| A-302 | `/docs/COMMON_FAILURE_CONDITIONS.md` | FC-00a~e definitions + automated validation CLI |
| A-303 | `/methodology/v5/PLAN_LOCK_DIRECTIVE.md` | Development Cycle Plan Lock rules |
| A-304 | `/CLAUDE.md` | Project hard boundaries (verify FC-00a) |

---

## OUTPUT ARTIFACTS

| ID | File Path | Format | Grade | Description |
|----|----------|--------|:----:|------|
| A-305 | `docs/03_PROMPT_CONTRACTS.md` (validation complete) | 📄 MD | 🏛️ | Final confirmed Contract collection |
| A-306 | `docs/COMMON_FAILURE_CONDITIONS.md` | 📄 MD | 🏛️ | FC-00a~e definitions + automated validation CLI commands |
| A-307 | (Git checkpoint) | 🔖 | ⚡ | Commit message: `[CHECKPOINT-Stage4-2]` |

---

## EXECUTION RULES

### 1. Final Contract Validation (Checklist)

Reverify following items for each Contract:

when to use it

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