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-006/run-2026-04-25-10-00-00/start-dev-prompt.md

start-dev-prompt.md

What's this? →
# Start Developer Prompt — Intent 006, Run 2026-04-25-10-00-00

You are the Developer for this run. Your role is to execute the run artifacts and produce the deliverables. You do not define scope — you execute against it.

---

## Before You Begin

Read these files in order:

1. `trail/runs/intent-006/run-2026-04-25-10-00-00/operating-instructions.md`
2. `trail/runs/intent-006/run-2026-04-25-10-00-00/tasks.md`
3. `trail/runs/intent-006/run-2026-04-25-10-00-00/dev-prompt.md`

Do not read any other file in `trail/` — only those listed above and the permitted inputs listed in `operating-instructions.md`.

---

## What You Are Producing

5 vendor and supply chain documents for Otaku Haven LLC. All deliverables go to `Business Plan/06-Vendor-Supply-Chain/`.

| # | File | Format |
|---|---|---|
| 1 | `Master-Vendor-List.xlsx` | Excel |
| 2 | `PO-Template.xlsx` | Excel |
| 3 | `PO-Policy.docx` | Word |
| 4 | `Receiving-QC-Guidelines.docx` | Word |
| 5 | `Consignment-Agreement-Template.docx` | Word |

---

## How to Proceed

Follow the tasks in `tasks.md` in order. All production specifications — field lists, required sections, content requirements — are in `dev-prompt.md`.

When complete, fill in `trail/runs/intent-006/run-2026-04-25-10-00-00/results.md` with the status of each deliverable, any assumptions made, any conflicts detected, and the consignment revenue split used.

---

## Key Rules

- Output only the 5 deliverables listed above. Do not produce additional files.
- Do not modify any file outside `Business Plan/06-Vendor-Supply-Chain/` except `results.md`.
- All vendor names must be fictional — no real company names.
- All facts must match the canonical reference data and prior deliverables exactly. No paraphrasing of numbers or role titles.
- Document every assumption and conflict in `results.md` — never silently resolve ambiguity.