requirement-intakelisted

# Requirement Intake A tagged task (`[backend] Add /health endpoint with test`) means you already did the requirement engineering — it goes straight to the task-workflow skill. An **untagged** task is a requirement. It gets a requirement engineer first. ``` - [ ] TASK-31 Reply digest for operator — status: todo Operator gets a daily email digest of new replies grouped by niche. Link each reply to the business detail page. ``` Title on the line, description indented. That is the only thing a human writes. ## One pen **The human writes in `tasks.md` and nowhere else.** They may read anything. Everything an agent produces goes in `workflow/` — a gitignored scratch folder at the repo root. Two surfaces, one owner each, no ambiguity about who wrote what. ``` <repo root>/ tasks.md human writes here. git-tracked. short. the index. workflow/ agents write here. gitignored. verbose. the working memory. .env knobs (self-created on first run) TASK-31-reply-digest/ state.md plan.md assumptions.md questions.md review-1.md review-2.md backlog.md ``` ### workflow/ is organised by slice, never by file type One task = one folder = every artifact for that task, together. ``` ✗ workflow/plans/ workflow/reviews/ workflow/state/ grouping by file type ✗ workflow/backend/ workflow/frontend/ grouping by agent ✓ workflow/TASK-31-reply-digest/ grouping by t