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-002/run-2026-04-25-15-14-00/dev-prompt.md

dev-prompt.md

What's this? →
# Run: run-2026-04-25-15-14-00
# Purpose: Executive Summary, Risk Assessment, KPIs Framework, and Marketing Plan — Otaku Haven LLC

## Your Role

You are the Developer for this run. You execute. You do not define scope.

---

## Files to Read — In This Order

1. `trail/runs/intent-002/run-2026-04-25-15-14-00/operating-instructions.md`
2. `trail/runs/intent-002/run-2026-04-25-15-14-00/tasks.md`
3. `trail/meta/files/Otaku_Haven_Reference_Data.md`
4. `Business Plan/02-Strategic/Financial-Model.xlsx` — required for Tasks 002 and 004; stop if missing
5. `Business Plan/01-Formation-and-Brand/Brand-Style-Guide.docx` — required for Task 005; read before writing the Marketing Plan

These are your only inputs. Read nothing else.

---

## Required Outputs

| File | Path |
|---|---|
| Executive-Summary.docx | `Business Plan/02-Strategic/Executive-Summary.docx` |
| Risk-Assessment.docx | `Business Plan/02-Strategic/Risk-Assessment.docx` |
| KPIs-and-Reporting.docx | `Business Plan/02-Strategic/KPIs-and-Reporting.docx` |
| Marketing-Plan.docx | `Business Plan/02-Strategic/Marketing-Plan.docx` |
| results.md (populated) | `trail/runs/intent-002/run-2026-04-25-15-14-00/results.md` |

---

## Execution

1. Read all inputs listed above in order.
2. Execute Task 001 first: verify Run 1 outputs exist. Stop if either file is missing.
3. Execute Tasks 002–005 in order. Populate `results.md` continuously.
4. For Tasks 002 and 004 (Executive Summary, KPIs): read `Financial-Model.xlsx` before writing. All financial figures must come directly from that workbook — not estimated independently.
5. For Task 005 (Marketing Plan): read `Financial-Model.xlsx` for the marketing budget figure and `Brand-Style-Guide.docx` for brand identity. The marketing budget total must match the Financial Model exactly.

---

## Ambiguity Handling

If ambiguity arises: choose the simplest interpretation consistent with `tasks.md`. Document the decision in `results.md`. If you cannot proceed without inventing scope or violating `operating-instructions.md`, stop and document the blocker.

---

## Run Completion Validation

Before declaring this run complete, verify all of the following:

- [ ] Task 001: Run 1 outputs confirmed present
- [ ] `Executive-Summary.docx` — all 6 sections present, all financial figures match `Financial-Model.xlsx`
- [ ] `Risk-Assessment.docx` — all 5 risk categories present with required minimum risks
- [ ] `KPIs-and-Reporting.docx` — all 5 KPI categories present, financial targets tied to `Financial-Model.xlsx`
- [ ] `Marketing-Plan.docx` — all 8 sections present, budget matches `Financial-Model.xlsx`, handles match reference data
- [ ] `results.md` fully populated: Tasks Completed, Files Changed/Added, Deviations, Assumptions Made, Open Questions/Blockers