AI Dev Tools Zoomcamp 2026

Homework 1: AI-Native Developer Workflow Statistics

Distribution of scores and reported study time for this homework.

Submissions

337

Median total score

Average total score

Score distribution

All values are points.

Metric	Min	Q1	Median	Average	Q3	Max
Questions score	3	6.0	6.0	5.7	6.0	6
Learning in public score	-	0.0	0.0	0.4	0.0	7
Total score	3	6.0	6.0	6.2	6.0	14

Questions score

Min: 3
Median: 6.0
Max: 6
Q1: 6.0
Avg: 5.7
Q3: 6.0

Learning in public score

Min: -
Median: 0.0
Max: 7
Q1: 0.0
Avg: 0.4
Q3: 0.0

Total score

Min: 3
Median: 6.0
Max: 14
Q1: 6.0
Avg: 6.2
Q3: 6.0

Time distribution

All values are hours reported by students.

Metric	Min	Q1	Median	Average	Q3	Max
Lectures	0.0	2.0	3.0	3.9	4.0	72.0
Homework	0.0	1.0	2.0	3.2	4.0	30.0

Lectures

Min: 0.0
Median: 3.0
Max: 72.0
Q1: 2.0
Avg: 3.9
Q3: 4.0

Homework

Min: 0.0
Median: 2.0
Max: 30.0
Q1: 1.0
Avg: 3.2
Q3: 4.0

Question breakdown

Correctness and answer distribution per question.

1. Which coding agent did you use?

337 / 337 correct (100.0%)

Answer	Count
Claude Code	64
Codex	35
Claude	27
claude code	17
Codex CLI	12
Antigravity	11
Cursor	11
Claude code	9
OpenCode	9
GitHub Copilot	8
codex	6
Copilot	5
opencode	5
Gemini CLI	4
claude	4
OpenAI Codex	4
Antigravity IDE	3
github copilot	3
Aider	3
Github Copilot	3
Antigravity CLI	2
Opencode	2
Hermes Agent	2
Kilo Code	2
ChatGPT	2
Gemini	2
Codex + GPT 5.6 Terra High	1
Hermes + DeepSeek Harness	1
claude, because i have yearly subscription	1
openai Codex	1
ChatGPT / Codex	1
Oh My Pi (omp) — spark-deepseek/deepseek-v4-flash	1
Github Co-pilot	1
My coding agent is Claude Code	1
Cursor Grok 4,6/Composer2,5	1
1- Copilot AI agent 2- chatGPT chatbot	1
Google Antigravity	1
I used OpenAI Codex CLI as my coding agent throughout the project.	1
Grok (xAI)	1
I used CODEX CLI.	1
ChatGPT/codex	1
Antigravity CLI (powered by Gemini models)	1
Open Code	1
Vs plugin Codex	1
claude.ai	1
Opencode powered by Meta Muse Spark	1
DeepSeek as architect and OpenCode as builder	1
puku-cli	1
agy CLI with Gemini	1
Claude and OIllama	1
Codex and Claude	1
Claude Sonnet 5	1
Git Copilot	1
Gemini cli	1
CodeX	1
Claude code.	1
opencode big pickle	1
Cursor (Grok 4.6)	1
claude code (fable 5.1 and opus 5)	1
Replit Agent	1
cursor	1
Windsurf	1
Arena.ai Agent Mode — an agentic assistant that edits files and runs commands directly in the repository. (Replace with Claude Code / Cursor / Codex CLI if you used one.)	1
In This Section We use Claude Code in VSCode	1
Claude COde	1
Claude Code.	1
Custom company copilot based on Qwen	1
Copilot Chat	1
I chose Codex CLI as my coding agent.	1
Codex and Claude Code	1
Microsoft copilot	1
Codex in ChatGPT Work	1
Google Antigravity - IDE	1
Qwen AI + cline ( Vscode )	1
Claude web + DeepSeek	1
Codex CLI (models: GPT-5.6 Luna, Terra, Sol and GPT-6 Astra)	1
Goole Antigravity	1
Codex CLI (OpenAI)	1
Claude Code (Opus 5)	1
claude code & codex for the initial plan discovery	1
AIDER	1
Oh my pi	1
pi	1
Claude Code (Anthropic's CLI agent)	1
gemini cli	1
Antigravity agent claude sonnet	1
claude ai	1
claude code in VSC	1
cline	1
Continue with llama3.1:8b model from ollama	1
antigravity	1
Google Antigravity's gemini	1
VS Code + Copilot	1
Github Copilot (Luna)	1
Claude Code (Sonnet 5).	1
open code	1
VSCode with Antigravity Claude Sonnet 4.6 (thinking)	1
Gemini 3.1 Pro	1
Claude code, Codex, OpenCode	1
Antigravity CLI (using Gemini 3.1 Pro)	1
Claude, Antigravity	1
chatgpt	1
Big Pickle (OpenCode)	1
Github copilot and claude	1
OpenCode (Nemotron 3 Ultra)	1
copilot + vscode	1
ChatGPT Codex	1

2. What are the 2-4 features your spec settled on?

337 / 337 correct (100.0%)

Answer	Count
this started as a City journal. 1. Capture a place in one line. add records a place with neighborhood, free-text note, tags, and an optional rating. Low enough friction that I log a spot while still standing outside it. 2. Find it again when I only half-remember it. find does typo-tolerant, ranked search across name, note, tags, and neighborhood — and never comes back empty: below the confidence threshold it offers the closest 3, labelled as weak matches. 3. Want-to-go → been-there loop. Every place is wishlist or visited. todo shows what I still owe the city; visit flips a place over and asks for the note and rating while the memory is fresh. 4. Nudges and coverage. surprise picks somewhere to go, favoring the never-visited and long-neglected. stats shows how much of the city I've actually touched.	1
Chore management CRUD Dashboard Suggested assignee History log	1
User & Household Management: Create/join a household and add members. Chore Creation & Assignment: Add recurring or one-off chores and assign them to household members.	1
1. Chore list, each assigned to one of 3 people 2. "Mark done" button (no history) 3. Recurring chores that auto-reset after completion (e.g. every N days, weekly) 4. No login — pick who you are once, remembered in session	1
Roommates with names + an Admin role — only the Admin can rename a roommate Anyone can mark any chore done — regardless of who it's assigned to Completion attribution — each completed chore records who marked it done and when, visible to all roommates Grouped main screen — open chores grouped into Overdue / Today / Upcoming (Today highlighted), plus a separate Completed section showing who completed each	1
## 3. Core Mechanics & Workflows ### 3.1 Chore Assignment & Recurrence - Chores are scheduled on a fixed daily recurring cycle. - Each chore is assigned to a specific child. ### 3.2 Two-Step Approval Flow 1. Completion: Child logs in on their device and clicks Mark Done on an assigned chore for today. 2. Review: Chore status shifts to Pending Approval. 3. Verification: Parent logs in, views the pending approvals list, and clicks Approve or Reject. 4. Resolution: - If approved: Task counts as completed toward the child's daily streak. - If rejected: Chore returns to the child's active list with feedback/rejection state. ### 3.3 Streak & Gamification Logic - Daily Streak: A streak increments when all assigned chores for the day are approved. - Milestone Badges: Unlocked automatically when streak milestones are achieved: - Bronze Starter: 3-day streak - Silver Habit: 7-day streak - Gold Champion: 14-day streak ---	1
Family management (children) tasks and points rewards engagement, motivation	1
Manual chore assignment, automatic chore rotation, completion tracking with reminders, and a dashboard with fairness/progress statistics	1
1. dashboard and history 2. reminders and notifications 3. Changing, rejecting, and claiming chores 4. Chores itself	1
1. Add a task (create a chore with title and description) 2. Assign a user (assign task to a household member) 3. Mark as done (complete a task) 4. View the list (see all tasks with status and assignee)	1
Users: 2 (you + wife), both full read/write, no admin hierarchy Chores: two types — permanently owned (you: vacuum + drains; her: dishwasher) and free-for-all pool Completion tracking: who did it + when, full log (not just a checkbox) Frequency: per-chore (daily/weekly/monthly/custom) Notifications: owner-only nags for permanent chores, both nagged for free-for-all; delivered via web push + email fallback Platform: Django backend, installable PWA frontend Auth: lightweight — PIN or magic link per person, no full account system	1
### Core Features The application will support: 1. Chore assignment - Chores are distributed using a fairness-based system. - The system should consider the household's configured fairness rules. 2. Chore scheduling - Support fixed schedules. - Example: Clean the bathroom every Sunday. - Support flexible deadlines. - Example: Clean the bathroom sometime between Monday and Sunday. 3. Completion tracking - Members can complete assigned chores. - Some chores can require verification before being considered approved/completed. 4. Fair workload distribution - Fairness is customizable by the household. - The exact fairness mechanism is not fully finalized yet. - Possible future direction: chore weights, duration, or other configurable measures.	1
1. Create / edit / delete / complete chores 2. Assignment & completion tracking 3. Soft‑delete & recurrence handling 4. Simple member management	1
1. Shared name-pick dashboard — one link, no login; four housemates pick their name. 2. Weekly rotation — a fixed chore list (in config, not the UI) rotates through people one at a time every week, whether or not the chore was finished. 3. Done checkbox — mark the current week’s assignment complete so you can see who’s behind. 4. Overdue flag — anything still unchecked when the week turns is shown as overdue (red); rotation still moves on.	1
Add new member, add new tasks and assign them to members, list of former tasks and assignees.	1
- Set up the python environment and install django - Authentication: existing users can log in into the application - Registration: new users can sign up	1
Course management, learning progress tracking, learning notes, and a simple progress dashboard.	1
Households and members Create, edit, and delete chores Assign chores to household members Mark chores as completed or pending	1
1. Request intake 2. Request classification 3. Action plan 4. Status tracking	1
Create & assign tasks, grouped list by assignee, mark done, SQLite persistence	1
RBAC Categorisation of tasks Configurable allocation: automatic, manual Recurrence of tasks	1
The spec settled on these features: 1. Shared board — a few users can add chores to a communal list and see what's there. 2. Claim & complete — users claim open chores and mark them done; the board shows status. 3. Mixed chore types — recurring chores (weekly trash, daily dishes) with due dates/cadence, plus one-off tasks on demand. 4. Done tracking — a record of who did what and when.	1
Household Chore Manager — A mobile app for multiple households/groups where users can: Assign chores to specific people or add to a shared pool Create one-time and weekly recurring chores Track completion history Earn points for completed chores View chore distribution stats and leaderboards	1
- Any household member can create/edit chores - Chores are claim-based - One person can claim a chore at a time - Claimed chores can be unclaimed only before the deadline	1
Weekly Rotation Engine Chore Dashboard Chore History One‑Off Backlog	1
Household creation and joining Weekly chore planning Self-assignment and completion Automatic overdue reminders	1
Couple (2 partners, one household) Weekly planning together (pick/drag chores per day) Recurring templates + weekly tweaks Completion tracking with progress Mixed assignment (some assigned, some open)	1
households & members, recurring chores with due dates, round-robin rotation assignment, completion history	1
1. Anonymous weekly feedback via a public link. 2. A 1–5 project-health score with an optional comment. 3. Duplicate-submission protection using hashed IP and device data. 4. Role-based dashboards showing results, trends, score distributions, and comments.	1
-Automatic fair chore rotation -Flexible chore scheduling & lifecycle -Smart responsibility management -Shared household visibility with light gamification	1
Chore roster & effort points; one-click completion & history; live fairness dashboard & status badges	1
* chore management with predefined and custom one-time or recurring tasks * smart assignment to either person, both people, or optional automatic rotation * weekly and monthly calendar with completion tracking and in-app reminders * simple monthly statistics with completed tasks and completion rates per person	1
Communal pool (anyone can view/complete chores); recurring logic based on waiting period; status tracking (Upcoming/Due/Overdue); task details with name, description, and priority.	1
> 1. Open-Pool Kanban Claim Board: Shared chore pool (`Unclaimed Pool` → `In Progress` → `Completed This Week`) where members claim tasks on demand via 1-click actions. > 2. Deadline-Driven Visual Urgency Engine: Dynamic Django model property calculating urgency tiers (`🟢 On Track` → `🟡 Due Soon` → `🔴 Overdue` → `🚨 Critical Overdue`) based on `due_date`. > 3. Dynamic Seasonal Chore Filtering: Central household season setting (`SPRING`, `SUMMER`, `FALL`, `WINTER`) filtering active seasonal tasks (e.g., summer lawn care vs. winter snow removal). > 4. Automated Recurrence & History Archive: Completed recurring chores timestamp history and automatically spawn the next instance into the open pool with an updated deadline.	1
- The tool is primarily for any shared household - The core interaction is assing chores to people - When chore is completed, it should be marked as done and should be recorded who did it and when - Chores could be either a one time task or a recurring task	1
It actually asked about a total of 7 features, but these were the first four: - Built for one fixed, known household. Anyone can add or edit chores and members — no roles, no admin, no login. - Assignment: Mixed model. - Recurrence: Flexible recurrence. - Completion: Self-report and trust-based. A person taps "done" — no verification, no dispute, no photo proof.	1
1. Auto-rotating chore assignments — repeats on a schedule, split evenly across the 5 members 2. Completion tracking — mark done, with optional confirmation from another member 3. Due notifications/reminders — plus manual browsing 4. Shared dashboard — single access, no individual logins	1
1. Chores & members - A fixed list of household members (name only, no accounts). - Chores can be one-off or recurring (e.g. "every Monday", "every 3 days"). 2. Manual assignment - Any member can assign any chore to any member. - Assignment can be changed at any time before completion. 3. Completion & history - Marking a chore done logs who did it and when (visible history). - If the chore is recurring, completing it automatically creates the next occurrence based on its schedule. 4. Due dates & overdue flagging - Chores have a due date. - Chores past their due date and not yet completed are visually flagged as overdue.	1
Household & roles Chore management Completion tracking Grading	1
1. Recurring chores — fixed interval (every N days), with due-date and overdue tracking 2. Round-robin assignment — strict rotation across household members (simple ordered list, no weighting/randomness) 3. Completion history — a log of every time a chore was marked done, by whom and when 4. Simple CRUD + dashboard — custom Django templates for chores/members, with a dashboard showing due/overdue status and a mark-complete action (no member logins — they're just records)	1
Household chore creation, frequency scheduling (daily/weekly), and task completion tracking.	1
Family Members & Chore Catalog: Define family members (name and role) and create recurring chores assigned to a specific member and a fixed day of the week (Monday through Sunday). Weekly Family Dashboard: A weekly grid/matrix overview showing all scheduled chores organized by day of the week and family member. Personal Daily View ("My Day"): Filter view for an individual family member showing only today's pending chores with a quick toggle to mark chores as Pending or Completed.	1
Household creation + join-by-invite-code Task list with default point values (admin-editable, changes logged with who/when) Recurring tasks (daily/weekly) Per-person daily free-time capacity, self-reported Capacity visible to all household members (transparency, not private) Capacity changes logged (who changed it, when) — same audit pattern as point values Claim-first task pool	1
Create and manage one-off and recurring chores Assign chores or leave them open for claiming Track due/overdue and completed chores Track effort points and contribution statistics	1
- Pure-function schedule — the schedule is computed from the date and a config file; nothing about who owes what is stored. - Time-based rotation — a new period means a new assignee, regardless of whether the previous one completed the chore. - Completion logging without enforcement — a checkbox writes a log row; no debt maths, no nagging. - Swaps as overrides — "Sam takes my week" writes an override record keyed on (chore, period); the computed schedule is never mutated. - Shared-link access, no accounts — the unguessable URL is the access control; identity comes from a name dropdown next to the checkbox. - Per-chore periods, weekly/monthly only — each chore carries its own period; seeded weekly and monthly, daily chores deliberately excluded.	1
- Either adult can skip a task. - Either adult can complete any task. - The original assignment remains unchanged.	1
Приложение будет для одного домохозяйства или нескольких? -> для одной семьи Как будем распределять дела в семье? -> вручную — при создании дела выбираем ответственного. Какие дела поддерживаем? -> разовые и повторяющиеся.	1
Fairness-based auto-rotation for recurring chores Manual assignment for one-time chores Simple difficulty weighting (easy/medium/hard) In-app notifications for reminders	1
1) Create chores with a task description, responsible person, and deadline. 2) View incomplete chores with the assignee and deadline, including an Overdue status for late tasks. 3) Mark chores as completed and move them to a separate Completed section. 4) Edit and delete existing chores.	1
Scope Summary: Shared Household Chores Tool * Target Audience: Whole family * Chore Assignment & Rotation: Automated weekly rotation with manual parent overrides/approval * Accountability & Verification: Photo proof required for task completion * Reward System: Gamified rewards (badges, levels, achievements)	1
Log sleep sessions — bedtime, wake time, and sleep-stage data (seeded from a public dataset like Sleep-EDF for the MVP, so it works without a smartwatch on day one). Compute personal sleep stats — average full-cycle length and average time-to-fall-asleep, derived from logged sessions. Recommend a bedtime — given a target wake time, return a few bedtime options (e.g. "10:15pm — 5 full cycles," "11:45pm — 4 full cycles") plus a suggested wind-down start time. (optional 4th) View sleep history — a simple list/chart of past sessions and trend in cycle length over time.	1
1. Chore Management: Add/edit chores and set a default owner for each. 2. Daily Effort Logging: Log who did which chore with a subjective effort rating (1–10). 3. 30-Day Trend Chart: A line chart showing cumulative effort per partner over time. 4. Fairness Indicator: A percentage imbalance displayed next to the chart.	1
Track when each chore was last done. Plan chores into a weekly schedule. Log history so patterns become visible.	1
Automated Recurring Chore Generation & Round-Robin Rotation Open Claim Pool (Backlog Board) Gamified Points & Household Leaderboard In-App Visual Deadlines & Urgency Tracking	1
1. Add Person 2. Add Company 3. Log Interaction 4. Search & Filter	1
1. User registration and authentication (email-based) 2. Household management with member invitations 3. Chore assignment with weekly rotation 4. Chore completion and refusal tracking	1
Calendar view as the home screen; tasks appear as dated items Add a one-off task (title, date, optional note) Claim an open task → it shows your name Mark a task done → moves to history with who/when	1
- Individual accounts with parent (admin) and child (member) roles - Parent-assigned chores - Recurring chores (daily / weekly) - Parent verification before points are awarded	1
Task Creation & Assignment Manager creates tasks Supervisor assigns tasks to workers Completion Flow Worker submits a completed task Supervisor approves or rejects it, with a reason required on rejection	1
### Automatic Assignment Assignments are automatic and fixed. Roommates cannot: - Swap assignments - Decline assignments The assignment algorithm should prioritize: 1. Fairness 2. Availability 3. Priority 4. Light streak influence Fairness should consider: - Total estimated effort assigned/completed over time - Rotation of unpleasant chores - Gradual rebalancing after someone returns from away mode The system should show: - Assignment explanation - Fairness score breakdown - Rotation history ### Availability Each roommate can define: - Weekly recurring availability - Time ranges for each day Availability: - Is visible to other roommates - Influences automatic assignment - Is secondary to fairness ### Away Mode A roommate can enter vacation/away mode. While away: - They are excluded from assignments. When returning: - Fairness should rebalance gradually. - The system should not immediately overload them with chores.	1
1. Chore Catalog & Scheduling (Daily / Weekly / One-off): Parents can create, edit, and assign recurring or one-off chores with set point values. 2. Parent Approval & Verification Workflow: Children mark completed tasks as `Pending Approval`, which parents review and approve/reject before points are awarded. 3. Point Ledger & Real-Time Scoreboard: A transaction ledger (`PointLedger`) that tracks earned points, updates balances atomically upon approval, and displays a household leaderboard. 4. Role-Based Dashboard (Parent vs. Child Views): A responsive interface allowing fast switching between a Parent view (admin, chore creation, pending approvals queue) and a Child view (active chore list, one-tap submission, balance tracker).	1
- Create one household and manage its members. - Create multiple weekly recurring chores. - Automatically assign chores fairly based on fewest completions. - View assignments and mark chores complete with history.	1
- Create a household chore - Assign one family member as the responsible person - Set a required due date and an optional due time - Mark a chore as completed	1
Log chore completions — record what chore was done and when (a tracking log, not a reminder pusher) Editable chore list — freely add, edit, or remove chores anytime, each with its own expected interval (e.g. dishes = 1 day, vacuum = 7 days) Overdue flagging — a chore is flagged overdue when time since its last log entry exceeds its interval Mobile-friendly single page with localStorage — simple browser page, data persists locally on one device, no backend	1
1. Household chore assignment & recurrence — chores with difficulty/points, assigned via manual, rotation, or claim modes, with fixed or flexible recurrence schedules. 2. Completion approval workflow — members submit completions; an administrator approves or rejects them (pending/rejected completions never trigger gamification). 3. Gamification (points, streaks, badges, leaderboards) — an append-only points ledger, daily streak tracking, fixed milestone badges, and all-time/current-period leaderboards, all driven strictly by approved completions. 4. Due/overdue visibility — an in-app API surface showing what's due or overdue, using timezone-aware date boundaries.	1
Roster management, Chore management, Agentic assignment, Status/summary report.	1
Create one-off chores with title, description, and due date; assign chores to a roommate; switch the active roommate with a simple profile selector; mark chores as completed and filter the task list by roommate and status.	1
Chore management — create/edit/delete chores (one-off or recurring, with priority, and manual or auto-rotate assignment) Dashboard — overdue / due-today / upcoming view grouped by household member, with a "mark done" action Household members — add/edit/remove the people chores get assigned to Completion history log — record of who completed what and when, with on-time/late status	1
* Manual Assignment with Roles: An administrator ("head of the household") creates tasks and assigns them to specific users. * Trust-Based Status System: An open workflow where any family member can mark a task as completed (or revert the status back if done by mistake). * Extended Attributes: Each task card includes a deadline (due date) and a complexity score (points/weight). * Recurring and One-Off Tasks: Support for both single, one-time assignments and regular, repeating chores. * Hybrid Categorization: A mix of predefined basic zones (e.g., Kitchen, Living Room) and the ability to create custom categories (e.g., Appliances, Tech).	1
Manage flatmates and chores (name, interval, rotation order) via the Django admin Complete a chore: records who did it, advances the rotation, recomputes the due date on the fixed rhythm Overview of what is due and overdue, with the current assignee Fairness view: completions per flatmate over the last 30 days (specified, not implemented)	1
The 4 features settled on are: - Flexible Recurring Chores: Creation and editing of tasks with effort points and schedule settings (fixed dates or flexible windows), keeping overdue items visible. - Fairness-Driven Assignment & Suggestions: Manual claiming and assignment paired with a suggestion system that uses historical effort points to recommend balanced task distributions without auto-assigning. - Completion & History Audit: Logging task completion with timestamps, support for editing/undoing completions, and lifetime history tracking for fairness calculations. - Daily Dashboard & In-App Reminders: A centralized screen showing today's priority tasks, a compact household balance summary, and in-app alerts for upcoming or overdue chores.	1
A tool for tracking time, mileage, and tasks related to caring for an aging parent in assisted living with a progressive disease. Features will include: Capture - Start/stop timer for a visit or task session - Route picker at start; miles prefill from the saved route - Odometer in/out as a per-trip override - Every entry editable after the fact - Non-driving time entries (phone calls, paperwork, insurance, coordination) - Out-of-pocket expenses, with a category and a deductible flag Tasks - Recurring care calendar: prescription refills, facility invoice review, care plan meetings, Medicare open enrollment, insurance renewals - Agenda for next visit — items surfaced when the timer starts, so they don't evaporate the moment you walk in - Follow-ups from phone calls: deadline plus a note recording who said what, and when Numbers - Month-end: hours, miles, out-of-pocket - Year-end: deductible miles × the correct IRS medical rate, hours total, out-of-pocket total - Export	1
### 1. Target Users: Family The tool is designed for parents and children living in the same household. ### 2. Chore Creation: Hybrid - Parents can create and assign regular chores to family members. - Children can add or claim optional chores. ### 3. Recurring Chores: Recurrence The tool supports: - One-time chores - Recurring chores, such as daily or weekly chores Automatic rotation between family members is not currently in scope. ### 4. Completion and Approval: Parent Approval The basic workflow is: Parent assigns chore → Child completes chore → Child marks it as Done → Parent approves or rejects completion A chore is not considered fully completed until a parent approves it.	1
Roommate profiles Chores and cleaning areas Weekly rotation and assignments Task completion and status tracking	1
1. Chore CRUD (create / list / edit / delete) 2. Assignee (assign a household member) 3. Completion toggle (done / not done)	1
Calendar publication in local server, configure chores in a YAML file, regenerate button, and fair repartition of chores	1
Search & filter: Cable list with faceted filters (family, signal type, length range, location, condition) + text search + a detail view showing both ends. Quick-add flow: One-page streamlined form to add a cable in a few keystrokes (two ends + length + location). Labels: Printable per-cable ID + QR that deep-links to the cable's page. Kits / looms + location tracking: Group cables into named bundles; move a whole kit between locations; recursive "what's in this case/location" view.	1
Core Mechanics: Preference-based fair share with per-chore cadences. Bidding & Assignment: Per-cycle preference bidding; resolves automatically via random draw tie-breakers as soon as all housemates submit their bids (First-to-Bid Threshold). Accountability: Simple overdue flags (no hard lockouts or reassignments). Multi-Tenancy: Multi-household support with a direct household picker and instant join.	1
- Single household only. No multi-tenant/multi-household support needed for v1. - Individual accounts per person	1
## Assignment Model - Fixed rotation - Runs on a custom fixed shift length (e.g. every 2 weeks), same cycle length for all chores ## Chore List - Templated defaults to start (dishes, trash, bathroom, etc.) - Roommates can add/edit custom or one-off chores ## Completion Flow 1. Person self-reports a chore as done 2. Another roommate peer-confirms it ## Accountability Mechanism - Visible status board only (done / not done / pending confirmation) - No reminders, escalation, or penalties — social visibility does the work	1
1. Chore claiming & fairness - members self-claim chores; workload-based fairness (weekly minutes, availability-adjusted) with warnings on unfair claims, shown as a rolling 7-day % with trend chart. 2. Recurring chores with on-demand occurrences - daily/weekly/monthly recurrence, due date or flexible window, auto-flagged overdue, no background jobs. 3. Points, badges & leaderboard - fun/status system separate from fairness: points on completion, milestone badges (10/50/100), always-visible leaderboard. 4. Household membership via join code - passwordless-style simple accounts, multi-household support with one active household, leave/rejoin preserving points but not chore history.	1
Customer management, Invoice generation, Inventory tracking, Sales reporting	1
- User & Household Management - Chore Management & Sharing - Monitoring & Activity History - Configurable Notifications	1
1. Household Management & Access Household Creation: Any user can create a household and set house rules/name. 2. Automated Round-Robin Chore Engine Chore Creation: Title, description, area/category (Kitchen, Bathroom, Living Room, Trash), frequency (Daily, Weekly, Bi-weekly, Monthly). 3. Dashboard & Visual Accountability My Chores" Tab: Personalized view of tasks due today, upcoming, or overdue. 4. Chore Swapping Swap Requests: If a roommate cannot complete a chore during their cycle, they can initiate a swap request with a specific flatmate.	1
Daily and weekly recurring chores Manual assignment, self-claiming, and automatic rotation Filterable dashboard with overdue labels Self-confirmed completion with activity history	1
housemates + point-scored chore catalog, log a completed chore, weekly Monday to Sunday leaderboard, recent activity feed	1
The spec settled on 4 features: 1. Chores CRUD — each household maintains a catalogue of chores (title, description, a points effort weight, active flag); any member can create / edit / delete them, always scoped to their own household. 2. Assignments — assign a chore to a household member with a due date; assignee limited to household members; an assignment is PENDING until completed or skipped, and is overdue when still pending past its due date. 3. Completion log — completing an assignment writes an immutable CompletionEvent (who, when, points awarded, optional note); a History page lists the household's completions newest-first, filterable by member. 4. Dashboard — the landing page: my pending chores, household overdue, recent activity (last 10), and a 30-day points leaderboard, plus the household's invite code. (Auth — register + create-or-join a household by invite code — is supporting infrastructure, not counted as one of the features.)	1
Single household, one shared chore list. 1) Household members roster, 2) chores with recurrence + due dates, 3) automatic rotation assignment among members, 4) completion tracking with overdue visibility. Written to _docs/plan.md.	1
-Project initialization and basic Django configuration. -Database setup and app integration (configuration.py/settings.py). -Task Traking and planning via backlog.md. -Automated testing configuration using pytest	1
1. A parent creates a chore with a title, optional notes, category, priority, due date/time, and optional cash reward. 2. The chore is either assigned to a child, available for a child to claim, or marked shared so multiple children may claim it. 3. A child marks the chore complete. 4. A parent approves it or rejects it with an explanation. A rejected chore returns to the child. 5. Approval adds the cash reward, when present, to that child’s unpaid balance. 6. A parent records a payout with amount and date, reducing the unpaid balance and preserving payout history.	1
- Each scheduled chore instance has a simple done / not-done checkbox. - Fixed and flexible chores are each a single row, with a checkbox that resets at the start of the chore's own frequency period (daily resets daily, weekly resets weekly, monthly resets monthly, etc.). - Ongoing items with no fixed period (insurance, dishwasher, cooking) are also plain checkable rows, with no automatic reset. - No due-time reminders, no streaks or missed-chore history, no notes field.	1
1. Sensor Node & Telemetry Ingestion: Register hardware IoT sensor nodes and ingest multi-channel measurements (voltage, current, temperature, vibration). 2. AI Anomaly Detection Engine: Automated evaluation flagging electrical overshoots, overcurrent and thermal runaway. 3. Telemetry Dashboard & Alert Feed: Query telemetry history and inspect flagged hardware anomalies.	1
Create and manage chores, assign chores to household members, mark chores as completed, and view the current chore list with assignees and status.	1
Users: roommates/couple, shared web app (persistent shared storage, same view on every device) Chores: preset list, daily + weekly only — just add names to get started Assignment: fixed rotation per chore, with manual swap between two people when needed Completion: checkbox + who completed it, kept as a history log Overdue handling: in-app visual reminder/nudge (no real push notifications — browser-only)	1
Shared Kanban Board with Open Task Pool: A single-board interface that categorizes tasks by status (To Do, In Progress, Done) while visually separating unassigned backlog chores from claimed tasks. Self-Serve Chore Claiming: A peer-to-peer claiming mechanism allowing any household member to self-assign open chores without needing managerial roles or permissions. Recurring Chore Lifecycle Automation: A state engine that automatically resets completed recurring chores back to the "To Do" column based on their defined recurrence schedule. Passive Staleness & Inactivity Indicators: Lightweight visual cues that flag neglected chores sitting untouched and highlight member inactivity without using rigid scoring or push notifications.	1
1. Household with roles — one household of up to six people; the first registrant becomes the sole administrator, everyone else is a roommate, and each account belongs to exactly one household. 2. Chore rotation — chores have a title, fixed points, daily/weekly recurrence, and a deadline (daily 23:59, weekly Sunday 23:59). Weeks start Monday; weekly chores rotate each Monday, daily ones keep the same assignee all week; overdue chores auto-transfer to the next roommate with no penalty; paused chores neither rotate nor score. 3. Complete → approve → points — roommates mark their chore done, the administrator approves (awards the fixed points) or rejects (returns it to the same roommate). 4. Weekly ranking — points totalled per member for the current week, reset every Monday.	1
• Target Audience: Families with kids. • Form Factor: Central shared home tablet / kiosk (touch-optimized, avatar selector, PIN-protected parent area). • Motivation System: Gamified Allowance Tracker (Cash earnings + XP, levels, streaks, and badges). • Task Engine: Hybrid (Mandatory daily routines + Optional claimable bounty board). • Verification: Kid captures photo proof via tablet camera → Parent reviews & approves via PIN. • Tech Stack: Django + SQLite + HTMX + Alpine.js + Tailwind CSS (No AI, pure deterministic logic).	1
Got long list of specifications, posting here just two of them: ## 2. Household and Members - The system supports one household. - A household is created by an owner. - The owner invites other members. - Everyone in the household can participate in chores. - The owner can remove a member at any time. - When a member leaves or is removed: - Their points and history remain. - Their active chores become available again. ## 3. Chores The system supports both: - One-off chores - Recurring chores A chore contains: - Name - Description - Points - Due date	1
1. Members & chores management: add household members and chores, each with an effort weight (1–5 points). 2. Auto-balancing assignment: each week the app assigns chores so every member's total weight per week lands as close to the equal target as possible. 3. Repeat discouragement: avoids giving the same person the same chore in consecutive weeks. 4. Weekly checklist: mark assignments as completed for the week.	1
* Task Assignment: Manual ("Chore Market" — users pick tasks from a shared pool). * Motivation & Tracking: Calendar and hard deadlines (no points, karma, or gamification). * Task Verification: Honor system (users click "Done", tasks close immediately without approval). * Task Generation: Fully manual (no automatic recurring or scheduled tasks).	1
- Family members — Designed for parents and children. - Age-based chores — Children can only claim chores appropriate for their age. - Recurring chores — Chores repeat on a defined schedule. - Chore details — Each chore has a name, frequency, description, deadline, category, and age range.	1
- Add dev skills - Select "High" effort in model -	1
1. A single shared TODO list with active and resolved sections. 2. Inline TODO creation and editing (title, optional description, optional due date). 3. Resolve and reopen TODOs, including overdue visibility and urgency-based ordering. 4. Confirmed permanent deletion of TODOs.	1
Chore Rotation, Due Dates & Deadlines, Manual Assignment	1
>Target audience: Roommates: Independent adults who need strict fairness, rotation, and minimal nagging >Task Allocation Strategy: Strict Fixed Rotation: Tasks cycle sequentially on a set schedule (e.g., Person A cleans the bathroom this week, Person B next week). (but i pushed back that people can trade or give tasks if consensual) >Verification & Accountability Model: Honor System (Trust): A simple checkbox where marking it "Done" closes the chore for that cycle. >Cycle & Recurrence Scope: Strict Weekly Cadence: All recurring chores reset on a single synchronized day (e.g., every Monday at 00:00).	1
- Shar- chore checklist — see all pending chores; any member marks any chore done; overdue items flagged. - Two assignment modes — admin assigns manually, or chores sit in a self-serve pool members claim and can release. - Recurring chores — fixed schedule (every Monday) and interval-after-completion (3 days after last done); completing one schedules the next. 4. Activity log — full household-visible history of who completed or un-completed what, and when.	1
Module 1: Sprint Planning & Canvas Module 2: Daily Standup Widget Module 3: SOS Practices & Micro-regulations Module 4: Transformational Reflection & Archive Module 5: Analytics Dashboard	1
getting list of items listing prices analyzing trends of listings	1
1. Project management: CRUD for the case-study systems (name, architecture style, LOC, role). 2. Question catalog: questions linked to a project, categorized into 5 types (structure, pattern, dependency, usage, evaluation questions). 3. Ground Truth answers: one validated reference answer per question, with validation notes.	1
Assignment Management: Create and view homework assignments with custom titles and detailed descriptions. Timestamp Tracking: Automatically record and display the creation time for each assignment. Admin Interface Integration: Manage assignments via the built-in Django administration panel.	1
Gamified approach Family members can earn xps by fulfilling a chore Approval workflow: Chore fulfillment has to be confirmed by other family member Winner perk is selected at the beginning of each weekly cycle	1
Automatic Wi-Fi Channel Selection – The system automatically identifies and selects the best available Wi-Fi channel. Interference Detection – It analyzes nearby Wi-Fi networks and detects channel congestion and interference.	1
1. Least-recent auto-rotation. Each period the system assigns every recurring chore to whoever has not done that chore for the longest time. 2. Skip / overdue bounty board. If you skip or miss the deadline, the slot is posted for neighbors. The first other roommate who claims it does the chore and gets paid. 3. Rising fixed-price bounty + IOU ledger. The bounty starts at a catalog price (you cannot set your own). Every day it sits unclaimed, it grows by a household interest rate. The app records who owes whom; money moves outside the app.	1
1. Households & roles — one person creates a household and invites members. Roles: owner, co-admin, member. Owner and co-admins manage chores; members only do them. 2. Chores — admins create and assign chores. One-time or recurring (daily, weekly, monthly). Each chore has a title, assignee, and due date. 3. Chore status & reassignment — assignee marks a chore done. Chores past due show as overdue. In-app notifications for due/overdue chores. A member can request reassignment; an admin picks a new assignee. 4. Activity log — history of what was completed, by whom, and when. Viewable per household and per member.	1
Add and view household members. Create and assign a one-time chore with a title, assignee, and due date. View active chores with their assignee and due date. Mark a chore complete and display it in a separate completed section.	1
The spec settled on these four MVP features: 1. Household creation and approved access. 2. A shared Kanban chore board. 3. Chore assignment and completion. 4. One-time and weekly chore scheduling.	1
# Project Specification: Household Chore Manager (`chore_manager`) ## 1. Overview A web-based tool for managing shared household chores designed specifically for couples and partners. The application emphasizes quick coordination, shared visibility, and effortless task delegation without feeling transactional. ## 2. Target Audience & Dynamic - User Group: Couples / Partners sharing a household. - Core Need: A low-friction, transparent way to see what needs to be done around the house and claim tasks organically. ## 3. Core Feature Set ### 3.1 Chore Management (Shared Backlog / "Grab Bag" Model) - Unassigned Backlog: Central list of all open chores that need attention. - Task Claiming: Either partner can easily claim a task from the backlog to signal they are taking care of it. - Task Completion: Mark claimed or unassigned tasks as completed. - Chore Attributes: - Title & Description - Category (e.g., Kitchen, Bathroom, Living Room, Outdoor, Errands) - Priority / Urgency (Low, Medium, High) - Estimated Time / Effort (optional) ### 3.2 User & Household Management - Simple partner authentication (Django Auth). - Shared household workspace so both partners see the same live backlog and status. ### 3.3 Dashboard & Activity History - Dashboard: Overview of currently claimed tasks ("My Chores") and available tasks ("Backlog"). - Activity Log: History of completed chores for shared visibility and appreciation. ## 4. Technical Architecture - Backend Framework: Django (Python) - Database: SQLite (Django default) - Frontend: Django HTML Templates + Basic CSS / Styling - App Module: `chores` app inside `chore_manager_proj`	1
Rotating assignment Interval recurrence after completion Households joined by invite code Completion history	1
1. Log a price sighting — item name (with brand/variant), shop name, price, date seen. 2. Price movement per item per shop — compares the two most recent sightings at that specific store to show whether the price went up, down, or stayed the same, regardless of visits to other stores in between. 3. Current cheapest shop per item — computed from each shop's most recent sighting. 4. Stale entry flagging — sightings older than 30 days are visibly marked stale so outdated data isn't mistaken for current pricing.	1
- Simple named profiles with password, no email - Roles & permissions - Admin and manager roles can create, edit, and assign chores. All others can view chores and marke their own assigned chores as done - Supports both recurring chores (e.g. trash every Tuesday) and one-off/ad-hoc chores	1
- Who this is for -> Just me, solo tracking - Where do you want to use this tool -> mobile-friendly web app - core scheduling model -> recurring + one-off tasks - how should app remind -> passive view only - where should data live -> local file/DB, self-hosted	1
The MVP settled on four things: 1. Households with invite-only membership and two fixed roles (admin / member). 2. Chores with due dates, priority, effort, categories, and recurrence (daily/weekly/monthly). 3. Assignment as either fixed people or claim-it-yourself; completing or skipping (with a reason) is tracked. 4. A simple dashboard - your assigned chores, with overdue derived at read time.	1
- Shared household view - Multiple users - Chore assignment - Status tracking - Recurring chores - Reminder logic - Basic reporting - Gamified points and rewards	1
Core features in scope: Household management — create/join a household, invite members, roles (admin/member) Chore CRUD — create chores with name, description, frequency, difficulty/points Assignment engine — manual assign, auto-rotation schedules, or open-claim board Completion tracking — mark done, verify, earn karma points Leaderboard & stats — fairness scores, contribution history, streaks Notifications — in-app alerts + email digests/reminders for upcoming/overdue chores PWA shell — installable, offline queue for marking chores done	1
1. Branching financial quests — Short, illustrated scenarios where choices create meaningful, non-judgmental consequences. 2. Gamified progression — XP, levels, achievements, badges, cosmetics, unlocks, and Saving mastery make learning feel like an adventure. 3. Adaptive open-world journey — Players freely explore financial zones while deterministic recommendations suggest useful next quests based on their goals and previous choices.	1
1. Ability to create project 2. Ability to view list of created projects 3. Form for completing feedback	1
The spec settled on 4 features: (1) a "Today" screen listing chores due today, ordered by date; (2) three chore types - every N days, specific weekdays, and one-off; (3) a one-tap "Done" self-report that logs completion and reschedules recurring chores; (4) a weekly points summary per household member.	1
Create chores, view available chores, claim chores, and mark claimed chores as completed.	1
My project is for weekly with my repos on GitHub, so, this is the 4 features: Portfolio triage — one-time pass that sorts every repo into showcase/hide/delete and makes dead weight private Weekly retrospective — Monday report from GitHub history alone: went well / went wrong / mid-flight / this week's focus Project lifecycle tracking — explicit shipped / paused / dropped, so ended work leaves the report AI coaching — one batched LLM call that names portfolio-wide behavior patterns	1
1. Multi-household management: Users can create or join multiple households with isolated data. 2. Role-based membership: Each household has one Owner, at most one Admin, and regular Members with clear permissions. 3. Chore lifecycle management: Admins create and assign chores; Members move assigned chores through Pending → In Progress → Completed. 4. History and organization: Chores support due dates, priorities, optional categories, soft deletion, duplication, filtering, sorting, and completion history.	1
1. Anonymous weekly check-ins with a short personal section plus project-specific feedback. 2. Adaptive AI follow-up questions that ask for more detail only when useful, while keeping the check-in short. 3. Separate team and manager summaries, with managers seeing deeper risks, trends, and anonymous supporting evidence. 4. Early issue detection and recommended actions, including severity scoring for delivery, workload, collaboration, and recurring concerns.	1
- Backend: Python (FastAPI) — easiest for wrangling academic APIs and any ML/embedding work - Frontend: Next.js / React — dashboard-style UI, mature ecosystem - Database: Postgres — cache API results and computed scores, avoid hammering rate limits - Ranking: start with a weighted formula (transparent, debuggable) before reaching for ML re-ranking	1
Parent and Child roles User accounts with login Household management, with one Parent/owner per household	1
Adults create recurring and one-time chores. Chores rotate by child/teen/adult eligibility, balanced by easy/medium/hard effort. Dashboard shows today’s assignments; calendar shows chores and deadlines only. Completion uses trust, household approval, or parent-selected photo proof. Missed chores get a grace period, reminders, and adult manual reassignment.	1
- Backend: Python + FastAPI - Frontend: React (TypeScript) - Database: PostgreSQL	1
1. Automatic weekly chore rotation — roommates are automatically assigned an apartment area every Monday using a fixed rotation. 2. Individual chore checklists — each area contains multiple tasks that roommates can mark complete/incomplete. 3. Shared weekly dashboard — everyone can see all roommates' assignments and overall completion progress. 4. Chore history — past weeks are saved and can be reviewed with assignments and task completion status.	1
1. Roommates & chores setup — add roommates and define recurring chores with a repeat frequency (weekly, fortnightly, etc.) 2. Automatic rotation — the app assigns each chore to the next roommate in turn on its schedule, so nobody has to divvy things up manually 3. Check off + points — mark your assigned chore done, earn points for completing it 4. Shared dashboard — one view showing the rota / whose turn it is, overdue chores, and the leaderboard	1
Create household members Create chores with assignee and due date Mark chores as complete View pending and completed chores separately	1
1. Household members — add / list / deactivate / remove the people on the rota 2. Chore catalog — recurrence (daily / weekly / biweekly / monthly), 1–5 difficulty, an assignee 3. Mark done — logs a completion, awards points, rotates the chore to the next active member, and rolls the due date forward (plus snooze) 4. Dashboard, leaderboard, history log and fairness stats (points per member, late rate)	1
Similar to the video Being able to leave notes for meetings for stand up, what went well, blockers next steps, upload video for transcript create actions from transscript anonomisation of who is putting commets / actions	1
## Users & Access - Simple login (email/password) per user - Household of 2, linked via email invite (one user invites the other by email) - Equal permissions — either user can create, edit, delete, or reassign any chore ## Chores - Manually assigned to a person (no auto-assignment/rotation/claiming) - Support both: - Recurring chores (daily/weekly/custom schedule) - One-off chores (added as needed, no repeat) ## Tracking - Checkbox to mark a chore as done - Records timestamp and who completed it ## Reminders - Scheduled reminders based on due date/time (automatic) - Manual nudge — either user can trigger a reminder for a specific chore - Delivered via: - In-app (visible when the app is opened) - Email	1
1) Allow users to claim unassigned chores and release claimed chores. 2) Allow users to mark their claimed chores as done and award points. 3) Implement chore trade proposals, acceptance, and rejection. 4) Track user points and provide a leaderboard ranking.	1
Chore & person setup, weekly rotation, current week view, history	1
household members, chore catalog with a cadence in days, rotation assignment that auto-advances, overdue/today/upcoming dashboard.	1
2. A. Full multi-tenant: user accounts, each user joins/creates a household, data isolated per household 3. C. + Rotation (auto-assign to next person each cycle) and points/fairness tracking 4. A. Points per chore; dashboard shows each person's total for the period	1
1. 6-question psychological distress assessment 2. Automatic K6-based score calculation and cutoff interpretation 3. Local history saved in the browser 4. History page with a trend chart and past scores	1
Status board — every chore grouped Done / Due / Overdue; chores auto-mark done when the due date passes, anyone can flag one "not done" (→ Overdue until cleared) On-screen digest banner — what's due and overdue today, shown on the shared tablet (no external delivery) Cover pool — a member marks themselves out for a date range; their chores in that window become claimable by anyone In-app admin screen — add/edit/remove members and chores, set fixed owners and recurrence rules (interval / weekdays / after-completion)	1
1. Custom points store — children earn points for chores and spend them on rewards the parents define and price themselves ("1 Hour Screen Time" = 50 pts, "Pizza Night" = 200 pts). 2. Parent approval — chores are never auto-completed. A parent reviews the work and clicks Approve before any points reach the child's ledger.	1
1. Membership: Invite-only; each person has their own login 2. Who sets the week: Automatic rotation (app), not a manager picking each week. 3. Marking done: Anyone can complete any chore; credit stays with the assignee	1
# Hotel Maintenance Tracker — v1 Scope ## Access - Shared desktop dashboard, no login required - Staff pick their name per task (no accounts, no roles/permissions) ## Task Creation - Only front desk / management can create tasks - Staff report issues to front desk/management, who log them in the system ## Task Fields (all required) - Title - Description - Picture - Picture when task done - Status: Open / In Progress / Done - Priority: Urgent / Normal / Low - Location: Room number / area ## Assignment - Manager manually assigns each task to a specific technician - No self-claiming or auto-assignment in v1 - Status Done only with picture task done uploaded ## Execution Team - In-house maintenance team (multiple technicians) ## Recurring / Preventive Maintenance - Supported alongside reactive (break-fix) tasks - Fixed-interval scheduling (e.g. every 7 / 30 / 90 days) - New task auto-created when interval is due - No specific calendar-date scheduling in v1	1
1. Create chore + assign to roommate 2. Shared chore list (visible to all) 3. Mark chore as Done (checkbox) 4. Household + roommates (the context that makes the list shared)	1
1. Weekly Start / Stop / Continue feedback - Team members submit separate cards. - Cards are attributed by default, with optional anonymity per card. - Before reveal, users only see their own feedback. 2. Retrospective board with clustering + voting - Facilitator reveals all feedback at once. - AI suggests thematic clusters, but the team can edit them. - Each participant gets 3 stackable votes. - Vote totals stay hidden until voting closes. 3. Discussion outcomes and action items - Topics are discussed in vote-priority order. - Topics can be marked Discussed, Skipped, or Deferred. - The team records notes, decisions, and simple action items with owner, optional due date, and Open/Done status. 4. Meeting record upload + AI-assisted summary - Facilitator can upload audio, video, transcript files, or paste transcript text. - The system suggests decisions, action items, owners, due dates, and a short retrospective summary. - Nothing AI-generated becomes official until the facilitator reviews and confirms it.	1
.	1
User authentication, data visualization, CSV upload, and model prediction.	1
- Weekly planning session — the group opens the app together and defines the week's chore list, assigning each chore to a person. - Daily use — anyone can open the app, log in with their PIN, and check off chores as they complete them. - Missed chores — if a chore isn't checked off, it simply stays visibly undone. No punishment, no auto-reassignment. - History review — anyone can look back at past weeks to see who completed or missed which chores.	1
Households — create a household (a name), it holds members and chores. Members — add people to a household (just a name, no login). Chores — add a chore: title, assigned member, frequency (once/weekly), done flag. Chore list view — see all chores for a household, who they're assigned to, done or not.	1
Create and assign household chores; set an assignee and due date; mark chores as completed; view a list filterable by person and status.	1
- create new tasks - delete tasks - sort and filter tasks - search specific tasks	1
1. Chore list with point voting Any adult can add a chore (name, description, date/time it's needed, and whether it's recurring or a once-off). Members vote a point value; the chore's weight = average of votes. 2. Claiming Members claim an open chore. For recurring chores, claiming is "just this week" or "ongoing until protested." Once-off chores are claimed once and marked done — no weekly cycle for them. 3. Reassessment / protest Applies to recurring chores' point values and ongoing claims — claimant or others can protest, reopening the vote. 4. Fairness tracking Everyone's claimed points (from both recurring and once-off chores) vs. their target share of the total.	1
Shared chore board - 1. all household members see the same chores 2. each chore has title, assignee, due date, and status Assign and update chores - 1. assign tasks to a person 2. change status: pending, in progress, completed 3. quick updates without extra steps Household member management - 1. sign up and log in separately 2. one household per account 3. add members to the same home Activity tracking 1. show who created or completed a chore 2. simple recent activity log for accountability	1
- Name picker (no login): on first visit, choose your name from a dropdown; remembered on that device. - Add chores: create one-off tasks or recurring tasks (daily, weekly, custom interval). - Assign chores: to a specific person, or leave open/shared for either person to claim. - Track status: mark a chore Pending → Done; overdue chores are flagged automatically. - Reminders: in-browser pop-up notification ahead of a chore's due time. - History log: view past completed chores — who did what and when. - Multi-device sync: both people see the same live chore list from their own device.	1
- Individual family-member accounts managed by a parent/admin - chores that can be assigned to one or multiple members or left unassigned to be claimed - helper approval and per-member completion - daily, weekly, and monthly recurring chores	1
Members and chores — manage the household roster (name, active flag) and a catalogue of chores, each with a name, optional description, and a recurrence (daily / weekly / monthly). Automatic rotation — each chore holds an ordered rotation of members. Completing an occurrence (or letting its due date pass) generates the next one for the following member, due one recurrence period later. Dashboard — the home page shows chores that are overdue, due today (grouped by assignee), and coming up this week, plus a per-member count of open chores so imbalance is visible. Completion history — an append-only log of completions (chore, member, due date, completed-at), filterable by member and by chore.	1
Create a chore with title, assignee, due date, and recurrence View all incomplete chores in one dashboard Filter chores by household member Mark a chore as complete and flag overdue chores	1
1. Invite-only households with user accounts. 2. A shared, household-specific weekly chore list. 3. Chores that can be assigned to someone or self-claimed. 4. Completion history plus automatic creation of the next weekly chore occurrence.	1
Weighted Points: Tasks are valued by effort/time, not flat counts. Hybrid Catalog: Preset chore library plus custom tasks with adjustable values. Two-Way Sign-Off: Completions require partner approval before points credit. Perk Economy: Banked points redeemable for agreed household rewards.	1
1. Claim-base chores - members voluntraily claim from a shared board 2. Escalating in-app reminders - unclaimed chores get nagging reminders until claimed 3. Points & leaderboard - each chores has points, standings shown per household 4. Self-mark complete with dispute window - claimer marks done, others can flag within a time limit	1
1. Household members 2. Chore creation/editing 3. One-off and repeating schedules 4. Fixed and rotating assignments	1
1. Chore catalogue — add chores, each with an effort weight 2. Member roster — add/list household members 3. Completion log — record that a member did a chore, on a date 4. Fairness dashboard — points per member over the window, plus a suggested next owner per chore	1
1. Shared chore list with definitions and occurrences — anyone adds a definition carrying assignment mode, recurrence, duration, difficulty, and skill requirements. Each due instance is a separate occurrence that keeps its own values and history. 2. Constrained scheduling — rotation filtered by skills and availability as hard eligibility rules, with a one-line explanation on every assignment. When nobody qualifies: push and flag, or stretch-assign to someone who opted in. Overdue flags but never silently reassigns. 3. Photo log with approval — required photo, assignee picks the approver, confirm or reject with a written reason. Rejection sends it back to the same person; admin decides after two. Approval of a stretch chore adds the skill. 4. Weighted scoring on an append-only feed — duration × difficulty per person, fixed estimates rather than self-reported time, monthly reset, feed persists with corrections recorded rather than overwritten.	1
1. Add and view household members. 2. Create chores with an assignee and due date. 3. Mark chores as completed. 4. View outstanding, overdue, and completed chores on one dashboard.	1
The specification settled on four main features: 1. Household management—users can create or join a household and manage household membership. 2. Chore management—users can create, assign, edit, complete, and delete chores, with due dates and recurrence. 3. Dashboard—users can see pending, assigned, upcoming, overdue, and completed chores. 4. AI-assisted chore suggestions — users can describe their needs in natural language and review AI-generated chore suggestions before confirming them. This feature was partially implemented. During development, we encountered a Codex CLI quota limitation, so we continued the remaining work manually. We also could not configure a real OPENAI_API_KEY, so the complete AI generation workflow could not be manually tested.	1
- Description: What needs to be done - Priority: High, Medium, or Low - Status: Pending or Completed - Completion History: Who completed it and when	1
- Support both recurring (daily/weekly templates) and one-off ad-hor chores, each with a point value - Chores sit in a shared pool; people claim them; system tracks per-person points to keep workload fair - Unclaimed/overdue chores get auto-assigned to whoever has the lowest point - Leaderboard of point totals + a history log of who did what and when	1
1- User Authentication 2- GDPR compliance 3- Using ontology for data flexibility	1
- Governance modes (Peer-to-Peer vs. Hierarchical households) - Task mechanics & lifecycle (one-off/recurring tasks, checklists, flexible instant-vs-admin-verified completion) - Real-life scenarios (drop/can't-do, overdue tracking, blocked state with reason, vacation/away mode)	1
Build a simple website for families to manage shared household chores. The primary goals are: 1. Reduce the need for parents to repeatedly remind family members about chores. 2. Motivate participation through points, streaks, and rewards. The MVP is intended for the whole family: parents and children. Parents can: - Create chores. - Assign chores to a specific family member. Family members can: - View today's chores. - View chores assigned to them. - Earn points. - Build streaks.	1
- Rotation tracking that only moves a chore to the next person when marked done - No accounts/login — single household scope - Works on both shared devices (e.g., fridge tablet) and individual phones/browsers - Overdue chores show a visual indicator (highlight/red), no notifications	1
## Overview A local web app for tracking shared household chores. Only one person (the user) operates the app, but chores are tracked per household member. ## Stack - Backend: Django - Database: SQLite - Interface: Local web app (no auth/login) ## Scope ### Household Members - Simple CRUD (create, edit, delete) - Fields: name only - No accounts, no passwords — just a name picker used when assigning/completing chores ### Chores - Fields: - Title - Description (optional) - Assigned member - Recurrence rule (e.g. daily, weekly, every N days) - Due date - Full CRUD (add/edit/delete) ### Recurrence - Chores support recurring schedules (e.g. "vacuum every Monday", "trash every 3 days") - Marking a chore complete automatically generates the next occurrence based on its recurrence rule ### Views - Full chore list: shows all chores with due dates visible; filterable/sortable by member or date - Add/edit/delete chore form - Mark complete action on each chore	1
Client IP Detection, Proxy Support (X-Forwarded-For), JSON API Endpoint	1
## 2. Core data models and database migrations ## 3. Dynamic interval and next-trip prediction engine ## 4. REST API endpoints and Token Authentication	1
authentication and store authentication on local sqlite database managing one household only where chore is completed mark has done and keep an history missed chores are marked overdue Members can be created manually or join via invite/code.	1
1. Tiered user roles, 2. Chore creation/assignment with recurring schedules 3. Completion tracking 4. Point-based dashboard	1
Two-Location Inventory & Stock Operations: Auditable & Recoverable Transactions: Local Demand Intelligence & Purchase Recommendations Local Backup, Restore & Reporting	1
1. Mother is the project manager and she should check and validate the chores done by other family members. 2. Father should wash and clean the car every Saturday. 3. Children should be given badge after each task they complete	1
- User registration with email/password via Supabase Auth - Create household with custom name and automatic invite code generation - Frequency options (one-time, daily, weekly, monthly, custom) - Weekly view with time-block scheduling	1
1. Household and member management with admin/member roles, email magic-link sign-in, and PIN-protected profiles for members without email. 2. Chore creation and scheduling with basic recurrence, manual assignment, fixed round-robin rotation, and self-selection. 3. A mobile-friendly chore workflow: today's and upcoming chores, completion with optional notes/photos and admin approval, plus reassignment or skipping with a reason. 4. In-app reminders and basic workload visibility through assigned/completed chore counts.	1
1. Multitenant workspaces — links live under a tenant prefix (/{workspace}/{code}), a user can belong to several workspaces, and the same code in two workspaces is two different links. 2. Custom slugs — pick your own short code or get a generated one; codes are unique per workspace, not globally. 3. Link expiry — a link can be given an expiry date, after which it returns 410 Gone instead of redirecting. 4. Click analytics — every hit records timestamp, referrer and user agent; each link shows a total and a 30-day per-day chart.	1
Templates Testing Features Task	1
1. Member & Chore Management 2. Automated Weekly Rotation 3. Completion Check-in & History	1
1. Household setup and onboarding 2. Chore configuration 3. Automated cycle execution 4. Personal task execution and tracking	1
A fully local AI-powered desktop application built with Django that acts as a personal electronic music production mentor and audio analysis system for Ableton Live.	1
Chore Assignment Chore Tracking Notifications/Reminders Reporting	1
Users: You + partner, shared WhatsApp group Chores: Start with a fixed list, add more anytime via chat Assignment: Claim-as-you-go via buttons ("I'll do it") Logging: Tapping claim immediately prompts for time spent (single step) Fairness metric: Self-reported time, not task count	1
From module_1/_docs/plan.md, v1 settled on things like: Invite-code join (no email/password) Admin vs member roles (admins manage templates; anyone adds one-offs) Open shared list with claim / release / complete One-offs + recurring templates that spawn chores	1
- Project: Household Chores Manager (family of 4, shared login, no individual accounts) - Fixed weekly chore assignments + daily checklists, daily/weekly time budgets per person, instant chore swaps between family members (kids' edits require adult approval) - Tracking: check-off completion + log actual time spent, warning only (no blocking) on budget overrun, full visibility of everyone's status and weekly history - Notifications: before a scheduled time block starts, for unfinished daily chores	1
The 4 main features are: 1. Weekly household chore list management 2. Fair task allocation based on each member’s workload 3. Task assignment and completion status tracking 4. Weekly history of assigned and completed chores	1
Flexible task pool — recurring templates + manual ad-hoc adds, no fixed schedule Auto-assignment — bot balances tasks between you two based on recent activity Escalating reminders — nudge, then stronger nudge if still undone Recent-only history — short log (7–14 days) to power fair assignment, no long-term stats Delivered via a Telegram bot in your shared chat.	1
1. Create and manage household chores. 2. Assign chores to household members. 3. Mark chores complete and record who completed them. 4. Award and display points for completed chores.	1
Add an expense; view all expenses; filter expenses by category; display the total amount.	1
1. Manage household members 2. Create and edit chores 3. Rotate chore assignments automatically 4. Track chore status and workload	1
Users: adults only, one household, real accounts (Django auth: signup, login, password reset), each on their own phone. Core loop: task list → tap to claim → tap to complete → points land on a shared weekly bar → 🎉 screen when the goal is hit. Completions can be undone. Tasks: recurring catalogue (regenerated each week) + one-off tasks added on the fly. Each task has a name and a weight (effort/unpleasantness) that equals its points. Goal: one weekly point target, resets Monday. No streaks, no carry-over, no rewards.	1
Status Board — real-time view of today's chores: done, pending, overdue Chore Assignment System — mix of fixed/rotating assignments and self-claimable chores, fully custom creation by admins History Log & Ownership Map — who did what over time, and who owns which chores (full transparency, no scoring) Flag & Escalation — passive overdue/unclaimed flags that escalate to an admin if unresolved	1
Chore Management — Create, edit, archive, assign, and set recurring frequencies for household chores. Automated Round-Robin Rotation — Automatically rotate chore responsibility among active roommates when a chore is completed. Overdue Tracking — Show upcoming, due-today, and overdue chores with a persistent overdue warning. Household Activity Feed — Display a chronological history of recent chore completions, including who completed each chore.	1
Create and assign household chores; set due dates/recurring chores; mark chores as completed; view all chores and their status on a shared dashboard.	1
Designing an automated recurring payment application which will accept inputs from user for automatic deduction of amount every month for a particular policy	1
1. Automatic, weighted assignments: each week, chores are randomly assigned across ethe 5 household members, biased by each person 's accumulated chore weight over time, so no keeps getting stuck with the heavy chores. 2. Self-checkoff: each person marks theirown chores done from one shared device. 3. Weekly cycle with automatic rollover. 4. Single shared device, no accounts.	1
1. Who's it for? → Small shared household (2-6 people, roommates or family). Considered: solo tracker (too simple, no "shared" problem to solve), large family with kids/rewards (adds complexity — points, parental controls — that's a v2 concern). Shared household is the core "chores are contested/shared" problem worth solving. 2. Platform? → Web app (mobile-responsive). Considered: native mobile (higher dev cost, app store friction), CLI (wrong audience — housemates aren't all technical). Web is accessible to everyone in a household with zero install. 3. Core problem to solve? → Fair assignment + visibility of who did what. Considered: pure reminder/notification tool (doesn't solve fairness), point/reward gamification (nice-to-have, not core). The #1 real-world pain point in shared households is "did you even do the dishes?" and "why am I always the one who does X?" — so assignment + accountability is the spine. 4. Assignment model? → Recurring rotation (chore auto-rotates to next person on a schedule), with manual override/swap allowed. Considered: pure claim-based (first-come, leads to nobody claiming unwanted chores), fixed permanent assignment (unfair over time, no flexibility). Rotation guarantees fairness by default; manual swap handles real-life exceptions.	1
The spec settled on these four core features: 1. Create and assign chores to family members. 2. Track chore completion and view status. 3. Support one-time and recurring chores. 4. Send reminders for upcoming or overdue chores.	1
Add household members Create and assign chores Track chores as open or completed Filter chores by status and assignee	1
1. Shared Chore Management — create chores with a frequency and point value, and see what is due or overdue. 2. Chore Completion & Points — select the member who completed a chore, mark it done, and award the points automatically. 3. Member Views — each roommate has an individual view showing their monthly points, lifetime XP, and completion history. 4. Garden Progression — each member has a garden that grows with lifetime XP, plus a shared neighborhood view showing everyone’s gardens together.	1
Shared household management with email invitations and administrator roles. Customizable chore catalog with one-off and recurring chores. Automatic chore assignment based on equal distribution and estimated effort. Configurable completion and reminders, including due-date alerts and household-specific approval rules.	1
## Users - Small household, fixed group of people (no multi-household support) - Each person has their own view and checks off their own chores ## Assignment - Fixed rotation (e.g. dishes Mon/Wed/Fri, rotates weekly) - No self-picking, no auto-balancing algorithm	1
View a dashboard of chores with due date, assignee, and status. Create and edit chores. Assign or reassign chores to household members. Mark assigned chores complete or return them to pending.	1
The main features are: - Team members submit weekly Start/Stop/Continue feedback. - Contributors can choose to submit feedback anonymously. - A facilitator reveals all feedback at once, after which the team can cluster cards and vote on discussion topics. - The team records decisions and action items from the discussion	1
1. The app has one shared family account with no need for individual authentication. A user can select a family member profile. 2. Admin can create a chore and assign it to a family member so that responsibility is clear. 3. Admin can create a one-time chores for occasional household tasks, and recurring chores, for tracking regular household responsiblilities. Admin can also edit and delete a chore. 4. Family member can see the chores assigned to him/her and all household chores.	1
## Chores Each chore contains only: - Name - Frequency - Effort points Supported: - One-time chores - Recurring chores - Daily / weekly / monthly recurrence - Custom recurrence (e.g. every 3 days, every 2 weeks) ## Smart Assignment The assignment system considers two factors with equal priority: - Fairness — distribute effort points reasonably across members. - Preferences — respect member preferences. Each member can mark a chore as: - Like - Neutral - Dislike There is intentionally no availability system. Assignment is triggered manually, and the user chooses the assignment period each time. Members can swap assigned chores after assignment.	1
Anyone can assign a chore (S / M / L) to anyone else. The receiver accepts, declines, or sends it back. Accepted chores go on a personal week board (Mon–Fri); leftovers land in a weekend catch-up pile. Mark done → points (more if someone else assigned it). Household scoreboard + weekly winner with silly titles.	1
Household member management; chore creation, editing, and deletion with assignees, due dates, and difficulty points; a weekly board for pending, completed, and overdue chores; and a workload summary with planned and completed points.	1
1 - Chore management — create, edit, activate/deactivate chores, and use a predefined chore catalog. 2 - Weekly planning and daily execution — generate recurring chore occurrences, assign or reassign responsibilities, manage due dates, complete or cancel chores, and handle overdue items through the Week and Today views. 3 - Workload visibility — compare planned versus actual effort, including who completed each chore. 4 - History and household settings — preserve weekly summaries and completed work, while allowing the household members to be configured and renamed.	1
- no db, one device, simple division of labour between two partners, recurring tasks with intervals, categories, mobile-friendly design (for future porting & actual db)	1
Being able to manage roommates Being able to add chores Being able to add recurring chores Being able to rotate recurring chores among selected roommates	1
The spec settled on four main features: Activity management – create, edit, archive, and organize extracurricular activity groups by school year. Automatic viability status – classify activities as At Risk, Confirmed, Full, or Waiting List based on registrations and min/max capacity. Registration tracking and history – update aggregate registration numbers and keep historical snapshots of changes. Dashboard and filtering – view the current state of activities and search/filter them by relevant criteria.	1
Add authenticated user accounts and profile access Build teams, memberships, and team-manager controls Create retrospectives and manage their lifecycle Build the dashboard and retro lobby	1
Create and manage household members Create chores and assign them to a household member Mark chores as completed View pending and completed chores	1
1. Chores with custom repeat (house/cat/garden basics) 2. Kanban: To do / Today / This week / Doing / Done 3. Manual assign + overdue highlight (email/push deferred)	1
Household and member management; chore creation and assignment; completion submission with administrator approval/rejection; recurring chores with deadlines, calendar, points and rankings.	1
- Managing home maintenance checklists and recurring routines for one person. - Telegram bot - Task cycle: Hybrid between Strict intervals and dynamic from completion date - Text / Slash Command in Telegram	1
* supports multiple households (PIN access for simplicity for MVP, rather than secure login) * points system: chores are assigned points and users build up points that reset each week * non-completed chores roll over to next week	1
Fixed weekly schedule: all chores reset every Friday. Simple done/not done toggle. Markdown file storage for chore names and statuses. No completion history; only the current week is tracked.	1
1. Student Dashboard — students can view classes, attendance, assignments/deadlines, academic performance, syllabus progress, and topics requiring review. 2. Teacher Dashboard — teachers can create/manage classes and monitor students, attendance, assignments, performance, and syllabus progress. 3. Assignment & Attendance Management — teachers create assignments and attendance sessions; students submit assignments and check in to active attendance sessions. 4. Academic Progress & Syllabus Tracking — teachers manage syllabus topics and completion; the system calculates progress; students can flag topics for review.	1
Household members; chore board (title, notes, assignee, due date); mark done / reopen; fairness snapshot (open vs completed counts per person)	1
Note that I altered the focus slightly to "tracking recurring household tasks". Feature highlights: * Data layer is a yaml file, human editable, with one entry per task. * Due-date logic: Interval tasks (on completion, reset days till due), Fixed cycle tasks (like every Monday), Snooze until date. * CLI-based interface supporting commands like ```tasks due``` (to list what's due and upcoming), ```tasks done``` to register task completions and trigger related data management, and ```tasks snooze``` to snooze tasks. * maybe Gmail SMTP notification pipeline	1
I worked on a chat room match app for language learners. Here are some features: 1. the room can be published on a lobby (according to the language) or a link can be sent (for private ones) 2. each room has exactly 2 learners with real-time chatting 3. a sidebar contains some phrases of that new language so mates can use it 4. for the person who created the room, there are many administrative options, making it good for interviews	1
1. Recurring chore management 2. Assignment + automatic rotation 3. Dashboard tracking 4. Household + completion history	1
Households & membership (individual login accounts), chore creation (title + due date), manual assignment to a household member, completion tracking (done/not done)	1
1) Tasks with assignment modes (direct + shared pool) and recurrence, (2) completion approval flow with before/after photos, (3) points-reward system with a catalog and auto-redemption, (4) history of completed tasks.	1
- [ ] Init Django project + app (`chores`) - [ ] Configure DB (SQLite for dev, Postgres for prod) - [ ] `Person` model (name, email) - [ ] View + template: Current state section (pending/done/overdue)	1
1. Weekly Chore List: Users can create and view a fixed list of chores for the current week. 2. Manual Assignment: Users manually assign each chore to one of the two partners. 3. Mark Chores Done: Users can mark each chore as done or not done. 4. Fairness Summary: The tool should show a simple weekly count of assigned chores per partner.	1
My specification settled on four core features: 1. Configurable workspaces for household, professional, educational, and custom use cases. 2. Collaborative task management with reusable task templates, available task pools, assignments, deadlines, completion tracking, grace periods, and reassignment rules. 3. Role-based workspace membership and access control, with data isolation between workspaces. 4. Optional gamification with configurable scoring, penalties, scoreboards, and workspace-specific reward catalog management.	1
Housemate selection without authentication. Adding housemates by name (no edit/delete/credentials). Chore management: create and edit chores with title, assigned housemate, due date, and completion status. A shared chore list where anyone can view chores and toggle completion.	1
1. Default Assignment Model: Automatic Rotation 2. Fairness Model: Simple Turn-Taking 3. Rotation Frequency: Weekly 4. Exception Handling: Manual Reassignment	1
chore management(create, assign, complete) reminders - todays' due, overdue streak and volume badges levels for earning badges	1
1. Household creation, invitations, and member roles. 2. Chore creation, scheduling, and assignment methods such as fixed, shared, pool, and rotating assignments. 3. Chore completion tracking, overdue chores, optional proof photos, and points. 4. Dashboards, calendars, chore swaps, rewards, and activity history.	1
Brainstormed the vague idea into a scope (full Q&A in _docs/brainstorm.md, spec in _docs/plan.md). The spec settled on 4 features: Household members - a roster of people; members can be deactivated so they are skipped in the rotation. Chore catalog - reusable chore definitions with a frequency (in days) and a point value. Rotation & assignments - "generate next round" assigns each active chore to the next member in round-robin order with a due date; the dashboard lists everything pending and flags overdue items; one click marks a chore done. History & points - a "who did what" log of completed/skipped chores and a points leaderboard per member.	1
1. Life Context Toggles (Home Base and Errand Run task views) 2. Smart Routines (recurring chores and pet-care tasks) 3. Automated Low-Stock Triggers (low stock creates restocking errand task) 4. Auto-Reset Inventory Loop (completing restock task marks item in stock)	1
Peer Approval Verification (tasks reviewed by another housemate), Assigned Inspector Roles (each chore has a designated reviewer), Automated Fixed Rotation (Doer/Inspector roles cycle automatically), Strict Calendar Scheduling (rotations advance on fixed dates regardless of pending approvals)	1
Manual assignment of chores , Reminders notifications , history of completed chores , comments section	1
1.core problem 2.household 3.assignment 4.daily view	1
I designed a shared household chore manager for families. Each family member has an individual login, with adult and child roles. The 4 main features settled on were: Family accounts and role-based permissions. One-time and recurring chores (daily, weekly, monthly). Today, Upcoming, Overdue, and completion-history views. Email reminders before, at, and after the due time. The final specification was saved in spec.md.	1
1. Automatic chore assignment 2. Chore management and tracking 3. Points and rewards system 4. Notifications and shared family dashboard	1
1. Two-person households — exactly 2 members with equal permissions, one household per account, invitation-based joining. 2. Recurring chores with occurrences — flexible cadence (e.g. every 7 days); each occurrence is a distinct completion/history record; minimal states (active → completed, with overdue derived); one primary owner by default, with selected chores supporting multiple contributors. No archive/pause/complex lifecycle. 3. Workload & fairness engine — each chore has estimated time + difficulty/effort; members can submit actual time/effort after completion; the system learns from history but only proposes estimate changes; fairness based on equal workload over time with hidden automatic decay; people↔chore preferences/exclusions; helper contribution credits that feed future assignments; fairness weights start configurable and can evolve. Estimate changes accepted individually; fairness-weight changes need household approval. 4. Automatic assignment — auto-assign respecting people↔chore constraints; assigned member stays primary owner; another member can claim/help for credit. No trade/negotiation workflow, no auto-reassignment for overdue. 5. AI setup — guided questions + free-form household description; AI generates chore list, cadence, time/difficulty estimates, inferable preferences/constraints, an initial assignment plan, and its reasoning. Chores/estimates can activate automatically; assignments require member review.	1
Household & member management — A fixed group of users (roommates/family) with accounts; no open sign-up Chore management — Chores can be assigned to a specific person OR set to auto-rotate on a schedule (configurable per chore during setup) Completion tracking — Anyone can mark a chore as done with a simple checkbox Status dashboard — A shared view showing all chores, who they're assigned to, and whether they're done or overdue	1
The 4 features the spec settled on: Effort-weighted auto-assignment — chores split by point value, not just count. Monthly fairness balancing — effort evened out over a rolling monthly window. Admin-defined chores & scores — one person owns the list and effort values. Tap-to-complete with roll-over — self-report done; unfinished chores stay with the assignee and carry their effort debt forward.	1
- Workout logging - Progress charts/trends over time, per exercise - Personal records (PRs) — auto-calculated best values per exercise, per metric - Goals — target values per exercise (e.g. "bench 200lb x5", "5k under 25min")	1
Browse NYC restaurants from an external dataset/API Search and filter by restaurant name, borough, and cuisine Let friends flag/unflag restaurants they want to visit Highlight shared matches when 2+ friends flag the same restaurant.	1
A web/mobile app that helps beginner and intermediate swimmers self-teach breaststroke through a curated, adaptive lesson pipeline with a plan → do → log core loop. 1. format: web/mobile app 2. target users: complete beginners and intermediate self improvers 3. core loop: Plan → Do → Log (tool assigns lesson, user swims, user logs results) 4, content source: Curated drill library, with adaptive sequencing based on logged progress	1
Chore tracking — recurring and one-off household chores Automatic rotating assignment — chores auto-rotate among up to 4 household members on a schedule Shared dashboard with self-report completion — one shared view, no login, members check off chores themselves Completion history log — a record of completed chores is kept over time	1
Multi-household product — each household is its own space Core problem: accountability (getting chores actually done, not just fairness/coordination) Completion: self-report, honor system Assignment: rotating through housemates on a fixed schedule Missed chores: nudge (reminder to the person) → escalate (visible to household) if still missed Visibility: personal reminders + shared household activity feed Setup: template chore lists + full customization Scheduling: fixed recurring (e.g. "Tuesdays") Roles: one admin per household manages members/chores; others just complete tasks	1
1 View current assignments 2 Mark chore done 3 Auto-rotate on fixed day 4 Flag incomplete chores	1
1. There were 2 users. They will have a single signon. 2. The app will allow the two users to split the bill. 3. The way they can be split can be determined by the user.	1
1. Create and manage chores — title, description, frequency, due date and completion status. 2. Assign chores to household members. 3. Dashboard showing pending/completed chores and assignees. 4. Complete/reopen chores.	1
Household Chore Tracker — v1 Scope Users: Family with kids, 3-4 people, no login (pick your name from a household link) Chores: Daily recurring, fixed assignment (same person = same chore every day) Visibility: One shared list, everyone sees all chores Completion: Self check-off (honor system), no photo/parent approval Missed chores: No escalation — just logged as missed in history Notifications: In-app only, no push Platform: Mobile-friendly responsive web app	1
- user should be authenticated by email + password - task should be assigned fairly based on people availability - there should be an admin that manage everything - there should be a dashboard to visualize task distribution and completion status	1
The spec settled on these 4 core MVP features: 1. Shared chore calendar - Month and week views - Chores shown by due date - Shows title, assignee, and status - Overdue chores remain visible 2. Chore management - Create one-time chores with title, description, due date, assignee(s), and category - Statuses: Pending, In progress, Done - Admins can edit chores before completion - Members can create chores only for themselves 3. Household member management - Admin creates member accounts with username + password + display name - Simple Admin / Member roles - Admin can remove members and manage assignments 4. Basic completion history - Everyone can view a chronological history - Shows completed chores and completion date - Reopened chores are removed from completion history	1
- Recurring daily and weekly chore scheduling - Capacity-weighted assignment among adults and children - Assignment reminders and completion tracking - Reassignment requests and organizer overrides	1
## 2. Core Features 1. Multi-Household Support: - Users are grouped into isolated "Households" (representing an apartment of roommates or a family). - All tasks, schedules, and members are scoped to the specific household. 2. Weekly Duty Roster & Swaps: - Automated or manual assignment of a "Duty Person" for the current week within the household. - Swap Requests: If the assigned person is unavailable, they can send a swap request to another household member. If accepted, their duty weeks are exchanged. 3. Task Management & Hard Deadlines: - Ability to create tasks (e.g., "Clean the floors", "Take out the trash"). - Each task is bound to a specific hard deadline (e.g., "by 12:00 PM", "by 8:00 PM"). - A visual board to track the status of current tasks (To Do, Done). 4. Telegram Notification System: - A background process that checks the status of the daily tasks. - Sends automated alerts to the current Duty Person via Telegram every 3 hours containing a list of pending tasks that must be completed today.	1
The main features are task management and assignment, recurring chores, points and family ranking, and completion history showing who completed each task and when	1
- One household. No accounts, no login. Members are just named people. - Chores with a fixed cadence and an explicit rotation order. - A schedule generated upfront, with assignees visible in advance. - Excused skips (illness, travel) vs. unexcused skips that accrue debt. - Debt repayment by taking extra turns.	1
- Separate Internships and Placements tracking - Add/Edit/Delete opportunities - Search and filters for opportunities - Track MSc Physics eligibility, application status, and Green/Yellow/Red chance	1
1. Rotation-based assignment — each chore has a recurrence (e.g. weekly) and automatically rotates to the next household member each period, instead of being assigned manually every time. 2. Mark done + history — a member marks their assigned chore as done for the current period; every completion (and who did it, and when) is kept in a history log. 3. Overdue flagging — chores that are due today or past due for the current period are visually flagged in the chore list, so nothing slips through unnoticed.	1
Setup screen, Rotation engine, Chore board, Cover/Swap, Weekly reset	1
- Create or join a household with a code and display name. - See today's chores, unclaimed chores, personal chores, confirmations, weekly schedule, members, and history. - Add, edit, delete, reschedule, claim, complete, and confirm chores. - Generate the next occurrence when a recurring chore is confirmed.	1
Features settled on: household membership, shared chore list, chore creation/assignment/claiming/completion, and recurring chores with completion history.	1
Household members, automatic chore rotation, chore management and completion history, and a dashboard with calendar.	1
Rotation logic: Per-chore rotation Household structure: Multiple households per install, invite-based Chore creation: Free-form + recurrence picker Completion tracking: Simple checkmark, timestamped	1
- Analyse CV and compare against job description - Optimze CV against ATS tracker - Download optmized CV	1
1. Household membership and roles - Members join with a persistent household code and a chosen, unique name. - A household can have multiple admins. - Admins manage members, invitations, and admin rights. - Members can leave; admins can remove members while preserving their history. 2. Chore planning and assignment - Support one-time and recurring chores. - Each chore has a title, exact due time, assignee, verifier, and optional instructions or image attachments. - Recurring chores support specific weekdays or dates, automatic next occurrences, an end date or occurrence limit, skipping an occurrence, and changing future assignees. - Admins create, edit, archive, assign, and reassign chores. - Members may propose chores; admins approve, reject, or edit proposals. 3. Completion and verification - The assignee marks a chore complete. - A designated verifier confirms it; the verifier cannot be the assignee. - Rejection returns the chore to open and requires a comment. - Admins may override, reopen, confirm, or cancel a chore. - Admins choose per chore whether a completion photo is required. Assignees upload the photo when marking the chore complete. 4. Reminders, escalation, and history - Show open, pending confirmation, completed, skipped, and overdue states. - Send in-app reminders at a configurable time before the due time. - Escalate an overdue chore to admins once when it becomes overdue. - All members can browse full history, including status changes, timestamps, people involved, and rejection comments.	1
1. Chore core and assignment modes - CRUD 2. Recurrence plus fairness 3. Full home operations 4. Self-hosted web hub, via dashboard (overdue/today/myqueue/fairness) 5. Docker compose no trackers	1
Chore tracking — create chores with title, required due date, assignee, priority, notes, and custom tags. Email reminder drafts — generate one combined pre-filled email for chores that are overdue, due today, or due soon. Recurring chores — support daily, weekly, and monthly chores, with options to complete, skip, or edit occurrences. List and calendar views — view chores in a task list and calendar, plus a separate completed-chores view.	1
One user managing their own private boards. Contains images, goals, habits, progress metrics and reflections. Free-form visual like movable cards on a canvas. Status, percentage, milestones and deadlines.	1
Households joined via a shared code (no passwords) — housemates identify by picking their name Up to 10 predefined common chores seeded automatically per household, plus custom one-off chores anyone can add Manual assignment — any housemate can assign (or reassign) any chore to anyone in the household Self-report completion with a simple history log (who completed what, and when) — no points, photo proof, or push notifications	1
1. Create/Join Household → Generate or enter household code 2. Add Members → Each member creates a profile 3. Create Chores → Define task, assign to member, set frequency 4. Complete Chores → Mark done, add notes/photos, verify	1
Based on the specification, the project settled on these 4 core MVP features: Global Shear-Flow Analysis The tool automatically solves the global shear-flow distribution of the stiffened panel using the panel geometry, supports, and external loads. It displays shear-flow values, directions, and equilibrium calculations. Normal-Load Diagram Generation After solving, the user can select any structural boundary (stiffener) and the tool generates the corresponding normal-load diagram N(x)N(x), including key values and detailed equations. Bay-by-Bay Buckling Verification Each bay is checked against buckling criteria using user-selected KK vs. a/ba/b curves, calculating critical stress, utilization, and safety margins. Engineering Report Export The tool generates a complete PDF report containing geometry, loads, supports, shear-flow results, normal-load diagrams, buckling calculations, and conclusions. The four primary features are global shear-flow analysis, normal-load diagram generation, bay-level buckling verification, and PDF engineering report export.	1
This app is a shared ledger for a household that pools money into a single joint bank account. 1. Each member can create entries of spending in different categories, and their monthly contributions. 2. The ledger is logged using sqlite3	1
Chore list & assignment Create, edit, and delete chores (e.g., “Take out trash”, “Clean bathroom”). Assign each chore to a specific housemate or leave it unassigned. Rotation / schedule Define a simple recurring schedule (e.g., weekly) for each chore. Automatically rotate the assigned person each cycle, or allow manual rotation. Completion tracking Mark chores as done for a given week/date. View a simple history of completed chores per person. Basic housemate management Add/remove housemates. See a summary of who has what chores and completion stats for the current period.	1
1. Automatic, time-based chore rotation — each chore has its own independent rotation interval (in days) and round-robin order among members; the assignment moves to the next person automatically once the interval elapses, regardless of whether the chore was completed. 2.Completion tracking for history only — members can mark their assigned chore as done, but this only logs history/tracking and does not affect or reset the rotation. 3. Admin-controlled household management — the first person to sign up becomes admin automatically; admins can create chores, remove members, and promote other members to admin.	1
Admin can create, edit, and delete chores Admin sets chore type (fixed or rotating), schedule, and assigns members Members can view their upcoming and overdue chores Members can mark a chore as done with one click Members can view their chore history Points awarded per chore completion (configurable per chore) All-time cumulative leaderboard visible to all members Monthly reset leaderboard view Late penalty: full points if on time, reduced if up to 1hr late, 0 points if more than 1 day late In-app notifications when a chore is due or overdue In-app notifications when a rotating chore assignment changes Notification bell/inbox in the UI	1
The MVP should make it possible for a household to: - Set up a shared household without accounts. - Add 2–6 roommates. - Use predefined recurring chores. - Automatically distribute chores fairly using round-robin rotation. - Clearly see what each roommate needs to do. - Complete chores with minimal interaction. - Handle missed chores without manual re-planning.	1
Portfolio Lens — a Django app that turns Interactive Brokers Activity Statement PDFs into trustworthy portfolio metrics. Four core features (dependency chain): 1. Ingest and reconcile — Parse PDF into models; prove correctness by matching statement totals (NAV, TWR, P&L) to the cent. 2. Daily NAV curve and period returns — Replay trade log against yfinance closes to reconstruct daily equity curve; derive weekly/monthly/YTD returns time-weighted and money-weighted. 3. Benchmark and risk metrics — SPY comparison (cumulative + per-period alpha), volatility, Sharpe, max drawdown, beta, normal-deviation bands so a bad week is interpretable as noise. 4. Sector map and metrics export — Weights by sector/industry, best/worst contributors, and JSON/CSV exports so Claude Code can analyze the numbers without LLM arithmetic.	1
1. Project foundation - Choose the web framework and persistence approach. - Configure local development, environment variables, and basic application layout. 2. Authentication and households - Implement registration and login. - Create one household per account. - Add administrator and member roles. - Support joining a household with a generated code. 3. Chore planning - Add creation, editing, and deletion of one-off chores. - Add recurring chores with daily, weekly, and monthly schedules. - Display chores in a date-grouped list. 4. Assignment rotation - Rotate recurring chore assignments across household members. - Allow the administrator to override an individual assignment. 5. Completion and reminders - Let members mark assigned chores complete. - Add in-app reminders for upcoming and due chores. 6. Release readiness - Add validation and permission checks. - Test the core household, planning, rotation, and completion workflows. - Document local setup and deployment instructions.	1
Track cats · track chores with a frequency and an optional cat · mark a chore done (logs when, flags overdue) · edit or delete a chore	1
1. Gamification with points and rewards (to make chores fun). 2. A shared leaderboard where the top earner gets a prize at the end of the month. 3. Verify if the task is completed through peer review (another roommate must click 'approve' before points are awarded).	1
I am planning to build a browser-based focus app: ambient sound mixer + calming animated scene + Pomodoro timer + task checklist. mostly tending towards study sessions. The main features are - 1.Animated Calming Scene 2.Ambient Sound Mixer 3.Pomodoro Timer 4.Task Checklist	1
Fair chore rotation based on completed effort points (small/medium/large). Recurring chores, overdue tracking, and accepted roommate swaps. Per-chore WhatsApp and web-push reminders; WhatsApp replies can mark assigned chores done. AI prompt box for fair-assignment explanations and confirmed chore creation or swap actions.	1
1. Household + simple identity. Members pick their name from the household's roster to identify themselves — no password, no login. 2. Recurring chores with an expected cadence. A chore is created once (name + cadence, e.g. "vacuum — weekly") and repeats indefinitely. No one-off chores. 3. Completion-driven rotation. A chore stays "with" one member — regardless of elapsed time — until they mark it done, then it advances to the next member in order. 4. Overdue tracking, visual only. The chore list flags whether a chore is currently overdue based on its cadence. No notifications, no reminders.	1
1.- Shared Chore Board: Chores organized into three clear views/tabs: Partner A, Partner B, and Shared Pool (unassigned chores like "clean dog poop"). 2.- Chore Creation: Quick form to add a chore title and assign it directly to a partner or leave it in the shared pool. 3.- Chore Completion: Check off assigned chores or claim & complete unassigned tasks with one click. 4.- Activity Feed with "Thank You" Reactions: A feed of recently completed chores showing who completed what, with a one-click "Send a Thank You!" button. ──────	1
# Household Chores Manager — MVP Scope ## Users - One household, 2–3 roommates. - Per-user login (email + password). ## Onboarding - First user creates the household. - Other roommates join with an invite code. ## Chores - Created from a template catalog and free-form custom entries. - Each chore is either one-off or recurring (daily / weekly / custom cadence). - Assignment: auto-rotation through roommates, with manual override. ## Doing chores - Self-mark done (trust-based, no verification). - In-app views: due today / overdue / upcoming. - History log of who completed what and when. ## Deliverable - Web app: backend API + browser UI. ## Explicitly out of scope (MVP) - Multiple households / multi-tenant. - Fairness tracking, points, difficulty weights. - Push / email notifications. - Completion verification by others. - Native mobile app. ## Open questions for later - Tech stack (frontend / backend / database). - Deployment.	1
Whose week — one roommate owns every chore that week; the page shows this week and the next few. Chore list — a fixed reminder of what “everything” means (not checkboxes). Instant swap — pick two weeks and they trade, immediately. No login — one shared URL; names, start date, and the list are hardcoded.	1
# MVP Features ## 1. Chore Library & Chore Creation ### Description The system provides a prebuilt list of common household chores. Users can also create custom chores. ### Chore Attributes - Title - Description - Frequency - Daily - Weekly - Monthly - Estimated Time (minutes) - Checklist Items ### Example ```text Title: Wash Dishes Frequency: Daily Estimated Time: 20 minutes Checklist - Rinse dishes - Load dishwasher - Clean sink ``` ### Acceptance Criteria - User can browse existing chores - User can create custom chores - User can edit chore details - User can delete custom chores --- ## 2. Automatic Task Generation ### Description Recurring chores automatically generate task instances based on their configured frequency. A new task is generated for every due date. Previous unfinished tasks remain in history. ### Example ```text Daily Chore: Wash Dishes Generated Tasks: Sep 08 Wash Dishes Sep 09 Wash Dishes ``` ### Acceptance Criteria - Daily chores generate daily tasks - Weekly chores generate weekly tasks - Monthly chores generate monthly tasks - Overdue tasks are preserved - New tasks are created regardless of previous task status --- ## 3. Task Claiming & Assignment ### Description Generated tasks start as unassigned. Any household member may claim a task. The system may suggest a recommended assignee. ### Acceptance Criteria - Tasks start unassigned - User can claim a task - User can release a task - User can reassign a task - Suggested assignee is displayed --- ## 4. Checklist-Based Progress Tracking ### Description Progress is tracked through checklist completion. Users may add notes describing completed work and remaining work. ### Task Statuses - Not Started - In Progress - Completed - Skipped ### Acceptance Criteria - User can check/uncheck checklist items - Status updates automatically - User can add notes - User can mark task completed - User can mark task skipped --- ## 5. Dashboard ### Description The home screen provides visibility into personal work and household work. ### Sections #### My Tasks Tasks currently assigned to the logged-in user. #### Household Tasks All tasks for the household. ### Metrics - Tasks Completed - Effort Completed (minutes) - Skipped Tasks - Unclaimed Tasks ### Acceptance Criteria - User sees assigned tasks - User sees all household tasks - Dashboard displays completion metrics - Dashboard displays effort metrics - Dashboard displays unclaimed tasks ---	1
(Features settled on): 1. Household Member Profiles: Simple member profiles (names/nicknames) without login friction. 2. Chore Creation & Due Dates: Add chores with title, description, due date, and priority (Low, Medium, High). 3. Flexible Assignment & Claiming: Assign chores directly to a member or post them to an open unassigned pool for anyone to claim. 4. One-Click Completion & Status Dashboard: Toggle chores complete/reopen with one click, plus status filters (All, Pending, Completed).	1
Spec: _docs/plan.md. It settled on four features: Answer: Fixed per-chore rotation and cadence (§2) — each chore has its own roommate order and frequency; turns are generated eight weeks ahead. Name + PIN sign-in with admin roles (§5, §7) — no email or signup; only admins edit chores and roommates. Completion tracking and history (§4) — every turn is a stored row with a status and who actually did it, so disputes are settled from the record. Away handling and swaps (§8) — a turn during a declared absence is skipped, not missed, and passes to the next person.	1
Here are the features: - Interface: Lightweight web application with an interactive dashboard displaying active chores, member rotation schedules, and completion statuses. - Core Logic: AI-assisted smart assignment engine that dynamically allocates chores while respecting member availability, preferences, and fairness. - AI Input: Free-text natural language notes/prompts (e.g., "Alice is traveling Thursday to Saturday, Bob prefers cooking over cleaning bathrooms"). - AI Engine: Pluggable LLM client (OpenAI / Gemini / Groq) with structured JSON output, paired with a deterministic local mock fallback for offline testing and CI pipelines without requiring API keys.	1
Register household members; create chores with an assignee and due date; view chores and mark them as completed.	1
## 1. Product Purpose A smart household chore management tool for any household type. The system helps households: - Assign chores intelligently - Distribute workload fairly - Track completion - Coordinate chores with minimal conflict The household size and members are configurable. --- ## 2. Core Product Pillars 1. Assignment — determine who should do each chore. 2. Fairness — distribute workload fairly. 3. Tracking — monitor completed and overdue chores. 4. Coordination — help household members coordinate without unnecessary conflict or nagging. --- ## 3. Smart Chore Assignment The system should recommend assignments automatically rather than relying only on manual assignment. The recommendation engine considers: - Workload — how much each member has already done. - Preferences — chores members like or dislike. - Availability — when members are available. - Skill / ability — whether a member is suitable for a particular chore. The household can therefore receive intelligent assignment recommendations rather than a simple static rotation. --- ## 4. Fairness Model Fairness is defined using a hybrid model: - Weighted effort — chores have different effort/weight values. For example, vacuuming can count as more effort than taking out the trash. - Personal circumstances — assignments can account for individual availability/capacity. The goal is not necessarily to give everyone the same number of chores, but to achieve a fair distribution of overall effort.	1
Users & Groups (Multiple Households): users can create households and invite roommates. Chore Creation & Assignment (Manual): users can create chores with due dates and assign them to household members. Deadline-Driven Visibility: chores are organized into Overdue, Due Today, and Upcoming. Completion / Simple Archive: completed chores move into a household-visible Completed/History log.	1
1. Chore Assignment - Rotating schedule: chores auto-rotate among members (no manual/claim/bidding). - Fairness weighting: rotation accounts for both: - Effort weight — harder chores count more - Time weight — longer chores count more - Combined to balance workload and prevent repetitive [...]	1
Three features I settled on: Chore assignment + tracking: Admins assign one-time or recurring chores to specific members, with Today / Upcoming / Overdue / Pending Approval views. Completion workflow: Members can mark chores done, add optional notes/photos, and some chores can require admin approval or rejection with a reason. In-app notifications + audit history: Due-date reminders, completion/edit notifications, and a detailed history of edits, completion	1
Spec-driven development Context engineering The product manager, software engineer, and QA roles Loop engineering Graph engineering	1
Gestion des tâches récurrentes Suivi et validation des tâches	1
(1) Dataset catalog · (2) Refresh logging · (3) Freshness status fresh/stale/failing/never · (4) Freshness dashboard + history	1
1. Explain simple changes in the bill using the information actually present on the electricity bill . 2. Summarise monthly electricity consumption and bill amount . 3. Monthly comparison of powerconsumption and bill amount 4. Consumption and bill charts over a period of time .	1
1. Add and tick off chores (personal to-do list, single user, no accounts) 2. Recurring chores — daily or weekly on chosen weekdays; completing auto-schedules the next occurrence 3. Snooze/postpone — "tomorrow" / "next week" pushes the due date without marking done 4. Urgency grouping — list sorted into Overdue / Due today / Upcoming	1
Members management; Chores CRUD (name, assignee, due date, done); Chore list sorted by due date with overdue highlight and member filter; Stats per member	1
1. Member list & roles — an admin-maintained roster of club members with a name and role each. Members don't self-register. 2. Current book & progress tracker — the club's current title and author, with each member's progress recorded as an actual quantity (pages read, from which a percentage is derived) rather than a status label, so the group can see who's ahead and who's behind. 3. Discussion: notes + Q&A — two modes. Free-text notes any member can post spontaneously about the current book, plus structured Q&A where the admin posts discussion questions and each member responds to them. 4. Reading history — a full, uncapped archive of every book the club has finished, each with title, author, and the dates read, optionally retaining the rating and the discussion from that book.	1
Create Project Data Model Build Project Setup with deadlines Implement AI Material Analysis Weekly roadmap generation	1
Household members can join using an invite code; members can claim and complete one-time or recurring chores; overdue chores become available again; and the household can view completion history.	1
Fair assignment and tracking is core features. Fair assignment is defined as equal turns. Over time every member should have completed roughly the same number of chores. (There is a skipping option for members to skip a chore but that is limited to max 7 chores). Chores are completed by self-reporting (no proof needed). Completed chores and debt cap is tracked. Assignmet ranking is affected by completed turns. (skipped chores does not count as completed)	1
Student management Assignment management Assignment status tracking Classroom dashboard	1
### Users - 4 people - Simple accounts: email/password login (each person's data and history tracked separately) ### Assignment Model - Mixed approach: - Some chores rotate automatically through people on a schedule - Other chores go into an open pool that people can claim ### Recurrence - Set per chore, either: - Fixed schedule (e.g. "trash every Tuesday") - Interval-based (e.g. "every 3 days since last completed") ### Claiming (Open-Pool Chores) - Rotating merit queue: open chores are auto-queued to whoever currently has the fewest effort points - People can still claim manually if they want, overriding the suggestion ### Completion Tracking - Checkbox to mark done - Timestamped history log: records who did what and when	1
1. Household and Member Management A household consists of multiple members and one leader. The leader can add, rename, and remove members. 2. Create, Assign, and Claim Chores Any member can create a chore. A chore can be assigned to oneself or to another member, or left unassigned so that other members can claim it. 3. Due Dates, History, and Chore Reuse Due dates are optional. Once a chore is completed, it moves into History. Chores in History can be reused, their key details are copied over so they can be edited and recreated as a new Open chore. 4. Shared Board and Household Progress Tracking All members share a single board, which can be filtered by member. The top of the board displays this week's completion rate and the number of overdue chores.	1
- Either partner creates one-off or recurring chores. - Every chore has a required due date. - Recurring chores follow a fixed schedule. - Either partner claims an available chore, reserving it.	1
1. Roommate CRUD (2-5 peers) 2. Chore catalog CRUD (name + time_estimate_min + recurrence) 3. Balancing engine — auto-assign to lowest sum(time assigned - verified) 4. Mark done → roommate verifies flow	1
Household members with accounts (basic login) Recurring chores (daily/weekly, reset after completion) Rotating auto-assignment (chore passes to next person) Chore dashboard (view + mark done)	1
- Chore scheduling/rotation - Task assignment & tracking - Notifications/reminders	1
Project Scope: Shared Household Chores Tool Domain: General household management (roommates, couples, families). Core Assignment Model: Hybrid (recurring rotations + an unassigned chore pool/bounty board). Accountability: Fairness meter (visual indicator of relative contributions/recency). Identity & Access: Simple profile switcher (select household member from a list, no password barrier). Architecture & Stack: Full-stack Django (Django templates + SQLite for quick setup and seamless persistence).	1
1. Weekly feedback submission — team members can submit structured feedback about progress, what worked, problems/blockers, improvements, and suggestions, with an option to submit anonymously. 2. Weekly feedback cycle — feedback can be edited during the week and automatically closes every Friday at 10:00. 3. Retrospective view — the team reviews the collected feedback in a board/meeting view during the weekly retrospective. 4. Action items and decisions — the team can record decisions and action items resulting from the retrospective.	1
1. Add a claim with patient name, payer name, amount, and service date. 2. List all claims, newest first. 3. Change a claim's status between pending, paid, and denied.	1
Recurring chores — three kinds: Daily — e.g. physical exercise, due every day. Flexible weekly target — e.g. "self-learning 2× this week", done on any days. 1. Recurring chores — three kinds: - Daily — e.g. physical exercise, due every day. - Flexible weekly target — e.g. "self-learning 2× this week", done on any days. - One-off — a single task with a due date, no repetition. 2. Two household members — chores are assigned to one of two people, and completions record who did them. 3. In-app reminders — a "Today" view listing what's due, with overdue items highlighted. No email, no push, no desktop notifications. 4. History & streaks — current streak and total completion count per chore.	1
1. Create household chores and set due dates. 2. Assign chores through a shared roommate rotation, with admin override. 3. Mark chores as completed.	1
Application about recipe calculation price 1. ingredients must be register with weight and price 2. recipe could be created with weight per ingredient 3. recipe calculations needs grams expected per unit	1
# Chore Types - One-time manual tasks (e.g., "buy milk") - Recurring tasks with customizable frequency (e.g., "vacuum weekly") # User Assignment - Assign each chore to a specific user - Recurring tasks: Manual assignment per period (different user can be assigned each week) # Completion Tracking Three status states: 1. Not Started 2. In Progress 3. Completed	1
Family Chore Tracker 1. Let kids mark a chore done for a specific calendar date. 2. Show the main weekly calendar with days as columns and kids as rows. 3. Let parents maintain kids and chores after initial setup. 4. Store chores assigned to one kid on selected days of the week.	1

3. Which file do you edit to include your app in the Django project?

314 / 337 correct (93.2%)

1 settings.py 314 (93.2%)

2 manage.py 20 (5.9%)

3 urls.py 3 (0.9%)

4 wsgi.py 0 (0.0%)

4. What is task 1 in your backlog.md?

337 / 337 correct (100.0%)

Answer	Count
Set up an empty Django project with a passing test	2
Scaffold the Django project with a passing test	1
Task 1: Settle the week-boundary and timezone decision	1
1. Scaffold an empty project with a passing test Goal: Leave a runnable Python project whose test suite passes with one real test. Description: Create the app package, dependency files, and pytest setup in this repository. Add a single trivial test that asserts a known-true condition so `pytest` exits successfully. Do not implement resume parsing, scoring, or any product feature.	1
- [x] Task 1 — Define models (`chores/models.py`) - `Person` — `name` (CharField). - `Chore` — `title` (CharField); `assigned_to` (FK → `Person`, `on_delete=PROTECT`, `related_name="chores"`); `interval_days` (PositiveIntegerField, `null=True`, `blank=True` — null = one-shot); `last_done_at` (DateTimeField, `null=True`, `blank=True`). - `__str__` on both.	1
1. Roommate model — Represent a roommate. Fields: name (required), is_admin (bool, default False), created_at. Decide and document the link to Django's User. Acceptance: model + migration created; __str__ returns the name; visible in Django admin.	1
Set up an empty project with a passing test https://github.com/hooman-the1/K6-Based-Psychological-Distress-Check/issues/1#issue-5363204926	1
The first task is Models: reference data — create a MileageRate model (period start/end date, cents-per-mile), seeded via migration with the 2025/2026 rate table from plan §6, and editable in Django admin so it doesn't go stale in 2027.	1
Data model – add Member and Chore models, migrations, register in admin	1
1. Set up the project with a passing test Goal: A runnable Django project managed with uv, with one test that passes. Description: Initialise the project with uv, add Django, and create the project skeleton with a single app. Add one trivial automated test (for example, a health-check view returning 200) and confirm the test suite runs green. This establishes the toolchain, test runner, and project layout everything else builds on.	1
Epic 1 — Project & User Setup [x] BE-01 Define custom user model with roles: manager, supervisor, worker [x] BE-02 Configure role-based permissions and Django groups [x] BE-03 Implement login / logout with session auth [x] BE-04 Restrict views by role using decorators or mixins	1
## Phase 0 — Foundations - T1 — Project config & base layout · deps: none Confirm `config` settings (timezone, sqlite, templates/static dirs). Add a responsive base template (nav + content block) and minimal CSS. No dark mode.	1
Implement a basic household chores list where household members can view and add chores.	1
## 1. Set up the base app - Add a home page for the `chores` app. - Link the app URLs from the main project URLs. - Add a base page template with navigation.	1
Set up Django project and app	1
"Set up the Django project skeleton" — create the `config` project and `chores` app, register `chores` in `INSTALLED_APPS`, wire `config/urls.py` to the app's URLs, add the SPA shell template, and verify `migrate` + `runserver` work.	1
Empty project with a passing test	1
Backlog is separated by milestones, and then, milestones are separated by tasks. Milestone 1 consist in setup, authentication and onboarding, and includes three tasks. The first task consist in the base configurations and the template setup. It's acceptance criteria is that the base template renders cleanly with responsive styling and a navigation placeholder.	1
Add ConnectorFamily and ConnectorType models ( catalog/models.py )	1
Task 1: Initialise Django project & create app	1
[x] TASK-01: Design & Implement Database Models - `Roommate`: `name` (CharField), `is_active` (BooleanField), `created_at` (DateTimeField), `order_index` (IntegerField). - `Chore`: `title` (CharField), `description` (TextField, optional), `is_active` (BooleanField), `is_one_off` (BooleanField). - `Cycle`: `start_date` (DateField), `end_date` (DateField), `is_current` (BooleanField). - `ChoreAssignment`: - Relations: `chore` (ForeignKey), `cycle` (ForeignKey), `assignee` (ForeignKey to `Roommate`). - Status: Choices (`NOT_STARTED`, `PENDING_CONFIRMATION`, `CONFIRMED`). - Audit fields: `completed_at` (DateTimeField, nullable), `confirmed_by` (ForeignKey to `Roommate`, nullable), `confirmed_at` (DateTimeField, nullable).	1
## Phase 1: Project Setup & Foundation ### 1.1 Django Project Initialization - [ ] Create Django project structure - [ ] Set up virtual environment and dependencies - [ ] Configure settings (dev/prod split) - [ ] Set up database (PostgreSQL recommended) - [ ] Configure static files and media handling - [ ] Set up .gitignore and environment variables ### 1.2 Authentication System - [ ] Implement user registration - [ ] Implement user login/logout - [ ] Create user profile model - [ ] Add password reset functionality - [ ] Set up session management	1
Task 1 is: Set up the Chore model.	1
Task 1: Models — Define Person and Chore in chores/models.py (fixed lists, ordered), then run makemigrations/migrate.	1
Set up project with a passing test	1
Create HouseholdMember model (name field, fixed set)	1
set up the Django project and register the app	1
Initialize the Django application	1
Project & app scaffolding — set up the Django project and the chores app.	1
Create the Django project and learning app, then implement the Course model with migrations.	1
Create the business request data model.	1
## Sprint 1: Foundation & Auth - [ ] Set up Django project structure (done) - [ ] Configure PostgreSQL database - [ ] Create custom User model (email as username) - [ ] Implement JWT authentication (djangorestframework-simplejwt) - [ ] Build auth endpoints: register, login, logout, refresh token - [ ] Add password reset flow	1
Project Setup with Tests	1
Create the Task model	1
## 1. Set up an empty project with a passing test Goal: Establish a minimal Django project and app that runs successfully. Description: Create the project structure, install the required dependencies, and configure the application. Add one basic test proving the empty project loads and passes.	1
Task 1: Project scaffold — create the Django project and chores app, register it in INSTALLED_APPS, confirm manage.py check passes.	1
Django Data Model	1
Project setup - add chores_app to INSTALLED_APPS, configure PostgreSQL, set up requirements.txt	1
Configure the chores app	1
Auth and household	1
Project skeleton — install Django, start the project/app, register it in settings.py	1
Django project scaffolded with uv Create core apps (households, chores, assignments)	1
Bootstrap an empty Django project with a passing test	1
## 1. Project Initialization and Environment Setup	1
Task ID: TASK-01, Title: User Profile & Language Preferences Model, Component: Models / Auth, Dependencies: None, Status: To Do	1
Setting up an empty project with a passing test	1
Set Up Empty Django Project With Passing Test	1
Scaffold the Django project and `chores` app with uv	1
Ask it to create a small backlog in backlog.md based on plan.md, then implement Task 1 from that	1
create the core data model	1
Task 1: Project & App Setup: Initialize Django project with `uv`, create the `chores` app, and register it in `config/settings.py` (`INSTALLED_APPS`).	1
Bootstrap an empty Django project	1
Answer: ## 1. Data model Create `Person` and `Chore` models in the `chores` app. - `Person`: name (unique within household). - `Chore`: name, `assigned_to` (FK to Person), `last_done_at`, `done` flag or status. - Rotation order needs a concrete field even before the algorithm is decided — e.g. a `Person.order` int or an ordered `rotation` list on `Chore` — so later tasks aren't blocked. Depends on open question: rotation order/algorithm among multiple people. Default to simple fixed list order (by `Person.order`) unless told otherwise. - Leave chore metadata (frequency, difficulty/weight) out of v1 unless the open question gets resolved first — add fields only when there's a confirmed need.	1
Milestone 1 — Data model; task 1.1: `Member` model: name.	1
Data Model — Create the Chore model (name, description, priority, waiting_period_days, last_completed_at), run migrations, register in Django admin.	1
Define the data models (Household, Membership with role, Chore, Completion, Grade) and run migrations.	1
1. Models — Add `HouseholdMember`, `Chore`, `ChoreAssignment` (ordered join table for rotation), `ChoreCompletion` to `chores/models.py`. Run `makemigrations` + `migrate`.	1
Task 1.1: Project Setup	1
Task 1 — Create Django project and `chores` app	1
## 1. Household and Adult models	1
## 1. Initialize Django project Goal: Create the base Django project structure. Description: Run `django-admin startproject choreflow .` in the project root. This creates `manage.py` and the `choreflow` settings package.	1
Создать модели данных и миграции	1
Task 1: Store chores — add a Chore model with title/description, responsible person, deadline, and completion status, then create the initial migration.	1
## Goal A `Chore` model defined in `chores/models.py` with all MVP fields and a migrated database, so that chores can be created, stored, and queried via the Django ORM — the foundation every other task builds on. ## Acceptance criteria - [ ] `chores/models.py` defines a `Chore` model with the following fields: - `title`: required `CharField` (max length 200) - `due_date`: required `DateField` - `assignee`: optional `CharField` (max length 100, `blank=True`, default empty string) - `notes`: optional `TextField` (`blank=True`, default empty string) - `priority`: optional `CharField` with choices `Low`, `Medium`, `High` (`blank=True`, default empty string) - `tags`: `ManyToManyField` to a `Tag` model (optional, `blank=True`) - `completed`: `BooleanField` default `False` - [ ] A `Tag` model exists with a single `name` field (`CharField`, `unique=True`) and a `__str__` returning the tag name. - [ ] An initial migration file exists under `chores/migrations/` that creates the `Chore` table, the `Tag` table, and the M2M join table. - [ ] Running `python manage.py migrate` applies the migration cleanly with no errors and no pending migrations remain. - [ ] A chore can be created via the Django ORM (e.g. `Chore.objects.create(title="Wash dishes", due_date="2025-01-15")`) and is persisted to the database. - [ ] Omitting `title` or `due_date` when saving a chore raises an `IntegrityError` (or validation error); omitting `assignee`, `notes`, `priority`, or `tags` is allowed. - [ ] `Chore.__str__` returns the chore's title; `Tag.__str__` returns the tag's name. - [ ] Tags can be created and assigned to a chore via the M2M relationship (e.g. `chores.tags.add(tag)`) and queried in both directions. ## Out of scope - Recurrence frequency field (daily/weekly/monthly) → moved to #7 (Recurring chores) - Admin site registration for `Chore` or `Tag` → no follow-up (not required by any MVP task) - Seed data or fixture loading → no follow-up (not required by any MVP task) ## Constraints - Stay inside the `chores/` app (`chores/models.py`, `chores/migrations/`). - Use Django's built-in ORM — no new dependencies (see `_docs/AGENTS.md`: dependencies require approval). - `Tag` names must be unique to avoid duplicates. - Follow Django naming conventions for models, fields, and migration files. - Refer to `_docs/plan.md` §10 (Chore Fields), §12 (Priorities), §13 (Tags) for field behavior and defaults.	1
Project skeleton	1
Task 1: "Models in core/models.py" → defining Chore and LogEntry as specified.	1
Task 1: Create Household model with fields: id - Primary key name - Household name code - Unique join code created_at - Timestamp	1
Set up the project with a passing test Goal: A Django project that runs and has one test that passes. Description: Create the Django project and the `chores` app, register the app in `INSTALLED_APPS`, and confirm `manage.py runserver` serves the welcome page. Add a single trivial test in `chores/tests.py` and confirm `manage.py test` reports one passing test. This task is complete when a fresh clone plus `pip install -r requirements.txt` and `migrate` gets someone to a green test run.	1
## Sprint 1: Core Data Models & Admin Configuration * US-101: Set up UserProfile Model * Description: Implement the `UserProfile` model with UUID, name, role (`Parent`, `Child`), `pin_hash`, `total_points`, and `level`. * Tasks: Write model code, create and apply migrations, register model in Django Admin. * US-102: Set up Chore and Assignment Models * Description: Implement the `Chore` and `Assignment` models with appropriate foreign keys, weekly start dates, statuses (`Pending`, `Submitted`, `Approved`, `Rejected`), and photo URL fields. * Tasks: Define models in `models.py`, generate migrations, verify relational constraints in database.	1
Create Person, Company, Tag, Interaction, Membership models with M2M relationships	1
Set up empty project with passing test	1
## 1. Bootstrap the project with Docker Compose and a passing test	1
## Project setup - [ ] Scaffold Django project (`django-admin startproject`) - [ ] Create `chores` app and register it in `INSTALLED_APPS` - [ ] Set up base template / static files structure	1
Task 1: Project Setup & Database Models Configuration Status: To Do Priority: High Description: Initialize the project environment, create the main app module, configure database settings, and define core models (User, Chore, ChoreSubmission, and PointLedger). Acceptance Criteria: Application structure initialized and running. Database schema defined with proper relationships and constraints. Initial database migrations created and applied successfully.	1
Create a household chore with a due date and list active chores.	1
T1 — Domain models: Flatmate, Chore, rotation. Create the Flatmate and Chore models with an ordered rotation linking them, in one initial migration.	1
Define the Chore and LogEntry models.	1
Configure PostgreSQL with Docker Compose and connect Django using environment variables.	1
1. Set up an empty project with a passing test Goal: Verify and stabilise the existing empty Chorum-murohc project baseline. Description: Treat the current Django 5.2 project, registered chorum_murohc app, uv lockfile, and app-registration test as the required empty scaffold; do not recreate them. First prove the incoming baseline with uv run --locked python manage.py test chorum_murohc; after obtaining and recording DA-01 approval for exact compatible pytest and pytest-django ranges, establish and document uv run --locked pytest as the outgoing canonical command and finish with a clean passing test and no product models or features.	1
### 1. Define the models Add `Person`, `Chore`, `History` to `chores/models.py` per the plan. - `Chore.effort` — small integer, validated 1–5. - `Chore.status` — `TextChoices` (`pending` / `assigned` / `done`), default `pending`. - `Chore.assigned_to` — nullable FK to `Person` (the plan's `assigned` status implies one; `History` alone can't answer "who has this now"). - `History` — FK to `Person` and `Chore`, denormalized `effort` snapshot, `completed_at` auto-set. - `Person.name` unique, so "remove-person by name" stays unambiguous. Done when: `makemigrations` + `migrate` run clean, and models are registered in `chores/admin.py` so data can be poked at via `/admin`.	1
Initialize the repository with a working Django 5 project, uv/pyproject.toml dependency configuration, and a passing pytest smoke test harness.	1
Project Initialization and Test Setup	1
Backlog Small, sequential tasks for implementing _docs/plan.md in Django. Task 1: Set up Django project skeleton with a passing test Create the Django project and chores app, confirm the dev server runs, and add a trivial passing test to prove the test runner works before building real features. Task 2: Build core data models Create Profile (admin flag), Chore (name, rotation interval), ChoreRotationMembership (round-robin order per chore per user), and ChoreCompletion (history log). Register all models in Django admin. Task 3: Implement rotation logic Add a current_assignee() method to Chore that computes who is currently assigned based on time elapsed since creation and the chore's own rotation interval, independent of other chores and regardless of completions. Task 4: Cover core logic with tests Add tests for: a chore with no members returns no assignee; a freshly created chore assigns the first member in rotation order; the assignee is never None when members exist. Task 5 (next up): Auth and admin-only actions Add signup/login views. Make the first user to sign up an admin automatically. Restrict chore creation and member removal to admins. Task 6 (next up): Mark-done flow Add a view/action for a member to mark their currently assigned chore as done, creating a ChoreCompletion entry without affecting rotation.	1
Set up an empty project with a passing test	1
Initialize Django project and core app structure	1
## 1. Set up an empty Django project with a passing test Goal: Establish the smallest runnable Django project and prove the test runner works. Description: Create the Django project and initial application structure without implementing product behavior. Add one basic test that passes and document the command used to run the test suite.	1
1. Project foundation - [ ] Create a Django project and a `chores` app; configure SQLite for local development, static/media files, environment-based settings, and a base layout. - [ ] Add authentication using Django's user model and a household profile/role layer. Seed Duella as manager and Jarvis, John, and Monty as members. - [ ] Enforce permissions: only Duella may administer chores, schedules, household rules, and approvals; members may only act on chores assigned to them or where they are helpers.	1
1. Project Scaffolding & First Passing Test Goal is to create an empty, runnable Django project with one passing test, proving the toolchain (Django + SQLite + pytest) works end to end. No models, auth, or business logic.	1
Create the Chore data model and database migration for storing chores, assignees, due dates, recurrence, and completion status.	1
## 1. Add family membership and sign-in	1
Create a pyproject.toml targeting Python 3.12+ with Django 5.x, pytest, pytest-django, and Ruff dependencies.	1
Create Member and Chore models	1
Project setup - An empty Django project with a successful test	1
Phase 0: Scaffold — from blueprint §7: django-admin startproject config ., startapp chores, add models + first migration, seed command with demo people/chores That's done, and so is Phase 1: Balancer core (balancer.py + tests + generate command). The first unstarted task is Phase 2: ICS generation	1
Scaffold Django project (`django-admin startproject`) and a `chores` app (`python manage.py startapp chores`)	1
Set up Django project structure	1
Project skeleton with a passing test • Goal: A running Django project with one green test, so every later task starts from a known-good baseline. • Description: Create the Django project ( config/ ) and the three apps ( accounts/ , households/ , chores/ ) per architecture.md, wire up pytest / pytest-django and ruff , add docker-compose.yml with web + db (Postgres) services, and add a single trivial test (e.g. a health-check view returning 200) confirming pytest passes both locally and via docker compose run web pytest .	1
## Status and Goal Planned; not implemented. Extend the [initial MVP](plan.md) so partners can find relevant chores, control recurring schedules, and update chore details. Keep the stack and development conventions in [AGENTS.md](../AGENTS.md). ## Priority Order 1. Filter the board. 2. Pause, resume, or permanently stop recurring chores. 3. Edit chores and add assignment during creation. ## Board Filters - Ownership options: All, Mine, and Available. - Mine means only chores currently reserved for the signed-in partner; completed chores are excluded. - Date options: All dates, Overdue, and Due this week. - Combine one ownership option with one date option. - Default to All and All dates, with a clear/reset action. - Preserve the Available, Claimed, and Done board structure, with counts reflecting the filtered results. Proposed details: weeks run Monday through Sunday in the household timezone. Due this week includes every due date in that calendar week; Overdue includes only unfinished chores due before today. Store filter selections in URL query parameters so refreshes and chore actions preserve the selected view.	1
Create the core data model	1
Housemate and Chore models with admin	1
Create the uv project, install Django 5.x, generate the household project and the chores app, and register chores in household/settings.py (INSTALLED_APPS). Configure TEMPLATES["DIRS"], the auth redirect URLs, and add .gitignore. Acceptance: uv run python manage.py check and uv run python manage.py migrate succeed.	1
"Members: data model + admin" — create a Member model and register it in Django admin.	1
## 1. Project scaffold with a passing test Goal: Get an empty, runnable Django project in place with a working test harness. Description: Create the Django project and a `chores` app with no models or views yet, wire up `manage.py test`, and add one trivial passing test (e.g. asserting the app loads) so the tool chain is proven before any real code is written.	1
Setup project structureand initialize configuration.	1
## 1. Data model - Define a `Chore` model: `name`, `assignee` (Donna / Russ / Both), `schedule_type` (fixed / flexible / ongoing), `frequency` (daily, weekly, monthly, every-2-months, quarterly, annual, 2-3x/week, ongoing), `days_of_week` (nullable, only for fixed-day chores), `is_done` (boolean), `period_start` (date, used to determine when to reset). - Write and run the initial migration.	1
Add the chore domain models	1
Add core data models for HouseholdMember and Chore.	1
Task 1: Set up Django models for SensorNode and TelemetryReading with migrations	1
Phase 0 — Foundation (1–3): custom user model + Household, registration/login, base layout + per-request timezone activation. Phase 1 — Domain (4–6): Chore CRUD, Assignment model + idempotent weekly rollover service, chores_tick command for rollover and overdue transfer.	1
1. Empty project with a passing test	1
Task 1: "Set up an empty Django project with a passing test" • Goal: Establish a runnable Django and Django REST Framework project baseline. • Description: Configure project structure, dependencies, settings, and test runner without any household/chore behavior yet — just prove the empty project loads with one minimal test. • Acceptance criteria: • The project starts with the documented development command. • Django system checks pass. • The test suite runs successfully with at least one passing test. • Dependencies and local environment setup are documented.	1
## 1. Data model - [ ] `Household` model + `Membership` (User ↔ Household, `role`: owner/member) (§2) - [ ] `Chore` model: name, description, points, due_date (date, not datetime), is_recurring, deleted flag/timestamp for archive (§3, §13) - [ ] `RecurrenceRule` model or field on `Chore`: calendar-based vs completion-based interval (§4, §18) - [ ] `Claim` model: chore ↔ member, claimed_at (§5) - [ ] `PointEvent` model: member, chore, delta, reason, kind (completion/adjustment/failure/manual), created_at, review deadline for completions (§6, §7, §8, §11) - [ ] `ActivityLog` model: actor, action type, target, timestamp, metadata (§13) - [ ] `Achievement`/`Badge` models + a member-achievement join table (§10) - [ ] Register everything in `admin.py` for quick inspection while building	1
Task 1: Models & validation Implements spec §1.2, §2.2–2.5, §"Data Model (Contract)". Files: - Modify: `chores/models.py` — `HouseholdMember`, `Chore`, `CompletionLog` - Create: `chores/migrations/0001_initial.py` (via `makemigrations`) - Modify: `chores/admin.py` — register all three models for quick inspection while UI doesn't exist yet What it does: Defines the three models and their fields exactly as in the spec's data model. `Chore.clean()` enforces: one-off chores can't have `interval_days` set; recurring chores need `interval_days >= 1`; manual assignment needs `assignee`; auto-rotate needs 2+ members in `rotation_pool`. Testing: Model tests for each validation rule in `clean()` (valid one-off, valid recurring, rejects recurring without interval, rejects auto-rotate with <2 pool members, rejects manual without assignee).	1
Task 1: Data Models & Core Schema Define Django models in `chores/models.py`: - `FamilyMember`: Name, role (Parent/Child), avatar, PIN (for parents), current XP, level, and balance/allowance total. - `Chore`: Title, description, chore type (`ROUTINE` vs `BOUNTY`), monetary reward amount, XP reward value, frequency (daily/weekly), and assigned kid (optional). - `ChoreSubmission`: Link to `Chore` and `FamilyMember`, photo proof image upload, status (`PENDING`, `APPROVED`, `REJECTED`), parent feedback note, and submitted/approved timestamps. - `Badge` & `StreakTracker`: Rules and records for streaks and milestone achievements.	1
## 4. Views & URLs - Pages: members, chores, weekly assignment (generate/regenerate), checklist to mark completions. - Wire up URLs and simple Django templates. - Done when: each page is reachable and the checklist POST updates `completed`.	1
Project Setup with Passing Test Goal: Have a runnable Django project with one passing test.	1
did not create backlog.md instead GitHub Issues were created directly as backlog Task 1 was “Bootstrap Django with a passing test.” It established the minimal runnable Django foundation: dependencies and lockfile, SQLite default/PostgreSQL configuration, an installed todos app, a placeholder home page/base template, vendored HTMX, CSS, and passing initial Django checks.	1
Initialize the Django project (e.g., `chore_manager`) and create a core app (e.g., `chores`). Configure settings for SQLite, static files, and templates.	1
Goal: A Django project that installs, runs, and has a green test suite. Description: Create a Django 6.0 project on Python 3.14 with pyproject.toml, pinned dependencies, and a config/ settings module reading DATABASE_URL, SECRET_KEY, DEBUG, and ALLOWED_HOSTS from the environment. Configure pytest-django and ruff, and add one test asserting the homepage returns 200. pytest must pass and ruff check must be clean before this task is done.	1
T1 · Base template + static setup — add templates/base.html, configure the TEMPLATES dirs and STATIC_URL in config/settings.py, and wire a placeholder home view + URL.	1
1. Empty project scaffold with a passing test Goal: Stand up the repo skeleton for both services with one green test in each. Description: Create the Next.js app (TypeScript, Tailwind configured) and the FastAPI app (Python, project layout with a `tests/` folder) as separate services in the monorepo. Each should run locally with a single command and have exactly one trivial passing test (e.g. a health-check route test) wired into whatever test runner is chosen, so CI has something real to execute from day one.	1
Set up the Django project with uv, create the evaluation app, register it in INSTALLED_APPS, build the Projet model, run migrations, and register it in the Django admin.	1
Passing smoke test for the empty project Test harness: pytest, Django DB, and uv scripts	1
Task 1: Set up the Django project and create the initial application.	1
1. Household models Household (daily bounty rate), resident (join date), chore catalog (name, cadence, fixed bounty start). Seed one household with N ≥ 3 residents in admin or a fixture.	1
1. Add user authentication and identity Priority: P0 Depends on: None Set up the signed-in user flow using Django’s authentication foundation. Make the current user available to household and chore views. Done when - Users can sign in, sign out, and access their identity. - Household and board routes require authentication. - User name and email are available for display and assignment decisions. Likely Django areas: assign_chores/settings.py, assign_chores/urls.py, chores/, templates, and migrations as needed.	1
Reassign instead of delete when removing a member - Removing a member currently cascade-deletes their chores.	1
Create the Chore model in chores/models.py with fields for title, description, category, priority, status (UNASSIGNED, CLAIMED, COMPLETED), assigned_to, created_by, created_at, and completed_at. Create and apply initial database migrations using python manage.py makemigrations and python manage.py migrate.	1
Finish project settings	1
Scaffold Django project structure (config/ package, core app, manage.py): https://github.com/aag-learn/ai-dev-tools-zoomcamp-homework-2026/issues/1	1
Task 1: Set up the Django project and app skeleton — create the project, create the pricewatch app, register it in INSTALLED_APPS, and confirm the development server runs.	1
project env and setup	1
## 1. Foundation - [ ] Custom user model — profiles are named, password-based, no email. Replace Django's default `User` with a custom model (or `AbstractUser` subclass with `email` dropped) before the first migration locks in. - [ ] Roles — add a `role` field (`admin`, `manager`, `member`) to the user model, or a `Household` + membership model if we ever expect multiple households. For v1, a flat role field is enough. - [ ] Auth flow — login/logout views using Django's built-in auth with username+password (no email). No self-registration needed yet if household members are added by an admin.	1
Scaffold Next.js project with a passing test and CI	1
Set up Django project, apps, and household membership Create the Django project and five apps: households, chores, assignments, leaderboard, notifications. Configure settings.py, root URLs, static files, and templates. Implement user signup/login with Django's auth system. Build Household and Membership models with roles (admin/member) and invite-code joining. Add views/templates to create, join, and view households.	1
Task 1, in tasks.md: ## 1. Project setup with a passing test Goal: An empty, runnable Django project with a green test suite. Description: Scaffold a new Django project and a `chores` app inside it, configure `TIME_ZONE = "Europe/Berlin"` and `USE_TZ = False` in settings, and add one trivial test (e.g. asserting the test runner works, or a smoke test on the admin/health path) that passes with `manage.py test`. Issue 1, after grooming: ## Goal An empty, runnable Django project with the `chores` app installed and a green test suite, so every later task builds on a known-working base. ## Acceptance criteria - [ ] `uv run manage.py test` exits 0 and reports at least 1 test executed - [ ] `uv run manage.py check` exits 0 with no errors - [ ] `uv run manage.py runserver` starts without error and serves a response on `/` or `/admin/` (200 or a redirect, not a 500) - [ ] `chores` app is listed in `INSTALLED_APPS` - [ ] `settings.py` sets `TIME_ZONE = "Europe/Berlin"` and `USE_TZ = False` - [ ] The database engine is SQLite (Django's default `django.db.backends.sqlite3`), per the stack choice in `_docs/plan.md` - [ ] `django` is added as a project dependency via `uv add django` (reflected in `pyproject.toml` / `uv.lock`), not installed ad hoc - [ ] `db.sqlite3`, `__pycache__/`, and `*.pyc` are excluded via `.gitignore` - [ ] The placeholder `main.py` / `Hello from shared-household-chores!` scaffold from the initial `uv init` is removed or replaced so it doesn't sit alongside the Django project unexplained - [ ] `manage.py` and the Django project package live at the repo root (not nested in an extra subdirectory) ## Out of scope - Any model (`RecurringChore`, `OneOffTask`) — see #2, #3 - Any view, template, or styling — see #5, #6, #7 - Configuring the dev server for LAN access — see #14 ## Constraints - Use `uv` for dependency management — `.python-version` (3.13) and `pyproject.toml` already exist in the repo; add Django via `uv add`, don't hand-edit dependencies - App name must be `chores` (matches every later task in `_docs/tasks.md`) - The Django project (settings) package name is an implementation detail the engineer may choose freely; note the chosen name in the PR/commit so later tasks can reference it if needed - No models, views, or URLs beyond what `startproject`/`startapp` generate plus the one smoke test — that's tasks #2 onward	1
Task 1 is “Set up an empty project with a passing test.” Its goal is to create a minimal React and TypeScript application with a passing automated test suite. It is complete and GitHub issue #1 is closed.	1
Admin can create a new project listing	1
Task 1: data models and admin — define the Task and TaskLog models, generate and apply the initial migration, and register both models in the Django admin so chores can be created and inspected.	1
Task 1 is Register the chores Django app. It requires: - Registering the existing chores app - Adding its stable project URL include - Confirming Django loads the app without errors - Ensuring manage.py check passes	1
Create the Chore Model	1
Task 1 is to scaffold the Django project and the portfolio app, and register the app in INSTALLED_APPS. It's done when runserver boots and manage.py check is clean.	1
1. Set up empty Django project with a passing test	1
Task 1: Create the Django project and the chores app, register the app in settings.py, and define the initial chore model.	1
SF-01 — Create the core domain models	1
Create the Django project skeleton and a passing test Goal: Establish an empty Django project that can run its automated tests successfully. Description: Initialize the repository as a Django project with a single project configuration and test runner setup. Add one minimal smoke test that passes, document the command to run tests, and do not implement product features yet.	1
## 1. Empty project with a passing test Goal: Prove the development environment works end-to-end before any app code exists. Description: Initialize a Django project targeting Python 3.14, with a PostgreSQL 18 database connection configured (even if no models exist yet). Add a single trivial test — e.g. a sanity check or a test that a health-check/home route returns HTTP 200 — and confirm it passes via the standard test runner.	1
1. Project setup — Create the Django project and a `chores` app, wire it into `INSTALLED_APPS`, set up the default SQLite database, and confirm the dev server runs.	1
Create the Django project skeleton and chores app	1
### CH-01 · Project skeleton `config/` project, `chores/` app, `base.html`, `static/app.css`, SQLite settings. - `test_check_passes` — `manage.py check` reports no issues - `test_dashboard_url_resolves` — `/` returns 200 with the base layout	1
1. Project scaffolding with a passing test	1
## 1. Set up the test harness and a smoke test Goal: Get one passing test running with a single command. Description: Add pytest and pytest-django to the project, configure them to find Django's settings, and write a smoke test that requests a new `/healthz/` endpoint returning a 200 with the string "ok". This proves the whole loop — routing, view, test runner — works end to end and gives every later task a green baseline to build on.	1
Data models	1
## Task 1 — Project scaffolding (DONE) - `uv add django`, `django-admin startproject config .`, `manage.py startapp chores` - Register `chores` in `INSTALLED_APPS` (`config/settings.py`) - Run initial `migrate`; `manage.py check` passes - Status: complete	1
Models — `Member`, `Chore`, `Occurrence`, `Absence`, `LogEntry` with `Chore` validation and the `(chore, due_date)` unique constraint. Migrations apply.	1
Design and create the data models	1
Member and Chore models with admin	1
1. Project scaffold with a passing test Status: Closed (completed). #1 In juliangarcianagyabi/01_ai_native_workflow_julian;· by juliangarcianagyabi was closed 2h ago	1
## 1. Sign up, log in, and log out Goal: People can create an account and use Django’s session auth. Description: Add signup, login, and logout using Django’s auth system (no email verification, no OAuth). After this task, an unauthenticated visitor can register and sign in. Do not add household logic yet.	1
Task 1: Family and Profile Models. Add the Family model and a Profile model that attaches to Django's built-in User and carries a role of either PARENT or CHILD. Children exist as profiles only and never get login credentials, so a child profile must be creatable without a user. Register both in the Django admin so you can create a family and its members by hand. Done when: make makemigrations chores generates 0001_initial.py, migrate applies it, and manage. py shell you can create one Family, one parent Profile and two child Profiles, then print them back.	1
1. Set up an empty Django project with a passing test Goal: Create the initial Django project structure and verify the test runner works. Description: Initialize an empty Django project using the selected MVP stack direction: Django, PostgreSQL-ready settings, server-rendered templates, HTMX-friendly views, and background jobs later. Add a minimal placeholder test so the repository has a known-good baseline before any product behavior is added.	1
.	1
Set up Django project structure and initialize the app repository.	1
Milestone 1 — Data Model - `Person` model: name, PIN (hashed), active flag - `Week` model: start date, end date (or just start date + auto-computed range) - `Chore` model: week (FK), name, assigned person (FK), completed flag, completed_by (FK, nullable), completed_at (nullable) - Register all models in `admin.py` for quick data inspection/debugging - Initial migration + smoke test in Django admin	1
My task 1 was "Project skeleton with a passing test"	1
Setup the project (I do not have the backlog.md file, I just push everything in plan file via super-power plugins)	1
Task 1: Data models — Chore, Vote, Claim Add to chores/models.py: Chore: title, description, scheduled_for (datetime), is_recurring (bool), created_by (FK to User), created_at. Vote: chore (FK), member (FK to User), points (int), one vote per member per chore. Claim: chore (FK), member (FK to User), mode ("once" \| "ongoing"), week_start (date), is_active. Register all three in chores/admin.py. Run makemigrations / migrate.	1
# Task 1: Database Setup & Migrations - Set up PostgreSQL database connection (optional, currently using SQLite) - Create and run initial migrations for all models - Create Django superuser for admin access - Test database relationships and constraints - Priority: High \| Effort: 2 hours \| Story Points: 3	1
Project setup and Django scaffolding - Create the Django project and app structure - Add the `chores` app to `INSTALLED_APPS` - Confirm the project runs locally via `manage.py runserver` - Set up the initial SQLite database and migrations	1
1. Define the `Chore` model (`chores/models.py`) — fields for title, assigned person, recurrence rule, due date/time, status (pending/done/overdue), and timestamps.	1
Create the chore data model	1
Task 1 — Household roster in admin. Add a Member(name, is_active) model — name unique, is_active defaulting to True, ordered by name — and register it in the Django admin. It ships when you can run the server, open /admin/, and add or deactivate household members. It also folds in the one-time setup the rest of the backlog assumes: the first makemigrations/migrate, a superuser, and the chores/tests/ package layout.	1
Create the Django project and chores app; configure templates, database, and root URL routing.	1
Create the Django project and 'visionboard' app	1
Create the household and chore data model.	1
Create the `chores` Django app	1
Task 1: Define the core Django data model - Create the Django app structure and models for households, users, chore templates, chore logs, perks, and perk redemptions. - Match the planned PostgreSQL schema as closely as possible using Django models and field constraints. - Add model validation for required fields, status choices, and point values. - Create migrations for the database schema. - Acceptance criteria: the app has the core entities and migrations that support the chore approval workflow.	1
Define core models in `chores/models.py`: `Household`, `Member` (linked to a household), `ChoreItem`, `ChoreOccurrence`, `Availability`, `ChecklistEntry`.	1
Define the data model	1
Create the Django foundation: set up the Django project and chores application, register the application in settings.py, and create the initial database models and migrations.	1
Task 1 was to establish the repository documentation and ignore rules. This included creating the README, specification, plan, and backlog documentation, as well as the .gitignore file.	1
Task #1: Data model — Person, Chore, ChoreInstance, Completion. Define the four core models in chores/models.py, register them in the admin, and generate/run the initial migrations.	1
The Agent completed the project withough using a backlog.md	1
• There is no backlog.md file in the current project, so Task 1 cannot be identified from the repository.	1
I am starting this real and big project, therefore, I would imagine the first task is to implement the user authentication with Django framework.	1
"Set up the uv-managed Python project and add Django as a dependency."	1
## 1. Project Setup with a Passing Test Goal: Have an empty Django project that runs and has one passing test. Description: Create a new Django project and a single app (e.g. `chores`), configure it to use PostgreSQL, and commit a minimal `settings.py`. Add one trivial test (e.g. asserting the home page returns a 200, or `1 == 1` if no view exists yet) and confirm `manage.py test` passes, so future tasks have a working CI-able baseline to build on.	1
## 1. Project skeleton with a passing test	1
Establish the domain model and project configuration	1
Initialize Django project, create ip_api app, and register it in settings.py.	1
Bootstrap Django project — create household_chores project and core app, add to INSTALLED_APPS, configure SQLite, create initial migration	1
## Epic 1: Project Setup - [x] Install Django, create virtualenv, pin `requirements.txt` - [x] Create `choretracker` project and `chores` app - [x] Configure SQLite (default), run initial migrations - [x] Verify dev server runs	1
Set up application project skeleton	1
Create `ChoreListView` showing all chores with filters (frequency, assignee, status, room)	1
Bootstrap the Django project. Create the Django project and apps for accounts, households, chores, and notifications; configure PostgreSQL, environment-based settings, static/media storage, logging, and Django admin; add automated formatting, linting, migrations, and a basic test command to CI. Done when the app starts from a clean checkout, the initial migration succeeds, and CI runs a smoke test.	1
Scaffold the Django project and apps — create the config project with the accounts, tenants and links apps, register them in INSTALLED_APPS, and swap in a custom User model before the first migration. Done when manage.py check passes and AUTH_USER_MODEL points at accounts.User.	1
Django forms & csrf Hardening	1
Define core data models (Member, Chore, Assignment) and run migrations	1
Establish a runnable local Django project with one passing automated test. Description Create the project structure, dependency definition, and minimal Django configuration required to run locally. Add a deliberately small smoke test and document the single command that runs it successfully. Do not add product features, data models, or UI beyond what is necessary to prove the foundation works.	1
### Task 1: Django Project Setup - Create Django project - Set up database schema - Configure settings	1
## 1. Project setup - Start Django project + a `chores` app; register it in `INSTALLED_APPS`. - Configure settings for two static household users (no public signup needed).	1
Empty Django project with a passing test — bootstrap Django + SQLite under module_1, Miniconda env, trivial green test via pytest.	1
1. Household chores domain model and migrations	1
## 1. Project skeleton with a passing test Goal: An installable, lintable Django project with `pytest` green on an empty suite. Description: Create `pyproject.toml` (project metadata, deps listed above, `ruff` config, and `[tool.pytest.ini_options]` with `DJANGO_SETTINGS_MODULE = "config.settings"`), `manage.py`, the `config/` project package (`settings.py`, `urls.py` with only the admin route, `wsgi.py`), the `chores/` app package (`__init__.py`, `apps.py`, empty `models.py`, `migrations/__init__.py`), a `tests/` dir, and `.env.example`. Add one trivial test (`tests/test_smoke.py`) asserting `import chores` works, and confirm `ruff check`, `python manage.py check`, and `pytest` all pass.	1
Set up empty Django project with passing test and database connection.	1
Project scaffolding with a passing test	1
User model: extend Django's built-in auth user (or a profile model) with an is_admin flag and household membership, plus Django admin registration for all the models, for quick data inspection during development.	1
1. Project bootstrap with passing test	1
Resolve Persistence and App Configuration	1
0. Foundations [ ] B0.1 (S) Project scaffolding. Django project chores created with uv. Add core app, set TIME_ZONE, LANGUAGE_CODE, SQLite path under a data/ folder so Docker can mount it. [ ] B0.2 (S) Base template. base.html with HTMX loaded from a vendored static file, a simple mobile-first stylesheet, and a {% block content %}. No JS framework. [ ] B0.3 (S) Dev tooling. ruff config in pyproject.toml, a Makefile or justfile with run, test, migrate, lint.	1
Create the Django project and expenses app.	1
1. Project Initialization & Base Test Suite Goal: Scaffold the initial Django project structure with a verified passing test. Description: Initialize the Django project named chore_manager alongside an application named core configured with SQLite. Create a basic smoke test in core/tests.py ensuring the test runner runs smoothly. Verify that running python manage.py test executes and passes cleanly.	1
Foundation	1
### T1. Core models: Household, Member, Chore The three nouns everything else hangs off. - `Household` — name, created_at. - `Member` — FK to `Household`, OneToOne to `auth.User`, `role` choices (`admin` / `member` / `guest`), display name. - `Chore` — FK to `Household`, name, category, `effort_weight` (small int, the fairness currency), `frequency` (choices: once / daily / weekly / monthly), `estimated_minutes`, active flag. Files: `chores/models.py`, migration. Done when: migrations apply; objects creatable in `manage.py shell`. Note: use a `Member` profile rather than a custom `AUTH_USER_MODEL` — households are many-to-one over users conceptually, and swapping the user model later is far more painful than adding a profile now.	1
# Backlog ## Task 1: Create Chore model - [x] Confirm the Django app that owns chore functionality. - [x] Define the `Chore` model with a title and description. - [x] Add due date and completion status fields. - [x] Add points and recurrence fields. - [x] Add an assignee relationship that can support family members. - [x] Add created and updated timestamps. - [x] Configure useful model ordering and string representation. - [x] Create and apply migrations. - [x] Add model tests for required fields and default values.	1
Scaffold the Django project and register the chores app.	1
Backlog: _docs/tasks.md, 23 ordered tasks. Answer: Task 1 — "Project skeleton and shared persistent storage: a runnable Django project with dev/prod/test settings reading SECRET_KEY and DATABASE_URL from .env, on SQLite with a documented path to PostgreSQL, and an explicit timezone. It is first because plan.md §9 requires one shared server-side database.	1
## 1. Set up the Django project and main application Priority: High As the development team, we want a runnable Django foundation so that we can build the household chores application.	1
Django env setup and data models	1
Define data models — Create `Chore`, `HouseholdMember`, and `ChoreAssignment` models in `chores/models.py` (name, description, due date, assignee, completion status).	1
Set up the initial project with a passing test. The task includes creating the Django app and installing the required dependencies.	1
##1. Project scaffolding with a passing test Goal: A runnable Django project with one green test. Description: Set up the `uv`-managed Django project (`household_chores` project, `chores` app), wired into `INSTALLED_APPS`. Add one trivial test (e.g. asserting the Django test client gets a 200 from a health-check or default URL) and confirm `uv run python manage.py test` passes.	1
1. Project bootstrap: Run the empty Django app	1
Create the Member and Chore domain models, register them in Django admin, create and apply the initial migration, and add model tests.	1
Establish application foundation and local persistence. Obs: It is tracked as GitHub issue #1.	1
Task 1: Project scaffolding with a passing test	1
Basic model for roommates , chores , recurring chores	1
Project bootstrap — set up the initial Django project structure and local development environment using Django, SQLite, uv, pytest, and pytest-django.	1
Set up the Django project and chores app with a passing initial test.	1
Task 1: Scaffold Django project + chores app	1
Add the Django chores page: create a view, URL, and template that display the current chore list with each chore marked as done or not done.	1
### TASK-001 — Record MVP implementation decisions - Description: Document the choices required before data modelling: account creation/role-selection flow, text-only versus file-based assignment response, single-submission versus replacement policy, mark range, and attendance-rate denominator/status rule. Keep choices within the approved MVP. - Dependencies: None. - Expected outcome: A short documented decision record that gives later tasks unambiguous rules to implement and test.	1
Create the household home page	1
1. `Task` model (`core/models.py`) — fields for `name`, recurrence type (`interval`/`fixed`), the recurrence parameters (`every_days`/`every_months`/`every_years` or `schedule`/`day`/`day_of_month`/`month`), `last_done`, `last_note`, `snooze_until`. Run `makemigrations` / `migrate`.	1
## 1. Project setup with an empty passing test Goal: Get a runnable Django project skeleton with one green test. Description: Confirm/initialize the Django project (`choretracker`) and a `chores` app, wire the app into `INSTALLED_APPS`, and add a placeholder URL with a minimal view (e.g. returning a 200 with a plain "OK" response). Add a single test that uses the Django test client to hit that URL and asserts a 200 response, so `python manage.py test` passes. No models or business logic yet — this task just proves the project boots, routes a request, and the test runner works.	1
Project setup with a passing test	1
Task 1: Build the dashboard shell and browser persistence foundation.	1
"Django scaffold with a passing test" — create the project + chore app, register it in INSTALLED_APPS, render an empty chore list on the home page, and get uv run python manage.py test passing with one trivial test.	1
Backlog task #1: "Data models: Household, Membership, Chore"	1
Profiles & profile switcher Create a `Profile` model (name, role: adult/child, avatar/color). Seed the 4 family profiles (2 adults, 2 children). Build a simple "who's using this?" landing page to pick a profile (no password), stored in the session.	1
- [ ] Init Django project + app (`chores`)	1
Task #1 is “Define Core Domain Constants and Data Model Skeleton.” Its goal is to establish the project’s foundational Django data model by defining the core models and domain enumerations, creating the initial database migration, and registering the models in Django Admin without implementing business workflows.	1
"Define the Domain Models": add Housemate and Chore models in chores/models.py with the fields from the spec, required fields enforced, and __str__ methods, without adding migrations.	1
## 1. Project scaffolding with a passing test Goal: Get an empty project running with one passing test. Description: Set up the project skeleton (framework install, one app/module, base configuration) and add a single trivial test that passes — for example, that the app's health/login page responds successfully. No domain models or business logic yet; this task only proves the toolchain and test runner work end to end.	1
## 1 — Project setup (priority: High) - Create Django project + `chores` app (migrations applyable). Acceptance: `manage.py migrate` runs; admin accessible. - Add basic settings, templates, `requirements.txt`.	1
Task 1 - Core data models + admin Create HouseholdMember, Chore and Assignment models in the chores app. Register all three in the Django admin with sensible list_display, list_filter and search fields. Add makemigrations / migrate. Done when: the three models exist and are editable in /admin/.	1
## 1. Core Data Models Setup Goal: Define the Django database models for Household, User, ChoreTemplate, ChecklistItem, TaskInstance, and TaskNote. Description: Implement Django ORM models matching the MVP specifications with appropriate fields, foreign keys, and status choices (Not Started, In Progress, Completed, Skipped). Generate and run migrations to create the corresponding SQLite database tables and register them in Django's admin interface for easy debugging.	1
Define the domain models and admin setup	1
Task 1.1: Core App & User Management Setup - Implement `Household` and `Household Member` models. - Create registration, login, and household creation/joining views.	1
Set up the application foundation	1
recurring schedule generator	1
Resolve the blocking product rules by defining the initial beta defaults for authentication, permissions, age groups, deadlines, points, refusal escalation, rejection actions, reminders, data retention, and child safety	1
Initialize an empty Django project that runs and has a passing test.	1
Project skeleton with a passing test	1
note that my backlog is a list of github issues, not a backlog.md file. 1. Project skeleton with a passing test Goal: python manage.py test runs green against the scaffolded project. Description: The cityjournal project and places app already exist on disk, but the app is not yet registered, so Django cannot see its models, commands, or tests. Add "places" to INSTALLED_APPS in cityjournal/settings.py, run migrate to create the initial SQLite database, and replace the empty places/tests.py with one trivial assertion. Done when the test runner discovers and passes that test.	1
# 1. Data model — Household and membership - `Household` (name, created_at). - `Membership` linking `settings.AUTH_USER_MODEL` to a `Household`, with a `display_name` and unique-together on (household, user). - Stick with Django's built-in `User`; no custom user model. - Migrations + `__str__` methods.	1
## 1. Set up an empty Django project with a passing test Goal: Establish a runnable project and a working test command before adding product features. Description: Create an isolated Python environment, pinned dependencies, one Django project, and one empty household application using Python 3.14.7, Django 6.1.1, and SQLite. Add a minimal placeholder page and a Django smoke test that verifies its successful response, without adding domain models or authentication flows. Document installation, development-server, and test commands in README.md, exclude local environments and database files from version control, and verify the test passes.	1
Define `Household` model (name, created date) \| One household per group of roommates/family.	1
## 1. Initialize repository and backend skeleton with a passing test — done (#1) - Goal: A runnable, empty FastAPI project with one green test. - Description: Created backend/ as a uv-managed FastAPI project with a GET /health endpoint and a pytest suite containing one test that asserts /health returns 200. README documents install/test/run; frontend/ holds a placeholder.	1
1. Project scaffold with a passing test (https://github.com/yakan/swim-self-learning-tool/issues/1)	1
Add Member model — name, color, is_active, order fields per plan.md. name (CharField) — the member's display name color (CharField, optional) — used for dashboard chips so each person is visually distinguishable is_active (BooleanField, default True) — inactive members are skipped when the rotation logic picks who's next order (PositiveIntegerField) — a fixed rotation order among active members, which is what the rotation engine uses to pick "the next person after the current cursor" (wrapping around when it reaches the end)	1
Household & Person models — chores app models for Household and Person (name, household FK). Supports "Manage household" (feature 5).	1
1. Set up an empty Django project Create the Django project with uv, add the application package, register the app, and keep the project free of product features. Add one basic test proving the Django test suite runs successfully. Acceptance criteria: Dependencies are declared in pyproject.toml and locked with uv.lock. uv run python manage.py check succeeds. uv run python manage.py test succeeds with at least one passing test. The application is registered in INSTALLED_APPS.	1
Task 1 - Set up the Django project and chores app — install Django, create the project/app, configure the app in settings.py, add a health/dashboard route, and verify the development server starts.	1
## 1. Data models - [x] `Household` model (a household has a shared link/slug, no auth) - [x] `Person` model (name, belongs to a `Household`, no password) - [x] `Chore` model (name, belongs to a `Household`, fixed daily recurrence) - [x] `ChoreAssignment` — links a `Chore` to a `Person` (fixed, permanent assignment, not rotating) - [x] `ChoreLog` — one entry per chore per day: status (`done` / `missed`), timestamp, done by	1
Custom user model	1
Set up the Django project and claims app, and register claims in INSTALLED_APPS.	1
## 1. Project Scaffolding and Test Suite Setup Goal: Ensure the project has testing tools configured and passes a baseline test. Description: Configure pytest and pytest-django via uv to establish the automated testing pipeline. Add a baseline test file confirming the Django configuration loads and the test runner executes cleanly. Verify that running uv run pytest succeeds without warnings or errors.	1
#1 Foundations - [ ] Data models: `Household`, `User` (extend `AbstractUser` with `display_name`, `role`, `household` FK), `Category` (seeded, `is_system`), `Chore`, `ChoreAssignee` (join table), `CompletionHistory`. Design `User`/`Household` as a FK now (not M2M) so multi-household support can be added later without a schema rewrite. - [ ] Custom user model wiring: set `AUTH_USER_MODEL`, register in admin, initial migration. Must be done before any other migration touches `User`. - [ ] Seed data: management command or migration to create the fixed category list (Cleaning, Kitchen, Laundry, Bathroom, Bedroom, Shopping, Trash, Pet Care, Other).	1
## 1. Scaffold the empty Django project Goal: Create an empty ChoreCrew Django project with one passing smoke test. Description: Initialize the selected Python and Django versions with a minimal project structure and dependency configuration. Add one smoke test that proves Django starts and the test suite passes, without implementing product behavior.	1
Bootstrap Django project and app — django-admin startproject and python manage.py startapp; configure INSTALLED_APPS in settings.py.	1
## Task 1 — Establish the application foundation Create the initial responsive web-application structure, including a documented approach for authentication, an authenticated application shell, and a place to select the active household once households exist.	1
Task 1 is “Finish project foundation and authentication”, which includes completing the Django settings, adding a responsive base layout, implementing login/logout, and requiring authentication for app views	1
Project Setup & Base Shell : Next.js App Router project setup and basic Placement & Internship Tracker UI shell.	1
1. Core data models — `Member` (household member), `Chore` (name + recurrence), and `ChoreAssignment` (chore, assigned member, period, done flag/timestamp). Register all three in Django admin so data can be entered manually before any UI exists.	1
Data models + migrations	1
Phase 0 (Project setup) - has task #1 Create the Django project (`config`) and the `chores` app, register the app in `INSTALLED_APPS`. Phase 1 (Domain model) - has task #1 for creating model Member — name, is_active, __str__.	1
Create the core data models.	1
Task 1 in backlog.md: Establish the domain model. Scope - Add `Household` and `Membership` models. - Enforce the MVP rule that a user belongs to at most one household. - Add the `Chore` model with name, description, household, creator, optional assignee, due date, schedule, and status. - Use explicit choices for one-off/daily/weekly/monthly schedules and active/completed status. - Add model validation for required names and household-consistent creator/assignee relationships. Done when - Migrations run successfully. - Model tests cover required fields, schedule/status choices, and household membership constraints.	1
## Task 1: Create household and member models Implement the foundation for one household with members and shared admins. - Add `Household` and `Member` models. - Generate a persistent household access code. - Require member names to be unique within a household. - Support multiple admins and preserve removed members for history. - Create and run migrations. Done when a household and its members can be created in the Django admin and the model constraints are covered by tests.	1
Task 1: Project scaffolding + Docker + CI + context docs — Enable any engineer to docker compose up a working Django project so future work has a consistent baseline	1
Setup project and base models with a passing test	1
TASK SPECIFICATION: 2. Household Model Goal Implement the Household model to support multiple apartments/families and act as the core tenant model. Implementation Details Target files: chores/models.py chores/admin.py chores/tests.py Key technology rules: Multi-Tenancy: This is the core tenant model. Other models will link back to this. Technical Requirements Create Household class inheriting from django.db.models.Model. Fields: name: models.CharField(max_length=255) join_code: models.CharField(max_length=10, unique=True) - used to invite new members. String Representation: Override __str__ to return the name. Acceptance Criteria The Household model is present in chores/models.py. The Household model has exactly two fields (name, join_code) with the correct constraints. join_code is explicitly set to unique=True. The __str__ method returns the household's name. The Household model is registered in chores/admin.py. The Django Admin list view for Household includes name and join_code. The makemigrations command successfully generates a migration file for the Household model without errors. Test Requirements Verify model creation: Create a Household instance with valid data and assert it is saved in the database correctly. Verify UniqueConstraint: Create a Household with a specific join_code, attempt to create a second Household with the SAME join_code, and assert that django.db.utils.IntegrityError is raised. Verify string representation: Assert that calling str() on a Household instance returns its name. OUT OF SCOPE Do NOT build views or HTML templates for this model. Do NOT create any API endpoints for this model. Do NOT implement the User model in this issue (that is Issue 3. User Model & Authentication Setup #3).	1
1. Project scaffold with a passing test Goal: Get an empty Django backend and React frontend running side by side with one green test each. Description: Create a Django project with DRF installed and a single pytest test that hits a health-check endpoint and asserts 200. Create a Vite + React app alongside it with one Vitest test that renders a placeholder component. No real features yet — this task just proves the toolchain works end to end. This one's already done (it's issue #1, closed per AGENTS.md's "Current state" section).	1
Task 1 is Data models — defining the core Django models before anything else: Household (name, auto-generated join code) Member (name, linked to household, no password auth) Chore (title, is_predefined flag, status, assigned_to/assigned_by, completed_by/completed_at) A create_predefined_chores(household) helper to seed the 10 predefined chores Admin registration for all models in chores/admin.py	1
## 1. Project skeleton + passing test Goal: Create an empty repository layout and verify CI/test runner with one passing test. Description: Initialize a minimal Python project structure (backend/frontend/docs), add a simple pytest test that always passes (e.g., assert True), and add a GitHub Actions workflow that runs tests. Confirm the CI workflow passes locally or in the Actions run.	1
## A-1 - Custom user model Replace `auth.User` with `expenses.Member` and set `AUTH_USER_MODEL`. Delete the local `db.sqlite3` and re-run migrations from stratch. Depends on: D1 Done when:`AUTH_USER_MODEL` = `expenses.Member`; `migrate` succeeds on an empty DB; `createsuperuser` works; `Member` is registered in the admin.	1
Task 1: “Set up a Django project and chores app, configure INSTALLED_APPS, and create basic models for Housemate and Chore with fields for name, optional assignee, frequency, and last completed date.”	1
1. Project setup Goal: Create a Django project with a passing test. Description: Initialise a new Django project (`household`) and app (`chores`) using `django-admin` and `manage.py`. Confirm the default test runner works by writing one smoke test that asserts `True`. Confirm the test suite runs green with `python manage.py test`.	1
## Epic 1: Project Setup - [ ] #1 Create project (`chores_project`) and app (`chores`) - [ ] #2 Register `chores` app in `settings.py` → `INSTALLED_APPS` - [ ] #3 Configure SQLite database (default) and run initial migrations - [ ] #4 Create a superuser (admin account) via `createsuperuser`	1
## Foundation - [x] Configure the Django application — Register `chores`, configure environment-based settings, and add a basic health-check or home page. - [x] Create the initial database migration — Confirm SQLite development configuration and establish the migration workflow.	1
Data model. Create Cat and Chore (with frequency, time of day, and an optional cat/assignee)	1
## 1. Project setup with a passing test Goal: Verify the existing Django scaffold runs with a pinned dependency list and a passing test suite. Description: The repo already contains a bare Django 4.2 scaffold (`config/` project, empty `chores/` app, `manage.py`, `.venv` on Python 3.9). Add a `requirements.txt` (Django, python-dateutil, requests, pywebpush), a `.env.example` with placeholder variables (SECRET_KEY, LLM_GATEWAY_, VAPID_, WHATSAPP_*), and a smoke test in `chores/tests.py` asserting the `chores` app is installed and `manage.py check` is clean. Done when `.venv/bin/python manage.py test` exits 0.	1
Initialize Django Project & Setup Models	1
B-01: Fix timer pause/resume state persistence The timer currently resets on page reload. Add localStorage persistence for remaining, mode, running, and startTime so a browser refresh does not lose an active session. Acceptance: Start timer → refresh page → timer shows correct remaining time and continues counting.	1
Task 1: Define Chore & Reaction Models and Run Migrations (Define the Chore and ThankYouReaction data models in chores/models.py and run database migrations).	1
- Household & Member models. Household(name), Member (household FK, name, order) — order is the rotation position, set by creation order. Migration + Django admin registration (roster management is unscored supporting functionality — admin is enough, no custom UI needed).	1
Task 1 — Django project and app skeleton Install Django, create project portfolio_lens and app portfolio. Register portfolio in INSTALLED_APPS in portfolio_lens/settings.py. Add a /health/ view returning {"status": "ok"}. Confirm python manage.py runserver serves it and python manage.py test passes with one test asserting the health view returns 200. Done when: server starts, health endpoint responds, test suite green.	1
## 1. Project setup - [x] Django project (`config`) + `chores` app, uv-managed env - [x] Base settings: timezone, `AUTH_USER_MODEL` decision, templates dir, static files (`accounts.User` thin subclass created up front; DB reset; `templates/` + `static/` wired; auth redirect settings) - [x] Base template + simple nav, a `home` view (`base.html`, `home.html`, `registration/login.html`; `HomeView`; `django.contrib.auth.urls` included) - [x] Dev tooling: Makefile (`run`/`migrate`/`test`/...) + README run commands	1
1. Create a Django app (`chores`) and register it in `INSTALLED_APPS`	1
• Task 1: Data Models & Migrations (Define Member and Chore models, register them in admin, and apply migrations). • Backlog file: backlog.md	1
Sprint 1: Data Models & Django Admin / TASK-01: Implement Core ORM Models	1
Create the Member and Chore data models and their database migrations.	1
Basic Database Models & Admin	1
Establish the database and application foundation	1
### 1.1 Django Project Initialization - [ ] Create Django project and main app structure - [ ] Set up virtual environment and install dependencies (Django, PostgreSQL driver) - [ ] Configure settings.py (database, static files, timezone) - [ ] Create .env file for environment variables	1
## Tarea 1: Setup Core y Configuración Base - Objetivo: Inicializar el proyecto Django `mastering_project` y la app `suite_api`.	1
## Phase 1: Project Setup & Predefined Data - [x] TASK-01: Initialize Django Project and App - Bootstrap Django project (`household_chores`) and application (`chores`). - Configure `INSTALLED_APPS` in `settings.py`. - Set up virtual environment, dependencies (`requirements.txt`), and `.gitignore`.	1
Project & app scaffolding — create the config project and catalog app, register it in INSTALLED_APPS, wire templates + routing, confirm the server boots	1
Task1 : Create the empty Django project with a passing test --Set up a minimal Django project structure with no product features implemented yet.	1
1. Empty project with a passing test ## Goal A runnable Django 5.x project with `pytest`, `ruff`, and `.env` loading in place, one green test, and README instructions for running the server and the tests. ## Acceptance criteria - [ ] `uv sync` installs Django 5.x, `pytest`, `pytest-django`, `ruff`, and `django-environ`. - [ ] `config/` settings package exists, SQLite is the database, and a `chores` app is registered in `INSTALLED_APPS`. - [ ] Settings read `SECRET_KEY`, `DEBUG`, and `ALLOWED_HOSTS` from a `.env` file via `django-environ`; `.env.example` is committed and `.env` is gitignored. - [ ] `uv run pytest` runs and reports one passing test. - [ ] `uv run python manage.py check` reports no issues. - [ ] `uv run ruff check .` passes. - [ ] README has a "Development" section (run the dev server) and a "Tests" section (whole suite + a single file). ## Out of scope - Any domain models — `Person` / `Chore` land in #2. - CI configuration. ## Constraints - Dependency versions declared in `pyproject.toml`; `uv` is the package manager. - Keep the generated `django-admin startproject` layout; only add what the criteria require. --- _Status: implemented on branch `task-1-project-scaffold` (commit `ad72f16`). Ready to verify against the above and close._	1
1. Set up the project skeleton with a passing test Goal: A clean Django project that runs and has one test proving the setup works. Description: Confirm the reading_club project and club app are wired together, run the initial migrations to create db.sqlite3, and add a minimal smoke test in club/tests.py that requests the site root and asserts a 200 response. Add a placeholder home view and URL route so that test has something to hit, and set TIME_ZONE in settings to the club's actual zone so timestamps do not display in UTC. Done when uv run python manage.py test passes and uv run python manage.py runserver serves a page.	1
Task 1 — Set Up Django Project and Core App It involves installing Django, creating the Django project and projects app, adding the app to INSTALLED_APPS, running migrations, and verifying the development server works.	1
Define the core data model	1
Data model integrity constraints : Owed turn count and chore frequency validations are added in that task	1
Create core Django models Implement the Student, Assignment, and AssignmentStatus models and create migrations.	1
Task 1 is the "Bootstrap Django and prove the baseline". We create the Django project and app, register the app, apply the initial migrations, add a minimal smoke test, and document the commands for setup, running, and testing ## Task 1 — Bootstrap Django and prove the baseline ### Goal Create the Django project and a single application package, with the smallest runnable configuration and test setup needed for later work. ### Acceptance Criteria - The repository contains a Django project and one Django app for the household-chore functionality. - The app is registered in Django settings and the project starts with Django's development server using the documented command. - The initial Django migrations apply successfully to a clean local database. - Automated tests use Django's built-in test runner. - A single minimal smoke test proves that Django can load the app, and the full Django test command `uv run python manage.py test` passes. - The README (or an equivalent short developer note) states the commands to install dependencies, migrate, run the server, and run tests, including `uv run python manage.py test` as the documented full test command. ### Out of Scope - Household, member, or chore models. - User-facing feature pages or workflows. - Authentication, authorization, and current-member selection. - Pytest or another alternative test runner unless a later approved task explicitly requires it. - Production deployment configuration or styling.	1
Set up the Django project	1
Configure Django base: config/settings.py:33 DATABASES, TIME_ZONE, STATIC_URL, TEMPLATES DIRS, add chores to INSTALLED_APPS - AC: uv run python manage.py check passes + db.sqlite3	1
It covers adding Django to a reproducible dependency file, configuring development settings, and confirming that python manage.py passes successfully.	1
## 1. Initialize Django Project with Docker and Passing Test Goal: Set up a minimal Django project with Docker that runs a passing test. Description: Create a Django 5.x project structure with Docker Compose for PostgreSQL, Redis, and the web service. Configure a basic test that verifies the project starts correctly (e.g., a simple view returning 200 OK). Include requirements.txt, Dockerfile, docker-compose.yml, and initial Django settings.	1
TASK-01: Define Core Models (Member, Chore, ChoreCompletionLog) Description: Implement models in chores/models.py with proper fields, choices, and relationships according to the specification. Acceptance Criteria: Member has name, avatar_color, and created_at. Chore supports choices for chore_type (ROTATING, POOL), weight (1–3), frequency_days, assigned_to (nullable ForeignKey to Member), and is_active. ChoreCompletionLog tracks chore, completed_by, completed_at, and effort_weight. Migrations are created (makemigrations) and applied (migrate) successfully.	1
1. Install Django	1
✅ Set up an empty Django project with a passing test. More specifically for the training's project: Task 1: Set up the Django project/app, dependencies, and a passing test.	1
Bootstrap the Django project.	1
Create the database models and migrations for households, one admin and ordered members, the household's next rotation position, and chores with assignee, due date, and completion details. Acceptance criteria - Each user belongs to at most one household and has an admin or member role. - Memberships have an admin-controlled rotation order and active status. - A chore belongs to one household and stores its assignee, due date, creator, completion time, and completing user. - Model validation prevents cross-household assignments and allows only one admin per household. - Migrations apply successfully.	1
Set up the empty Django project	1
https://github.com/davidacodes/family_chore_tracker/issues/10 Goal: Let kids mark a chore done for a specific calendar date. Description: Add a completion model keyed by chore and concrete date so history is separate from reusable weekly assignments. Implement checkbox behavior for marking chores complete from the main calendar without requiring parent PIN entry.	1
## Task 1 — Define core data model and migrations - Implement `Chore` and `Completion` models in the `chores` app. - Add field validation rules: - `weekly_target` required and `>=1` when `recurrence_type=weekly_target` - `due_date` required when `recurrence_type=one_off` - Create and apply migrations. - Add Django admin registration for both models. Done when - `poetry run python manage.py makemigrations` creates migration files cleanly. - `poetry run python manage.py migrate` applies successfully. - Models are visible and editable in admin.	1
## 1. Set up empty project with passing tests Goal: Initialize Django + HTMX project with SQLite, uv, and basic test suite Description: Create a new Django project using uv, configure settings for SQLite database, set up project structure for HTMX views, create the first minimal test file, and run initial tests to verify everything works.	1
Add Django REST Framework + `djangorestframework-simplejwt`; wire up `/api/v1/` URL namespace	1

5. Which command starts the Django development server?

319 / 337 correct (94.7%)

1 uv run python manage.py runserver 319 (94.7%)

2 uv run django-admin startserver 0 (0.0%)

3 python manage.py start 7 (2.1%)

4 uv run python app.py runserver 11 (3.3%)

6. Which command runs the tests in the terminal?

288 / 337 correct (85.5%)

1 pytest 45 (13.4%)

2 uv run python manage.py test 288 (85.5%)

3 python -m django run_tests 3 (0.9%)

4 django-admin test 1 (0.3%)

Calculated: 10 September 2026, 13:04