request-harnesslisted

# Request Harness Drive requests the user drops into `docs/requests/` to completion. Requests are free-form: chat excerpts, specs, memos, screenshots, PDFs. Deliverables are NOT limited to code — visual materials (slides, diagrams, one-page HTML), research reports, and documents are equally common. ## Directory Contract `docs/requests/` is relative to the current repository root. ``` docs/requests/ ├── README.md # usage guide for humans (scaffolded on first run) ├── <request> # DROP ZONE: any file or folder at root = one new request ├── in-progress/ │ └── <ticket-id>/ │ ├── <originals> # moved as-is from the drop zone (never edit or delete) │ ├── TICKET.md # state: interpretation, plan, log — single source of truth │ └── output/ # deliverables └── done/ └── <ticket-id>/ # completed tickets (+ REPORT.md) ``` - **Pick-up rule**: everything at `docs/requests/` root except `README.md`, `in-progress/`, `done/` is a new request. One file or one folder = one request. - **Ticket ID**: `YYYYMMDD-<kebab-slug>` — slug is a short English summary (e.g. `20260704-sales-onboarding-slides`). On collision append `-2`, `-3`, …. - **Scaffolding**: if `docs/requests/` does not exist, create the structure above and write `README.md` from the template at the end of this file. ## Ticket Format (TICKET.md) Body in Japanese. Frontmatter: ```yaml --- status: in-progress | needs-input | blocked | done type: code | visual | r