Case Study
Otaku Haven
A specialty anime retail business, planned end-to-end. 49 documents. 7 intents. One workday.
← Back to Otaku Haven
trail/runs/intent-004/run-2026-04-25-20-10-23/dev-prompt.md
dev-prompt.md
What's this? →# Run: run-2026-04-25-20-10-23
# Purpose: Produce all 11 Operations SOPs for Otaku Haven
## Developer Contract
You are the Developer for this run. Your job is to execute `tasks.md` exactly
as written and produce the 11 deliverables listed there. You do not define scope.
---
## Files You Must Read (in this order)
### 1. Run Artifacts (read first — these are your complete instructions)
- `trail/runs/intent-004/run-2026-04-25-20-10-23/operating-instructions.md`
- `trail/runs/intent-004/run-2026-04-25-20-10-23/tasks.md`
- `trail/runs/intent-004/run-2026-04-25-20-10-23/workplan.md`
### 2. Reference Data (read before any SOP production)
- `trail/meta/files/Otaku_Haven_Reference_Data.md`
- `trail/meta/files/Otaku_Haven_Document_Checklist.md`
### 3. Cross-Document Dependencies (read before the tasks that require them)
- `Business Plan/03-HR/Employee-Handbook.docx`
— Read before: TASK-001, TASK-002, TASK-005, TASK-009, TASK-010
- `Business Plan/02-Strategic/Business-Plan.docx`
— Read before: TASK-006, TASK-008
- `Business Plan/02-Strategic/Financial-Model.xlsx`
— Read before: TASK-003, TASK-007
---
## Files You Must NOT Read
Do not read any of the following. They are Manager inputs only:
- `trail/intents/intent-004/intent.md`
- `trail/intents/intent-004/manager-instructions.md`
- `trail/intents/intent-004/operating-instructions-override.md`
- `trail/meta/trail.md`
- `trail/meta/global-operating-instructions.md`
If you find that you need information that appears to be in one of these files,
stop and document what is missing in `results.md`.
---
## Output Location
```
Business Plan/04-Operations-SOPs/
```
Create this folder if it does not exist.
---
## Deliverables
| # | File | Task |
|---|------|------|
| 1 | `SOP-001-Store-Opening.docx` | TASK-001 |
| 2 | `SOP-002-Store-Closing.docx` | TASK-002 |
| 3 | `SOP-003-Cash-Handling.docx` | TASK-003 |
| 4 | `SOP-004-POS-Usage.docx` | TASK-004 |
| 5 | `SOP-005-Returns-Exchanges.docx` | TASK-005 |
| 6 | `SOP-006-Customer-Service.docx` | TASK-006 |
| 7 | `SOP-007-Inventory-Receiving.docx` | TASK-007 |
| 8 | `SOP-008-Visual-Merchandising.docx` | TASK-008 |
| 9 | `SOP-009-Loss-Prevention.docx` | TASK-009 |
| 10 | `SOP-010-Safety-Emergency.docx` | TASK-010 |
| 11 | `SOP-011-Vendor-Consignment.docx` | TASK-011 |
All in Word (.docx) format. No other formats permitted.
---
## Recommended Production Order
SOP-003 → SOP-001 → SOP-002 → SOP-004 → SOP-005 → SOP-006 →
SOP-007 → SOP-008 → SOP-009 → SOP-010 → SOP-011
(Rationale: SOP-003 must exist before SOP-002 can accurately reference it;
SOP-009 and SOP-010 cross-reference each other and are easier to write together.)
---
## Important Notes
1. Every SOP uses the same 7-section template defined in `operating-instructions.md`.
Do not deviate from the template structure.
2. SOP-003 and SOP-005 require forward-reference documentation in `results.md`.
Record specific values (not ranges) for cash thresholds and return policy terms.
3. All facts about the store (hours, roles, technology, address, products) come from
`Otaku_Haven_Reference_Data.md`. Do not invent facts.
4. If you detect a conflict between the reference data and a prior deliverable, stop
and document it in `results.md`. Do not silently resolve it.
5. Complete `results.md` as your final step (TASK-012).