SP 08 BACKLOG ERRORLOG
# Stage 8 Prompt: Backlog + Error Log Identification
> Spec-Contract v5.0 | Cycle: Assessment
> Stage Prompt ID: SP-08
---
## CONTEXT
- **Current Location:** Assessment Cycle > Stage 8 (Backlog and Error Log Identification)
- **Previous Stage:** Stage 7 (Integrated Verification + Quality Assessment) — Artifacts: EVALUATION_REPORT, SECURITY_VULNERABILITY_REPORT, LICENSE_COMPLIANCE_REPORT
- **Next Stage:** Stage 9 (Design Reflection + Re-execution Decision)
- **Product Mode:** Applicable (performed in all releases)
---
## OBJECTIVE
**Goals to achieve in this Stage:**
Extract all issues found in the Stage 7 assessment report and register them in **3 classification categories (Build Failure → Error, Quality Unmet → Backlog, New Ideas → Backlog)** as **BL-xxx (Backlog) or ERR-xxx (Error Log)** format, specifying **type/priority/related SP/effort/affected documents** for each item.
### Success Criteria:
1. **Error Log (ERR-xxx):** All Critical/High vulnerabilities, build failures registered (100%)
2. **Backlog (BL-xxx):** All quality improvements, unmet requirements, performance optimizations registered (100%)
3. **Classification Accuracy:** Each item's type/priority/effort clear and reasonable
4. **Relationship Mapping:** Related Phases, Spec sections, architecture components linked
5. **Consistency Totals:** A-070~074 assessment results match BL/ERR item count (e.g., 7 warnings = 7 items)
---
## CONSTRAINTS
### MUST DO:
- [ ] **8-1 Error Log Identification:** Extract all Critical/High issues from A-070, A-073, A-074 → Register as ERR-xxx
- [ ] **8-2 Backlog Identification:** Medium/Low issues, performance improvements, UI improvements, etc. → Register as BL-xxx
- [ ] **8-3 Classification Logic Applied:** Strictly separate build failure → Error, quality unmet → Backlog
- [ ] **8-4 Priority Assignment:** P0 (Critical, deployment blocker) / P1 (High, within 1 week) / P2 (Medium, within 1 month) / P3 (Low, gradual)
- [ ] **8-5 Effort Estimation:** Record expected work time (1h, 2h, 8h, 16h, 40h, etc.) for each item
- [ ] **8-6 Related Document Links:** Specify Spec, Phase, component line numbers
- [ ] **08_BACKLOG.md + 08_ERROR_LOG.md Writing Complete**
### MUST NOT DO:
- [ ] Do not confuse Error and Backlog criteria (e.g., "slow performance is error?" ❌ Backlog)
- [ ] Do not decide priority politically (e.g., "executive wants it so P0" ❌ based on technical impact)
- [ ] Do not over/under-estimate effort (reference team history, include 25% margin)
- [ ] Do not omit related documents (each item traceable for why it occurred)
- [ ] Do not register duplicate items (if "security vulnerability 1" and "package upgrade" same issue, merge)
### SCOPE:
- Modification Range: **A-080 (08_BACKLOG.md)**, **A-081 (08_ERROR_LOG.md)** newly created
- Reference Range: A-070 (EVALUATION_REPORT), A-073 (SECURITY_VULNERABILITY_REPORT), A-074 (LICENSE_COMPLIANCE_REPORT)
- **After Stage 8:** Transfer to Stage 9 (design reflection decision)
---
## INPUT ARTIFACTS
| ID | File Path | Reference Content |
|----|----------|-------------------|
| A-070 | `docs/07_EVALUATION_REPORT.md` | 10-section assessment results (warnings/unmet items) |
| A-073 | `docs/Security_Vulnerability_Report.md` | Critical/High/Medium vulnerability list |
| A-074 | `docs/License_Compliance_Report.md` | High Risk licenses, unidentified items |
| A-062 | `docs/04_VERIFICATION_LOG.md` | Phase verification failures |
| A-066a | `docs/Tech_Debt_Register.md` | Already registered technical debt |
| A-048 | `docs/02_SPECIFICATIONS.md` | User Story status (unmet items) |
---
## OUTPUT ARTIFACTS
| ID | File Path | Format | Grade | Description |
|----|----------|--------|:----:|-------------|
| A-080 | `docs/08_BACKLOG.md` | 📄 MD | 📊 | Backlog items (BL-xxx): Type/Priority/Effort/Related Documents |
| A-081 | `docs/08_ERROR_LOG.md` | 📄 MD | 📊 | Error Log items (ERR-xxx): Severity/Reproduction Conditions/Error Message/Fix Direction |
---
## EXECUTION RULES
### 1. Session Rules:
- **Single Session Execution:** Stage 8 completed in one Agent session
- **A-070~074 Required Reference:** Cannot proceed without assessment reports (return to previous stage)
### 2. Error Log Classification Criteria (ERR-xxx):when to use it
Community prompt sourced from the open-source GitHub repo SunnyBan101/spec-contract-v5 (no explicit license). A "SP 08 BACKLOG ERRORLOG" 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