Initial Ralph scaffold

prompts/phase1-prompt.txt

@@ -0,0 +1,58 @@
+# 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>

prompts/phase2-prompt.txt

@@ -0,0 +1,60 @@
+# Phase 2: Core
+
+## Context
+
+Read PROMPT.md for full project requirements and context.
+This prompt focuses ONLY on Phase 2: Core.
+
+## Phase Objective
+
+Main functionality and core features implementation
+
+## Phase 2 Tasks
+
+- [ ] ConnectWise Manage Integration: Read-only sync from ConnectWise Manage that imports service tickets, project tickets, and projects assigned to user. Projects with zero tickets surface as planning tasks. ConnectWise priority/SLA displayed for reference only; user assigns manual priority
+  - Acceptance: ConnectWise API integration syncs assigned service tickets as inbox items
+- [ ] Intelligent Calendar Scheduling: Automatic scheduling engine that pulls from CalDAV calendars (Nextcloud, Google Calendar, Outlook via Microsoft Graph) and places actionable tasks into available time slots, respecting working hours, context constraints, deadlines, and manual priority. Supports drag-drop manual override and task locking
+  - Acceptance: Engine reads existing events from CalDAV/Google/Outlook calendars
+- [ ] Interactive Calendar Week View: React SPA with interactive week-view calendar displaying scheduled tasks and calendar events. Supports drag-and-drop task rescheduling, manual time adjustments, and real-time updates when scheduling changes occur
+  - Acceptance: Week view renders all scheduled tasks and synced calendar events
+
+## 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 2 tasks:
+```bash
+npm run build && npm run test && npm run lint
+```
+
+All commands must pass with zero errors.
+
+## Completion
+
+When ALL Phase 2 tasks are complete and verified:
+- All features for this phase pass their acceptance criteria
+- prd.json shows passes: true for all Phase 2 features
+- Build, test, and lint all pass
+
+Output: <promise>PHASE_2_COMPLETE</promise>
+
+If blocked and cannot proceed:
+Output: <promise>ABORT_BLOCKED</promise>

prompts/phase3-prompt.txt

@@ -0,0 +1,60 @@
+# Phase 3: Integration
+
+## Context
+
+Read PROMPT.md for full project requirements and context.
+This prompt focuses ONLY on Phase 3: Integration.
+
+## Phase Objective
+
+External services, error handling, and system integration
+
+## Phase 3 Tasks
+
+- [ ] Weekly Review Interface: Dedicated GTD Weekly Review interface with auto-scheduled recurring review block. Shows all active projects, next actions per project, unprocessed inbox count, waiting-for items, and someday/maybe list for systematic review
+  - Acceptance: Weekly Review block auto-scheduled at user-configured recurring time
+- [ ] GTD Contexts and Life Domains: Context label system (@desk, @phone, @errand, @homelab, @anywhere) and domain organization covering Work (ConnectWise tasks), Homelab (Proxmox, networking, 3D printing, NAS), Daily Routines (meals, exercise, supplements), House (maintenance, errands, cleaning), and Professional Development (Azure certification)
+  - Acceptance: Tasks taggable with context labels (@desk, @phone, @errand, @homelab, @anywhere)
+- [ ] Waiting For and Tickler System: Waiting For list tracks items delegated or awaiting external input with optional follow-up dates. Tickler/Deferred items stored with future activation dates and automatically surface to inbox on specified date
+  - Acceptance: Waiting For list displays all items awaiting external action
+
+## 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 3 tasks:
+```bash
+npm run build && npm run test && npm run lint
+```
+
+All commands must pass with zero errors.
+
+## Completion
+
+When ALL Phase 3 tasks are complete and verified:
+- All features for this phase pass their acceptance criteria
+- prd.json shows passes: true for all Phase 3 features
+- Build, test, and lint all pass
+
+Output: <promise>PHASE_3_COMPLETE</promise>
+
+If blocked and cannot proceed:
+Output: <promise>ABORT_BLOCKED</promise>

prompts/phase4-prompt.txt

@@ -0,0 +1,58 @@
+# Phase 4: Polish
+
+## Context
+
+Read PROMPT.md for full project requirements and context.
+This prompt focuses ONLY on Phase 4: Polish.
+
+## Phase Objective
+
+Documentation, optimization, testing, and final packaging
+
+## Phase 4 Tasks
+
+- [ ] GTD Project Management: Project hierarchy supporting multi-step outcomes with next actions, reference material attachments, notes, and project status tracking. ConnectWise projects with zero tickets surface as planning tasks requiring work breakdown
+  - Acceptance: Projects created with name, description, desired outcome, and domain
+- [ ] Notifications and Rescheduling Alerts: Real-time notification system via WebSocket, email, and optional webhook when automatic rescheduling occurs due to calendar conflicts, when Waiting For follow-ups are due, or when Tickler items activate
+  - Acceptance: WebSocket push notifications to active browser sessions when tasks reschedule
+
+## 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 4 tasks:
+```bash
+npm run build && npm run test && npm run lint
+```
+
+All commands must pass with zero errors.
+
+## Completion
+
+When ALL Phase 4 tasks are complete and verified:
+- All features for this phase pass their acceptance criteria
+- prd.json shows passes: true for all Phase 4 features
+- Build, test, and lint all pass
+
+Output: <promise>PHASE_4_COMPLETE</promise>
+
+If blocked and cannot proceed:
+Output: <promise>ABORT_BLOCKED</promise>