Skip to content
Project Planner

Documentation

Getting started

The first session in Project Planner is designed to produce a real project model — not a blank canvas. This is the planned flow for the Windows application.

Documentation describes the planned Windows application. Interface examples use demo project content and are labelled as previews.

What you need

  • Windows 11, 64-bit (Windows 10 21H2+ is a legacy target).
  • A folder for the project. Planning files live beside application source, never inside it.
  • Optionally, Git and an AI provider account. Neither is required to inspect or edit a project locally.

Create a project

File → New Project asks for a name, description, type (web, desktop, mobile, API, AI application, SaaS, library or other), target platforms and an optional stack. Project Planner then writes two things at the chosen location:

  1. A .pp identity file in the project root. See Project identity.
  2. A project-planner/ directory with canonical sections for requirements, architecture, agents, development, security, testing, decisions and the blueprint.

If you open an existing folder that already has a .pp file, Project Planner loads that identity and does not create a second one.

Describe the idea

The Overview screen starts with the description you typed. The Product Planner and Requirements Analyst can propose a first set of phases and candidate requirements. Every proposal is a draft until you accept it. Nothing is written into the plan automatically.

Work through the lifecycle

  1. Accept, edit or reject proposed requirements. Each one gets a stable ID such as REQ-001.
  2. Turn accepted requirements into phases, milestones, tasks and subtasks.
  3. Add architecture components and the data that moves between them.
  4. Open the System Map and Data Flow screens — they are generated from that data, not drawn by hand.
  5. Assign agents, skills and MCP servers if you want AI assistance. Configure a provider first if you want model-backed runs.
  6. Run audits. Findings carry evidence, severity and a recommendation.
  7. Generate the blueprint and export it as Markdown, JSON, HTML or PDF.

Where to go next

  • How it works — the ten-step product walkthrough.
  • Workspace — Overview, requirements and planning.
  • Download — preview status for the Windows installer.

Something missing? Send feedback.

Feedback