Welcome to the 90-minute sprint! This document tells you exactly what's been set up and where to start.
Your team has a complete specification package for the Morning Command Center prototype. No ambiguity. No extra meetings. Just spec and build.
- README.md — Project overview (1 min)
- QUICK_REF.md — One-page sprint guide (2 min)
- PROJECT_PLAN.md — 90-minute timeline & task breakdown (3 min)
- SETUP.md — Environment setup & dev guide (10 min)
- CLAUDE.md — Code standards & team collaboration rules (3 min)
Total reading time: ~20 minutes. Then you code.
These define what to build. Keep these open while coding.
- specs/FEATURES.md — Feature specs, acceptance criteria, time estimates
- specs/DATA_MODEL.md — TypeScript interfaces, database schema, enums
- specs/API.md — REST API contracts with example responses
- specs/UI_SPECS.md — Component specs, color palette, responsive layout
These help you build it right.
- docs/ARCHITECTURE.md — System design, data flow, caching strategy
- docs/INTEGRATIONS.md — Code samples for Jira, Outlook, auth
Read first (5 min):
- QUICK_REF.md — Overview
- PROJECT_PLAN.md — Your phase 1 tasks
Then do:
- Review specs/FEATURES.md with team
- Clarify "overnight" algorithm and priority ranking
- Define the 5 recommended actions (see docs/INTEGRATIONS.md — Aggregation Service)
- Throughout sprint: Validate metrics accuracy
Key files to keep open:
- specs/FEATURES.md
- docs/INTEGRATIONS.md (Aggregation Service section)
Read first (10 min):
- QUICK_REF.md
- specs/DATA_MODEL.md — Database schema & interfaces
- docs/ARCHITECTURE.md — System design
Then do:
- Review database schema with Full Stack Engineer
- Create PostgreSQL schema (users, integration_tokens, overnight_summaries)
- Write TypeScript interfaces (src/types/*.ts) — no
anytypes - Create database migration file
- Throughout sprint: Review service implementations for data consistency
Key files to keep open:
- specs/DATA_MODEL.md
- docs/ARCHITECTURE.md
- SETUP.md — Database Operations
Read first (15 min):
- QUICK_REF.md
- SETUP.md — Environment setup
- specs/API.md — API contracts
- docs/INTEGRATIONS.md — Implementation guide
Then do:
- Set up environment (SETUP.md)
- Create mock Jira service (see docs/INTEGRATIONS.md#mock-data-strategy)
- Create mock Outlook service (see docs/INTEGRATIONS.md#mock-data-strategy)
- Create API routes that use mock services
- Implement aggregation logic (with Product Manager's input)
- Throughout sprint: Wire frontend → backend via mock APIs
Note: Real API integration is post-sprint work. Use mock data to move fast.
Key files to keep open:
- specs/API.md
- specs/DATA_MODEL.md
- docs/INTEGRATIONS.md
Read first (10 min):
- QUICK_REF.md
- specs/UI_SPECS.md — Component specs & design system
Then do:
- Set up Tailwind CSS + theme system
- Create component structure (src/components/)
- Build OvernightSummaryCard (loading, loaded, error states)
- Build KPICard component (all status variants)
- Build KPIGrid (responsive: 1 col mobile → 4 col desktop)
- Implement theme toggle (light/dark)
- Throughout sprint: Ensure responsive design, accessibility
Key files to keep open:
- specs/UI_SPECS.md
- SETUP.md — Project Structure
0:00-0:15 Spec Review & Architecture Alignment
0:15-0:45 Data Model & API Contracts
0:45-1:15 Core Components & Services
1:15-1:30 Integration & Demo Prep
See PROJECT_PLAN.md for detailed breakdown.
- Node.js 18+ installed (
node --version) - PostgreSQL running locally (
psql -U postgres) - NO real API credentials needed (using mock data)
- Git repo cloned
-
.env.localcreated from.env.example(see SETUP.md) -
npm installcompleted - Database created (
createdb morning_command_center_dev) - No TypeScript errors (
npm run type-check)
- Everyone read QUICK_REF.md
- Roles assigned (PM, EA, FSE, UX)
- PROJECT_PLAN.md reviewed
- CLAUDE.md (code standards) acknowledged
As you build, follow this structure (defined in SETUP.md):
src/
├── pages/ # Page components (index.tsx, overnight-summary.tsx)
├── components/ # React components (OvernightSummaryCard, KPICard, etc.)
├── api/ # Backend routes (/api/overnight-summary, etc.)
├── services/ # Business logic (jira-service.ts, outlook-service.ts, aggregation-service.ts)
├── hooks/ # Custom hooks (useOvernightSummary, useDashboard)
├── types/ # TypeScript interfaces (jira.ts, outlook.ts, dashboard.ts)
├── styles/ # CSS + Tailwind theme
└── utils/ # Helpers (timezone.ts, attention-score.ts)
By the end of 90 minutes, you should have:
- OvernightSummaryCard displays real data from Jira + Outlook
- Executive Dashboard shows 4+ KPI cards with live metrics
- Light mode + Dark mode both working
- Responsive design tested on mobile, tablet, desktop
- No TypeScript errors (strict mode)
- No console errors
- Team understands full data flow (Jira → API → Frontend)
See PROJECT_PLAN.md#success-criteria for full list.
You don't need to debate these:
| Decision | Rationale |
|---|---|
| Frontend: React + TypeScript | Type safety, component reusability |
| Styling: Tailwind CSS | Enterprise look, consistent theme system |
| Backend: Node.js + Express (or Next.js) | Fast to implement, integrates well with React |
| Database: PostgreSQL | Reliable, JSONB support for extensibility |
| Auth: OAuth 2.0 | Industry standard for Jira + Outlook |
| Caching: Redis (backend) + localStorage (frontend) | Prevents API rate limiting |
Q: Should we build everything or just MVP?
A: Build MVP in 90 minutes. Use QUICK_REF.md#definition-of-done as your checklist.
Q: What if we get stuck on Jira/Outlook API?
A: Use mock data. Swap real API after sprint. See docs/INTEGRATIONS.md — Testing.
Q: Do we need 100% test coverage?
A: No. Focus on critical paths (aggregation logic, API endpoints). See CLAUDE.md.
Q: How do we handle design decisions?
A: Product Manager or UX Architect decides immediately (< 2 min). No debate. See PROJECT_PLAN.md — Comm & Escalation.
Q: What if we finish early?
A: Stretch goals: PROJECT_PLAN.md#stretch-goals.
| Blocker | Solution |
|---|---|
| Jira API credentials missing | Take 5 min to get them (1 person only) |
| DB connection failing | Verify PostgreSQL running, reset connection |
| Node modules not installing | Try npm ci, then npm install |
| Port 3000 in use | Kill process: lsof -ti :3000 | xargs kill -9 |
| TypeScript compilation errors | Run npm run type-check to see all at once |
See SETUP.md — Troubleshooting for full list.
- Check the spec — Most questions answered in specs/ or docs/
- Ask the team — Use a dedicated Slack/Discord channel
- Escalate to role owner — PM/EA/FSE/UX make decisions fast
No async discussions. Decisions must happen in < 2 minutes.
- ✅ Everyone has access to this repo
- ✅ Everyone read QUICK_REF.md (2 min)
- ✅ Everyone checked Prerequisites
- ✅ Roles assigned (PM, EA, FSE, UX)
- ✅ Timer started (90 min from now)
- QUICK_REF.md — One-page sprint guide
- GETTING_STARTED.md — This file
- PROJECT_PLAN.md — 90-minute timeline
- CLAUDE.md — Code standards & team rules
- SETUP.md — Dev environment setup
- specs/FEATURES.md — What to build
- specs/DATA_MODEL.md — Database & types
- specs/API.md — REST endpoints & contracts
- specs/UI_SPECS.md — Component design
- docs/ARCHITECTURE.md — System design
- docs/INTEGRATIONS.md — Code samples
- README.md — Project overview
Last Updated: July 30, 2025
Status: Ready to sprint
Duration: 90 minutes
Let's build something great! 🚀