PrintQueue
scores
progress30%
prioritymedium
complexity5/10
readiness7/10
excitement5/10
hours invested0h
last12 days ago
claude · 1 hour ago
PrintQueue is thrashing — regressed from launching→idea→designing→development→designing within 48h, with progress slashed from 88% to 30%. Signals a scope/identity crisis, not a build problem.
- Write a one-paragraph description and tagline today
- Define the single core user and print job flow
- List the 3 features required for v1, cut rest
- Pick deployment target (local CUPS vs cloud) and commit
- Stop stage-toggling until scope doc is written
Plan from /cl
- Order intake — upload or preset + submit/order creates an order; valid file saved to the Docker volume · done 13 days ago
- Operator queue board with live polling/queue lists jobs oldest-first and refreshes within 10s · done 13 days ago
- Status control (Pending -> In Progress -> Done)PATCH advances and steps back status; board reflects change · done 13 days ago
- Preset library managementOperator uploads and deletes reusable preset designs · done 13 days ago
- Customer confirmation + live status pageTicket number shown; status page fires browser notification when Done · done 13 days ago
- Operator auth gate/queue* and mutating API routes require the password cookie · done 13 days ago
- File storage on Docker volume + validationUploads on pq-data volume; png/jpeg/pdf only, max 10MB enforced server-side · done 13 days ago
- Deploy to komarlab.com with real passwordLive URL responds; deployed commit matches local
Recent checkpoints
- 13 days ago0.5h