A structured workspace for turning ideas into development-ready projects.
Project Planner connects requirements, architecture, AI agents, development planning, testing and documentation in one workspace — so you understand what you are building, why, and what could go wrong, before implementation begins.
No installer is available yet. Interface previews on this site show demo project content.
Atlas Field Service
Mobile-first work-order management for field technicians with offline sync and AI-assisted scheduling.
Progress
8
Requirements
10
Tasks
15
Components
10
Flow nodes
19
Agents
8
Artifacts
5
Decisions
6
Open findings
Health
Activity
The Overview screen: project summary, progress, health and activity in a single command centre.
One connected lifecycle
Requirements with stable IDs, priorities, sources and acceptance criteria — functional, security, accessibility, performance and business.
Architecture components, dependencies and data flow as interactive graphs generated from the project itself, never from a static picture.
Nineteen specialised agents in five groups, each with a role, tools, skills, MCP connections, memory scope and permissions.
Phases, milestones, tasks and subtasks with dependencies and estimates, traceable back to the requirement that motivated them.
Evidence-based audits across security, privacy, dependencies, accessibility, performance and documentation gaps.
A blueprint, presentation outline and export package generated from the live project — Markdown, JSON, HTML and PDF.
Interface preview
Every component, its technology, dependencies and owner — rendered as a navigable system map generated from project data.
Learn more →See how data moves between users, interfaces, services, AI providers and storage, with classification and encryption on every edge.
Learn more →A live view of which agents are running, waiting or queued, what they are doing right now and what they produced.
Learn more →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 |
| 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 |
Phases, milestones, tasks and subtasks with estimates, acceptance criteria and links back to requirements.
Learn more →Evidence-based findings across security, accessibility, dependencies, performance and documentation.
Learn more →0
Critical1
High4
Medium1
Low1
Resolved| Ref | Category | Finding | Severity | Status | Component |
|---|---|---|---|---|---|
| AUD-001 | Security | Route proposals include customer names in the prompt | High | Open | CMP-007 |
| AUD-002 | Architecture | Notification worker has no dead-letter handling | Medium | Open | CMP-013 |
| AUD-003 | Requirements | REQ-006 has no acceptance criteria or linked tasks | Medium | Open | — |
| AUD-004 | Dependencies | Two HTTP clients declared across packages | Low | Acknowledged | CMP-005 |
| AUD-005 | Accessibility | Status conveyed by colour only in the dispatcher map legend | High | Resolved | CMP-002 |
15 components across 9 sections. 2 implemented, 5 in progress, 8 planned.
One generated document that explains the whole project — purpose, requirements, architecture, agents, tests and decisions.
Learn more →Built for Windows developers
Open a project folder, read its .pp identity file and keep planning documentation next to the code without uploading it.
OpenAI, Anthropic, Google, DeepSeek or compatible endpoints through one abstraction, with fallbacks and cost tracking.
Connect MCP servers and reusable skills, then assign them to the agents that need them — with per-server permissions.
API keys live in secure storage, never in prompts, logs, activity feeds or exports.
What this website shows
Preview release coming soon. Free plan available at launch.