Planning Dashboard

The dashboard is your per-project command center. What it shows depends on where the project is in its lifecycle — it has three distinct modes.

Accessing the Dashboard

Click Dashboard in the sidebar's Project section (it's the first item once your project has moved past onboarding).

Dashboard Modes

Trinity picks the mode automatically based on the project's phase.

Imported mode

Shown for projects you imported from an existing codebase, before you've created your first PRD. Presents three doorways into the planning flow:

  • Architect — jump straight into conversational PRD planning
  • Audit first — scan the codebase before deciding what to change (findings can feed directly into the first PRD)
  • Align first — clarify priorities and sharpen the roadmap before writing PRDs

All three paths eventually run through Architect, which mints your first PRD and the first release. A small note under the doorways links out to Release defaults in project settings so you can set tag_template / bump_strategy before the first release is auto-created.

Planning mode

Shown for greenfield projects whose roadmap is being generated and reviewed. Contains:

  • Roadmap status cards — one card per section (Vision, Phases, Milestones, Architecture, Design System). Completed sections turn green and link to the draft knowledge page; unfinished sections show a "needs content" badge.
  • Planning checklist — step-by-step: set up roadmap → review each section → (optional) align roadmap → generate PRD
  • AI Usage card — live counts of AI calls + input/output tokens while you're generating
  • Generate PRD CTA — the primary action. Disabled until every roadmap section has content.

Executing mode

Shown once the first PRD exists. This is the "normal" dashboard. At the top:

  • Release title + description — the active release's name, description/version
  • Release selector (top right) — switches between the project's releases. Selection is persisted per-user via the sync DB, so you land back on the last release you worked with across devices.

Four stats cards:

  • Total Stories — count + how many remaining
  • Completed — merged count + % complete
  • Tokens Used — total input + output tokens spent on the release
  • Total Time — total AI duration + counts of stories completed / PR'd / merged

Followed by paired cards:

  • Live Execution — workers and current pipeline activity
  • Active Releases — other releases running in parallel
  • Phase Progress — progress bar per phase, click-through to filter the stories list
  • Current Work — the story the coordinator is running right now (plus the last one finished)
  • Blocked Stories — stories waiting on unmet dependencies or unmerged complete stories
  • Activity Feed — recent project events

No-plan empty state

When you have a project but no PRDs (and therefore no releases), the dashboard shows a No plan yet panel with two buttons: Open Architect (starts the first PRD) and Release defaults (jump to project settings to tweak tag_template + bump_strategy before the first release is minted).

Generate PRD

From the Planning dashboard's Generate PRD button, Trinity launches the 5-phase planning pipeline:

  1. Architect — designs the phase and epic structure with rationale
  2. Story Writer — writes individual stories with acceptance criteria
  3. Dependency Mapper — populates depends_on and places quality checkpoints
  4. Target Mapper — assigns each story to the right project targets (web, api, mobile, etc.)
  5. Calibrator — calibrates difficulty and surface-area ratings comparatively

While it runs, the dashboard shows a live phase indicator (current phase highlighted, completed ones green, pending ones dimmed). The sidebar task indicator also reflects progress. You can navigate away safely — you'll be notified when it finishes.

PRDs and Releases

Trinity is release-first: every PRD belongs to exactly one release (prds.release_id). The dashboard is release-scoped — switching releases in the selector re-scopes the cards to that release's stories.

  • Multiple PRDs can live inside a single release as your plan grows
  • Architect proposes a release for each new PRD (existing unshipped one, or a brand-new one) — you can override before saving
  • Multiple releases can execute simultaneously; each release gets its own coordinator instance (see Releases)

Cross-PRD Story Dependencies

Stories can depend on stories from other PRDs using the prdSeq:phase.epic.story format — for example 1:1.2.1 means "story 1.2.1 from PRD 1". This works within the same release (typical) or across releases (advanced — in that case the upstream release should be shipped before the downstream one).

  • Architect — add features, modify stories, or create new PRDs conversationally
  • Align — health check (pre-PRD roadmap alignment or post-PRD drift detection)
  • Audit — on-demand codebase scan
  • Dependency Graph — the visual story-dependency view (lives on its own /graph page, not the dashboard)
  • Releases — create releases, wire dependencies, ship