The project detail page (Documentation Index
Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
Use this file to discover all available pages before exploring further.
/projects/:id) is split into two columns: a left content area with the timeline and signals, and a right rail of cards covering status, rollup, integrations, people, and post-release monitoring.
Header
- Title — click to edit
- Description — appears below the title; click to edit
- Stage stepper — horizontal progress bar showing the project lifecycle. Past stages get checkmarks, the current stage is highlighted, future stages are muted. Click any stage to jump. If the AI thinks you should advance (e.g., the PR merged), a green “suggested” pulse appears on that stage.
Left Column
Two tabs:- Signals (N) — every signal attached to this project, with sentiment, source, person, company, and a quick unattach button.
- Timeline (N) — a chronological event log: PRs merged, statuses advanced, scope updated, comments added, signals attached, integration links created. Each event shows the action type, metadata, and a time-ago label.
Right Rail Cards
Cards appear in roughly priority order. Some are conditional on the project’s stage or state.Status at a Glance
The bottleneck card. Answers “what’s blocking us and what’s next?”- Waiting on — e.g., “Waiting on @ian for 3d — PR #4521 review”. Severity pill (normal / warning / stalled) plus a one-click action button.
- Blockers — manually entered or AI-suggested environmental issues (not “waiting on people”), distinct from the Waiting On section.
- Next actions — checklist of what happens next. Manually added or AI-suggested. Real projects show “done” checkmarks as they complete.
Project Rollup
An AI-generated synthesis of the project, with sections for What / Why / Who / How / Risks / Next actions. Rendered as a two-column grid with:- Copy — one-click clipboard
- Refresh — regenerate from latest evidence
- Header: “Approved evidence only · [generated timestamp]”
Integration Issues
Shows attached Linear and Jira tickets. The ”+” button searches both providers in parallel; click a result row to attach.Agent Sessions
Recent auto-routing decisions. Each row shows confidence score and the reason the agent chose this project (e.g., “Routed to Engineering — technical signals + Linear ticket match”).People & Signals
Two tabs in one card.- People — companies sorted by ARR or mention count (logo, name, ARR, mention count), then individual people (name, company, signal count).
- Signals — flat list of attached signals with sentiment, person/company, and an unattach button.
Post-Release Monitor
Only appears when the project is in the Released stage.- Days since release
- Post-release signal count broken down by sentiment (positive / neutral / negative)
- Regression alerts (info / warning / critical) when the monitoring agent detects spikes in negative signals or support mentions
Close the Loop
Two parts:- Checklist — one row per linked contact: person name, their company, current reply state, and a “done” checkbox.
- Composer — draft a Slack or email update to send to the linked people. One-click Send to Slack or Email per contact.
Similar Projects
Surfaces up to 3 high-similarity duplicate candidates with a match %. Each row has a Merge button that collapses the candidate into the current project — moves all its signals over and archives the duplicate. The × button dismisses the banner for the session.Suggested Signals
Auto-fires when a project has fewer than 5 attached signals and the title is long enough to be a useful search query. Shows up to 5 semantic matches with:- Match %
- Signal summary
- Person/company
- Boundary tag (Customer / Internal)