Build your own Asana.

# Build an original app inspired by Asana

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original team project planner called Workpath, inspired by Asana. It is for a small team coordinating tasks with owners, dates, and a few dependencies. The main journey is creating a project, assigning work, connecting a blocker, and completing tasks while seeing board/list/timeline views stay consistent. Keep one organization and explicit permissions.

## Design
Create an original calm project workspace with project navigation, switchable list/board/timeline views, and a task detail panel. Expose owner, due date, completion, dependency, and unsaved state clearly. Timeline controls need accessible date editing rather than drag-only interaction.

## Features
1. Projects and membership: create a project, invite workspace members through authenticated membership, set project visibility, and prevent unauthorized changes to private projects.

2. Tasks and subtasks: create/edit tasks, assign one owner, set due dates and sections, add a bounded set of subtasks, and complete/archive work. Search and filter by assignee, status, and due date.

3. Consistent views: show list, section-based board, and a simple date-range timeline from the same task records. Reordering or rescheduling must update all views and survive a reload.

4. Dependencies: link blocker tasks, detect cycles, show blocked status, and recalculate it when a blocker completes or reopens. Do not silently shift every downstream date unless that behavior is explicitly implemented.

5. Collaboration and overview: add task comments, record changes, notify assignees in-app, and derive project progress from actual completed work. Export authorized tasks as CSV.

## Tech stack
Use a TypeScript app/API with PostgreSQL and authenticated workspace/project roles. Store dependencies as directed edges, validate cycles transactionally, and version task updates for concurrency. Use a lightweight timeline rendering approach and plain-date fields for due dates to avoid accidental timezone shifts.

## Data & behavior
Workspace; Member; Project; ProjectMember; Section; Task {projectId, parentId, assigneeId, startDate, dueDate, completedAt, position, revision}; Dependency {blockedTaskId, blockerTaskId}; Comment; TaskEvent; Notification. Compute progress and blocked status from persisted records.

Acceptance checks and scope:
Test task creation through all three views, a dependency cycle, reopened blockers, date boundaries, simultaneous updates, private-project search/export denial, and real progress after completion. Exclude automated workflow builders, email integrations, portfolios, billing, and enterprise resource management.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.