SP 10 HUMAN REVIEW

# Stage 10 Prompt: Human Review (Final Human Review)

> Spec-Contract v5.0 | Cycle: Review/Assessment
> Stage Prompt ID: SP-10

---

## CONTEXT

- **Current Position:** Review/Assessment Cycle > Stage 10 (Human Review)
- **Previous Stage:** Stage 9 (Automated QA) — Output: A-070, A-071, A-072, A-073, A-074
- **Next Stage:** Stage 11 (Release) or Stage 9 (Re-QA)
- **Product Mode:** Applicable (End of assessment, deployment preparation phase)

---

## OBJECTIVE

A human conducts final review of the deliverables that passed Stage 9 to make a decision on deployment approval or additional Backlog registration.

Success Criteria:
1. All activities (10-1 ~ 10-6) completed: Review preparation → Checklist creation → Issue classification → Approval review → Final decision
2. Final output (A-100) generated: Checklist, issue classification, deployment approval explicitly stated
3. Branch decision: Critical issues present → Return to Stage 9 / None present → Proceed to Stage 11

---

## CONSTRAINTS

**MUST DO:**
- [ ] Review A-070 (EVALUATION_REPORT), A-071 (Human_Test_Scenarios), A-072 (Production_Readiness), A-073 (Security), A-074 (License) mandatory
- [ ] Input additional issues by referencing A-080 (BACKLOG), A-081 (ERROR_LOG)
- [ ] Complete review of all three review categories (functional, non-functional, documentation)
- [ ] Classify identified issues as Critical/Major/Minor and specify explicit remediation method
- [ ] Clearly specify deployment approval status and conditions (if any)

**MUST NOT DO:**
- [ ] Ignore auto QA failures already found in A-070 by claiming "human review" justification
- [ ] Misclassify minor issues (Minor) as Critical, forcing unnecessary Stage 9 return
- [ ] Leave deployment approval status "ambiguous" (YES/NO or conditional specification required)
- [ ] Terminate without generating output file (A-100)

**SCOPE:**
- Modification scope: Generate `A-100_10_HUMAN_REVIEW.md` only (existing outputs not modified)
- Review scope: Summarized review of all deliverables from previous 9 stages
- Target roles: Product Owner, QA Lead, Release Manager, Release Gatekeeper

---

## INPUT ARTIFACTS

| ID | File Path | Reference Content |
|----|-----------|----------|
| A-070 | `outputs/tms/docs/methodology/v5/artifacts/A-070_EVALUATION_REPORT.md` | QA results summary, overall TC pass rate, regression test results |
| A-071 | `outputs/tms/docs/methodology/v5/artifacts/A-071_Human_Test_Scenarios.md` | Manual test results, performance/security/compatibility metrics |
| A-072 | `outputs/tms/docs/methodology/v5/artifacts/A-072_Production_Readiness.md` | Production deployment readiness checklist |
| A-073 | `outputs/tms/docs/methodology/v5/artifacts/A-073_Security.md` | Security test results, vulnerability analysis |
| A-074 | `outputs/tms/docs/methodology/v5/artifacts/A-074_License.md` | License compliance verification |
| A-080 | `outputs/tms/docs/methodology/v5/artifacts/A-080_BACKLOG.md` | Unregistered requirements, improvement list |
| A-081 | `outputs/tms/docs/methodology/v5/artifacts/A-081_ERROR_LOG.md` | List of errors discovered before deployment |

---

## OUTPUT ARTIFACTS

| ID | File Path | Format | Priority | Description |
|----|-----------|--------|:----:|------|
| A-100 | `outputs/tms/docs/methodology/v5/artifacts/A-100_10_HUMAN_REVIEW.md` | 📊 Assessment | P0 | Human final review results: Checklist (✓/⚠/✗), issue classification table, deployment approval status, branch decision |

---

## EXECUTION RULES

### Activity 10-1: Review Preparation

**Responsible:** Product Owner / QA Lead

1. Review A-070 QA Summary Report
   - Verify overall TC pass rate
   - Review regression test results
   - Check performance metrics

2. Review A-071 Test Results & Metrics
   - Verify manual test results
   - Verify performance/security/compatibility test pass status

3. Review A-072 Production Readiness Checklist
   - Confirm deployment readiness completion rate
   - Identify incomplete items

4. Review A-073, A-074
   - Confirm no security issues
   - Verify license compliance

---

### Activity 10-2: Review Checklist Creation

**Responsible:** Human Reviewer

1. **Functional Validation (Functional Review)**
   - Verify Story Acceptance Criteria (AC) 100% complete
   - Validate business requirements met
   - Confirm user experience (UX) appropriateness
   - Mark: ✓ (Pass) / ⚠ (Conditional) / ✗ (Fail)

2. **Non-Functional Requirements (Non-Functional Review)**
   - Performance (Latency, Throughput) — Refer to A-071
   - Security (Data Protection, Access Control) — Refer to A-073
   - Compatibility (Browser, OS, Device)
   - Mark: ✓ (Pass) / ⚠ (Conditional) / ✗ (Fail)

3. **Documentation (Documentation Review)**
   - API documentation completeness
   - User guide clarity
   - Deployment procedure accuracy
   - Mark: ✓ (Pass) / ⚠ (Conditional) / ✗ (Fail)

---

### Activity 10-3: Issue Discovery & Classification

**Responsible:** Human Reviewer

Classify all discovered issues as follows:

| Classification | Definition | Remediation Method |
|------|------|---------|
| **Critical** | Cannot deploy (functional errors, security vulnerabilities, data loss risk) | Immediately return to Stage 9 (auto-fix then re-QA) |
| **Major** | Can deploy but quality degradation (usability issues, performance degradation) | Register additional Backlog (Post-Release) |
| **Minor** | Minor improvements (UI fine-tuning, typos) | Register additional Backlog (Future Sprint) |

---

### Activity 10-4: Backlog/Error Input

**Responsible:** Human Reviewer

Reference A-080, A-081, and if additional issues exist, record them in "Issue Discovery List" section of A-100: