Project poster
The Project Poster is the Project Poster tab for every project. It gives you one page to capture what the project is about, who is involved, and what might go wrong — without navigating between tabs.
What is on the poster
The poster is organized into collapsible sections:
Each section remembers whether you collapsed or expanded it, so the poster stays configured the way you prefer.
Problem and solution
The Problem and Solution sections are rich-text fields that support markdown and Mermaid diagrams. Use them to document the high-level context of your project:
- Problem — describe the pain point, user need, or business opportunity. This is the project’s own spec.
- Solution — describe your approach, key decisions, and design. This is the project’s own design doc.
Both have inline editing — click to start writing, then click away to save. You can embed diagrams (sequence diagrams, flowcharts, state machines) directly in the content.
Risk registry
Risks track what might go wrong and what you plan to do about it. Each risk has:
Add a risk
Type a title in the “Add risk…” field at the bottom of the Risk registry section. Set the likelihood and impact with the quick-select buttons (HL, ML, LL for likelihood; HI, MI, LI for impact). Press Enter to create.
Manage risks
Click a risk row to expand its detail form. Edit any field inline — changes save on blur. Risks sort by score automatically (highest first), so the most critical risks stay at the top.
Stakeholder map
Stakeholders are people with an interest in the project’s outcome. The stakeholder map tracks who they are and how to engage them. Each stakeholder has:
Add a stakeholder
Click “Add stakeholder” at the bottom of the section. A dropdown shows team members not yet assigned. Select a person to add them with default settings, then expand the row to set their role, influence, and communication preferences.
References
References link your project to external resources. Supported types:
| Type | Auto-detected from URL |
|---|---|
| Figma | URLs containing figma.com |
| Notion | URLs containing notion. |
| Repo | URLs containing github.com |
| Doc | General documentation links |
| External | Anything else |
Add a reference
Type a URL in the reference field (the https:// prefix is shown automatically). Press Enter, then type a label for the link and press Enter again to save. The type is auto-detected from the URL but you can change it by clicking the type badge.
Edit references
Double-click a reference label to edit it inline. Click the type badge to change the type. Hover to reveal the delete button.
Use the poster with Claude Code
Claude Code can read and update the poster through natural language. Reading the poster calls plenar_get_project_poster, which returns the full summary including every section.
"Add a risk: third-party API rate limits might block our sync feature.
Set likelihood to medium and impact to high."
That calls plenar_add_risk with the title, likelihood, and impact.
"Add Elena Petrova as a stakeholder — she's accountable for the project,
high influence, and wants weekly updates via Slack."
That calls plenar_add_stakeholder with the person, RACI role, influence, and communication preferences.
"Add a reference to our design file: https://figma.com/file/abc123"
That calls plenar_add_reference; the type is auto-detected from the URL.
"Update the project problem statement to describe the new onboarding pain point."
The Problem field maps to plenar_update_spec and the Solution field to plenar_update_design_doc.
Common questions
Who can I add as a stakeholder? Any member of the project’s team. The dropdown lists members not already on the stakeholder map, so each person appears once.
Why is one risk above another? Risks sort by score — likelihood × impact, from 1 to 9. The highest-scoring risks stay at the top so the most critical ones are always in view.
Can I put diagrams in the Problem and Solution sections? Yes. Both are rich-text fields that render Mermaid, so you can embed sequence diagrams, flowcharts, and state machines inline.
Do poster edits change the schedule? No. The poster captures context — problem, risks, stakeholders, references. It doesn’t move tasks or recompute the plan.
What to do next
- Goals and milestones — structure the outcomes the poster’s Goals section summarizes.
- Goal health — how the health shown next to each goal is computed.
- Knowledge base — capture cross-cutting context that outlives a single project.
- Reports — turn the plan into a shareable summary for stakeholders.