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-007/run-2026-04-25-09-00-00/tasks.md

tasks.md

What's this? →
# Tasks — Intent 007, Run 2026-04-25-09-00-00

Execute tasks in the order listed. Cross-document dependencies are noted per task —
read the referenced files before producing each deliverable.

---

## Task 0 — Setup

- [ ] Create output folder: `Business Plan/07-Customer-Marketing-Community/`
- [ ] Read `operating-instructions.md` in full
- [ ] Read `dev-prompt.md` in full

---

## Task 1 — Read Cross-Document Dependencies

Read all of the following before beginning any deliverable. Note facts you will
reference in your output. Do not skip any of these reads — they are all required
for coherence.

- [ ] `trail/meta/files/Otaku_Haven_Reference_Data.md` — canonical facts (entity, address, technology stack, social handles, key dates, store hours)
- [ ] `Business Plan/01-Formation-and-Brand/Brand-Style-Guide.docx` — brand tone and voice (**read before writing anything**)
- [ ] `Business Plan/02-Strategic/Marketing-Plan.docx` — channels and strategy; budget context for Community/Events Plan
- [ ] `Business Plan/02-Strategic/Business-Plan.docx` — community engagement narrative for consistency
- [ ] `Business Plan/02-Strategic/KPIs-and-Reporting.docx` — metric definitions and tracking cadence for Community/Events Plan
- [ ] `Business Plan/04-Operations-SOPs/SOP-005-Returns-Exchanges.docx` — **REQUIRED before Task 5**; source of truth for all return policy details
- [ ] `Business Plan/04-Operations-SOPs/SOP-011-Vendor-Consignment.docx` — consignment details for Task 8 (Community/Events Plan local creator section)
- [ ] `Business Plan/05-Finance-and-Compliance/Data-Security-Policy.docx` — data handling practices referenced by Customer Privacy Policy

---

## Task 2 — Produce: Customer Privacy Policy

**Output:** `Business Plan/07-Customer-Marketing-Community/Customer-Privacy-Policy.docx`

**Dependencies:** Reference Data, Brand Style Guide, Data Security Policy

See `dev-prompt.md` § "Deliverable 1: Customer Privacy Policy" for required content and sections.

---

## Task 3 — Produce: Loyalty Program Terms and Conditions

**Output:** `Business Plan/07-Customer-Marketing-Community/Loyalty-Program-Terms.docx`

**Dependencies:** Reference Data, Brand Style Guide

See `dev-prompt.md` § "Deliverable 2: Loyalty Program Terms and Conditions" for required content.

Note: You must choose a points earning rate, redemption threshold, and point expiration period.
Document each choice in `results.md` under Assumptions.

---

## Task 4 — Produce: Return/Exchange Policy (Customer-Facing)

**Output:** `Business Plan/07-Customer-Marketing-Community/Return-Exchange-Policy.docx`

**Dependencies:** SOP-005-Returns-Exchanges.docx (MUST MATCH EXACTLY), Brand Style Guide

⚠️ **Highest-risk coherence task.** Every policy detail must match SOP-005 exactly.
Any discrepancy found between this run's brief and SOP-005 must be documented in
`results.md` — do not silently adjust.

See `dev-prompt.md` § "Deliverable 3: Return/Exchange Policy" for required content and format.

---

## Task 5 — Produce: Website Terms of Use

**Output:** `Business Plan/07-Customer-Marketing-Community/Website-Terms-of-Use.docx`

**Dependencies:** Reference Data, Brand Style Guide

See `dev-prompt.md` § "Deliverable 4: Website Terms of Use" for required content.

---

## Task 6 — Produce: Social Media Community Guidelines

**Output:** `Business Plan/07-Customer-Marketing-Community/Social-Media-Guidelines.docx`

**Dependencies:** Reference Data (digital presence — social handles), Brand Style Guide

See `dev-prompt.md` § "Deliverable 5: Social Media Community Guidelines" for required content.

Must cover all five platforms: Instagram (@OtakuHavenATX), TikTok (@OtakuHavenATX),
X (@OtakuHavenATX), Facebook (Otaku Haven Austin), Discord (discord.gg/otakuhavenatx).

---

## Task 7 — Produce: Community/Events Plan

**Output:** `Business Plan/07-Customer-Marketing-Community/Community-Events-Plan.docx`

**Dependencies:** Reference Data, Marketing Plan, Business Plan, KPIs-and-Reporting.docx,
SOP-011-Vendor-Consignment.docx, Brand Style Guide

See `dev-prompt.md` § "Deliverable 6: Community/Events Plan" for required content.

Must include:
- Pre-opening campaign (March–May 2026)
- Soft opening (May 25, 2026) — invite-only
- Grand opening (June 1, 2026)
- Ongoing event calendar framework
- Community metrics and targets

---

## Task 8 — Complete Results

Write final status to: `trail/runs/intent-007/run-2026-04-25-09-00-00/results.md`

Include:
- Completion status of each deliverable (Complete / Incomplete / Blocked)
- All assumptions made (especially points earning rate, redemption threshold, expiration period)
- All coherence notes (discrepancies found between brief and prior deliverables)
- Any deviations from this task list and why

---

## Pre-Completion Checklist

Before marking this run complete, verify all acceptance criteria in
`dev-prompt.md` § "Acceptance Criteria" are met.