From 7f6dcc8ffd7763875eb536dcc4998f6a22569c0a Mon Sep 17 00:00:00 2001
From: Samuel James <samueljamesinc@gmail.com>
Date: Sat, 5 Sep 2026 11:51:41 +0000
Subject: [PATCH] Add project intake document

---
 .kiro-team/intake.md | 105 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 105 insertions(+)
 create mode 100644 .kiro-team/intake.md

diff --git a/.kiro-team/intake.md b/.kiro-team/intake.md
new file mode 100644
index 0000000..cc52284
--- /dev/null
+++ b/.kiro-team/intake.md
@@ -0,0 +1,105 @@
+# Intake — TaskFlow
+
+## Problem
+
+Small teams managing shared work have no single place to track tasks, see who owns what, and know when something is blocked. They rely on a mix of email threads and shared documents that go out of date and cause work to be missed or duplicated.
+
+## Desired Outcome
+
+A working web-based task tracking system that allows small teams to create, assign, and update tasks without relying on external documents or email threads for status visibility.
+
+## Users
+
+- **Primary:** Team members who create and update tasks day to day
+
+- **Secondary:** Team leads who review overall task status and reassign work
+
+## Success Measures
+
+- [ ] A user can create and assign a task in 3 steps or fewer: yes/no
+
+- [ ] All tasks assigned to a user are visible on a single screen: yes/no
+
+- [ ] At least 90% of beta testers complete core workflow without asking for help: yes/no
+
+- [ ] Zero tasks are silently lost or unrecoverable after a failed save: yes/no
+
+## In Scope
+
+- Create, edit, and delete tasks
+
+- Assign tasks to a team member
+
+- Mark tasks as open, in progress, or blocked
+
+- View all tasks assigned to the current user
+
+- Basic error and empty states for all user-facing screens
+
+- Accessibility compliance to WCAG 2.1 AA
+
+## Non-Goals
+
+This project will deliberately NOT:
+
+1. Send email or push notifications of any kind.
+
+2. Support file attachments or document uploads.
+
+3. Provide time tracking or hour logging.
+
+4. Generate reports, charts, or exportable data.
+
+5. Support guest or unauthenticated access.
+
+## Constraints
+
+- Must be ready for internal beta with 5 test users within 8 weeks of kickoff
+
+- Must not store passwords in plain text
+
+- One full-time developer available for the build phase
+
+- No paid third-party service integrations at launch
+
+## Assumptions
+
+- **Assumption:** Teams using this tool will have between 2 and 15 members at launch.
+
+- **Assumption:** All users have access to a modern desktop browser.
+
+- **Assumption:** User account creation will be handled by an admin, not self-registration.
+
+- **Assumption:** Concurrent usage will not exceed 20 users during the beta period.
+
+## Accountable Human
+
+**Sam** — project lead, sole approver at every gate. No work advances to the next phase without Sam's explicit sign-off.
+
+## Definition of Done
+
+A feature is done when all of the following are true:
+
+- [ ] The feature works as described in the scope for the happy path.
+
+- [ ] At least one automated test covers the core behavior.
+
+- [ ] The empty state (no data, first-time user) is handled and visible.
+
+- [ ] The error state (failed action, bad input) is handled and visible.
+
+- [ ] The feature is keyboard-navigable and has no missing alt text or unlabeled form fields.
+
+- [ ] The code is committed to the main branch of the project repository.
+
+- [ ] Sam has reviewed and approved the feature.
+
+## Mockups
+
+3 mockups total:
+
+1. **Task List / Dashboard** — desktop (1440 px) and mobile (375 px)
+
+2. **Create or Edit Task screen** — desktop (1440 px) and mobile (375 px)
+
+3. **Blocked task empty and error state** — mobile (375 px) only
\ No newline at end of file