How it works
Project Planner guides a project through a fixed sequence of phases, but never locks you in: you can revisit any step, and every change is traced to the requirement, task or decision it affects.
Start from a name, description and project type (web, desktop, mobile, API, AI application, SaaS, library). Choose target platforms, stack, database and where the project lives on disk. Project Planner writes a .pp identity file and a project-planner/ documentation directory next to your source.
Write the idea in plain language. The Product Planner and Requirements Analyst agents propose scope, phases and candidate requirements — every proposal is reviewed by you before it becomes part of the project.
Requirements get stable IDs (REQ-001…), a kind, priority, status, source and acceptance criteria. Dependencies between requirements are explicit, and each one links forward to tasks, components and the agent responsible.
| Ref | Requirement | Kind | Priority | Status | Tasks |
|---|---|---|---|---|---|
| REQ-001 | Technicians can view assigned work orders offline | Functional | Critical | Accepted | TSK-004, TSK-007 |
| REQ-002 | Dispatchers assign and reschedule jobs on a map | Functional | High | Accepted | TSK-005 |
| REQ-003 | AI suggests optimal daily routes per technician | Functional | High | Proposed | TSK-009 |
| REQ-004 | All customer data encrypted at rest and in transit | Security | Critical | Accepted | TSK-003 |
| REQ-005 | Sync conflicts are resolved without data loss | Technical | Critical | Accepted | TSK-007 |
| REQ-006 | Work-order list renders in under 200 ms for 5k items | Performance | Medium | Draft | — |
| REQ-007 | Mobile UI meets WCAG 2.2 AA | Accessibility | High | Accepted | TSK-006 |
| REQ-008 | Customers receive arrival notifications | User | Medium | Proposed | TSK-010 |
Phases contain milestones; milestones contain tasks and subtasks with estimates, dependencies and acceptance criteria. Progress on the Overview is computed from this plan, never typed in.
| Ref | Task | Status | Priority | Agent | Est. |
|---|---|---|---|---|---|
| TSK-001 | Set up monorepo, CI and environments | Complete | High | Software Architect | 6h |
| TSK-002 | Design PostgreSQL schema for work orders and sync log | Complete | Critical | Database Engineer | 10h |
| TSK-003 | Implement field-level encryption for customer PII | In progress | Critical | Security Agent | 12h |
| Ref | Task | Status | Priority | Agent | Est. |
|---|---|---|---|---|---|
| TSK-004 | Build offline work-order store (SQLite) in the mobile app | In progress | Critical | Frontend Engineer | 16h |
| TSK-006 | Accessibility review of mobile navigation | Review | High | Accessibility Reviewer | 4h |
| TSK-007 | Conflict-resolution strategy for sync (last-writer-wins + merge log) | Blocked | Critical | Backend Engineer | 14h |
| TSK-008 | Sync API: delta endpoints with cursor pagination | Ready | Critical | API Engineer | 12h |
Describe components across frontend, backend, database, APIs, authentication, storage, AI, external services, infrastructure, deployment and security. Each component has a type, technology, inputs, outputs, dependencies, owner agent and status.
The System Map and Data Flow screens are generated from those components and flows. Zoom, pan, filter by view, select a node and inspect its dependencies, related requirements and tasks in the inspector.
Nineteen agents in five groups come pre-configured. Assign skills and MCP servers, pick a provider and model per agent, and decide what memory each agent may read. Agent runs are recorded with tool calls, artifacts and warnings.
Running
Waiting
Queued
Completed
| Agent | Task | Status | Current step | Progress | Elapsed | Tools |
|---|---|---|---|---|---|---|
| Frontend Engineer | TSK-004 Offline work-order store | Running | Drafting sync-state machine for pending changes | 62% | 4m 12s | 7 |
| Security Agent | Data-flow review (REQ-004) | Running | Checking classification of edges leaving the tenant boundary | 35% | 2m 03s | 3 |
| Accessibility Reviewer | TSK-006 Mobile navigation review | Running | Evaluating focus order on the work-order list | 81% | 9m 48s | 12 |
| Backend Engineer | TSK-007 Conflict-resolution strategy | Waiting | Question: prefer last-writer-wins for signatures, or block and ask the technician? | 40% | — | 5 |
The Development section detects your environment (Node, Python, Git, Docker, WSL, editors), shows Git status and history, offers a terminal workspace and tracks tests and builds — so the plan meets the machine it will be built on.
Testing plans are derived from acceptance criteria. Audits check requirements, architecture, security, accessibility, dependencies, performance, documentation, privacy, compliance and deployment, each finding carrying evidence, severity and a recommendation.
Generate the blueprint, presentation outline and export package from live data as Markdown, JSON, HTML or PDF. Decisions, versions and relationships are preserved so another team — or another tool — can pick up exactly where you left off.
Why use Project Planner?
Turn a rough idea into a plan you can actually execute, with an AI workforce that proposes rather than decides.
Share one traceable model of requirements, architecture and tasks instead of five disconnected documents.
The .pp identity file and planning directory tell any coding assistant what the project is, how it is structured and what rules apply — before it writes a line.
15 components across 9 sections. 2 implemented, 5 in progress, 8 planned.