64b8e0d80c
- Initialize npm workspaces monorepo (backend, frontend, shared-types) - Scaffold NestJS backend with modules: Auth, Users, Tasks, Projects, Inbox, Health - Create React frontend with Vite, TailwindCSS, Radix UI - Implement TypeORM entities: User, InboxItem, Task, Project - Add JWT authentication with Passport.js and bcrypt - Build Inbox capture API (POST /inbox, GET /inbox, POST /inbox/:id/process) - Create Inbox UI with quick-add form and GTD processing workflow modal - Configure Docker Compose stack (postgres, redis, backend, frontend) - Add health check endpoint with database/Redis status - Write unit tests for auth and inbox services Phase 1 features complete: - GTD Inbox Capture: Manual tasks via web form quick-add - GTD Processing Workflow: Interactive inbox processing interface Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
67 lines
2.1 KiB
Markdown
67 lines
2.1 KiB
Markdown
---
|
|
active: true
|
|
iteration: 1
|
|
max_iterations: 30
|
|
completion_promise: "PHASE_1_COMPLETE"
|
|
started_at: "2026-01-11T08:23:00Z"
|
|
---
|
|
|
|
# Phase 1: Foundation
|
|
|
|
## Context
|
|
|
|
Read PROMPT.md for full project requirements and context.
|
|
This prompt focuses ONLY on Phase 1: Foundation.
|
|
|
|
## Phase Objective
|
|
|
|
Project setup, core infrastructure, and initial configuration
|
|
|
|
## Phase 1 Tasks
|
|
|
|
- [ ] GTD Inbox Capture: Multi-source task capture system that ingests tasks from manual web form, REST API, email (IMAP/Microsoft Graph), and ConnectWise Manage sync into an unprocessed inbox for later GTD clarification
|
|
- Acceptance: Manual tasks can be submitted via web form quick-add and appear in inbox
|
|
- [ ] GTD Processing Workflow: Interactive inbox processing interface that guides users through GTD clarification: converting raw inbox items into Next Actions with context tags, Projects, Waiting For items, Someday/Maybe, Reference Material, Tickler items, or Trash
|
|
- Acceptance: Inbox view displays unprocessed items with processing workflow controls
|
|
|
|
## Working Instructions
|
|
|
|
1. Read PROMPT.md to understand the full project context
|
|
2. Focus ONLY on the tasks listed above for this phase
|
|
3. For each task:
|
|
- Implement the feature
|
|
- Write tests
|
|
- Run: npm run build && npm run test && npm run lint
|
|
- Update prd.json to set passes: true for completed features
|
|
- Append progress to progress.txt
|
|
- Commit with conventional commit message
|
|
|
|
## Constraints
|
|
|
|
- Always run tests before committing
|
|
- Never commit failing code
|
|
- Do not implement features from other phases
|
|
- Make reasonable decisions - do not ask questions
|
|
- Update prd.json when features complete
|
|
|
|
## Verification
|
|
|
|
After completing all Phase 1 tasks:
|
|
```bash
|
|
npm run build && npm run test && npm run lint
|
|
```
|
|
|
|
All commands must pass with zero errors.
|
|
|
|
## Completion
|
|
|
|
When ALL Phase 1 tasks are complete and verified:
|
|
- All features for this phase pass their acceptance criteria
|
|
- prd.json shows passes: true for all Phase 1 features
|
|
- Build, test, and lint all pass
|
|
|
|
Output: <promise>PHASE_1_COMPLETE</promise>
|
|
|
|
If blocked and cannot proceed:
|
|
Output: <promise>ABORT_BLOCKED</promise>
|