TasksCAN I VIBECODE
Confluence?
BUILD FIRST
- A non-sensitive or read-only version of the core experience
- A manual review step wherever correctness or trust matters
- A narrow companion tool that removes a real piece of work
LEAVE FOR LATER
- Regulated decisions, payments, or irreversible actions
- Claims of correctness, compliance, or uptime that the MVP cannot support
- Sensitive integrations until security, support, and auditability are ready
RESEARCH NOTES
What this tool actually does.
Confluence is Atlassian's team workspace for knowledge management and project collaboration. Core primitives are Spaces (workspaces for organizing related content), Pages (living documents nested in a hierarchical page tree), and Blogs (for announcements). It offers real-time co-editing, inline and page-level comments, @-mentions, likes, emoji reactions, and page sharing. Customizable templates cover meeting notes, project plans, and PRDs. Recent additions include whiteboards (infinite-canvas real-time brainstorming with sticky notes/shapes/connectors), embedded databases with table/card/board layouts, screen recording, Jira integration, and AI-powered search. Task management is not its primary purpose; teams typically embed assignments, due dates, and action items within pages and meeting notes, relying on page structure and comments rather than a dedicated task list.
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a team knowledge workspace called 'TeamPages' that reproduces the core Confluence workflow: teams create Spaces, author hierarchically nested Pages, and collaborate through comments, mentions, and inline task assignments embedded in the document body. The app must support real-time collaborative editing of rich-text Markdown documents, a sidebar page tree per Space, full-text and label-based search, and an activity feed showing recent edits and comments. Users must be able to highlight any sentence in a page and attach a checklist item with an assignee (@mention) and optional due date; these inline tasks must aggregate into a per-user 'My Tasks' view that links back to the source page. Additional requirements: page version history with diff view, read/write permissions per Space, public share links, and a WYSIWYG editor (suggest TipTap or Slate for collaborative editing, or Yjs + Markdown for simplicity). Styling must be original — do not copy Atlassian branding, logos, or visual design. Out of scope: Jira integration, whiteboards/canvas, databases, blogs, AI features, screen recording. Deliver a functional MVP with a README documenting setup steps, architecture choices, and known limitations (e.g., no offline support, no mobile app, single-server deployment).