Shared project context

The project brief,
connected to the work.

prd.works puts versioned Markdown, document discussions, and project tasks in one workspace. Your team uses the browser. Coding agents read and update it through the CLI.

Start with prd.works Explore the interface

Two collaborators, one shared briefInteractive walkthrough / sample project

PRDIn progress

Team invitations

Let workspace owners invite collaborators by email, with access scoped to their project.

Jamie / revision 12

Acceptance criteria

Owners can invite an editor or viewer.
Invitation links expire automatically.
Expired links show a clear recovery action.

Access rules

Only the invited account can accept a link. Accepting adds the account to the workspace with the assigned role.

All changes saved Saved v12

01 / 09Two people, one briefJamie + Mina

Jamie opens the requirements while Mina checks the recovery flow.

One example, three contributors.

Illustrated workflow with sample data. Edits are saved as document revisions; discussions stay attached to the brief.

A brief the agent can read

Keep requirements in Markdown. Read the same document from the web or CLI, without maintaining a separate prompt copy.

Updates you can trace

Document revisions record an author and version. Discussions stay on the document that prompted them.

Progress before the commit

Track phases and tasks directly. An agent can report a blocker while implementation is still in progress.

Browser + terminal

The same document, from either side.

Review the brief in the browser. Read its Markdown in a coding session. Both interfaces use the same project documents and task state.

Document: Versioned Markdown
Work: Phases, tasks, progress
Access: Scoped workspace credentials

Technical plan.mdSaved / v12

Workspace invitations

Issue scoped invitation links. Validate the recipient and expiry before granting project access.

API contract agreed
Release workflow ready
Review final copy

Terminalzsh

$ prdworks docs read DOCUMENT_ID --raw

# Workspace invitations
Issue scoped invitation links…

$ prdworks work list

[ { "title": "API contract", "status": "Done" }, … ]

Same workspace / document + work API

Same workspace

The agent interface

A small CLI for the whole handoff.

Run commands from your linked repository. Read commands return structured JSON by default; --raw returns Markdown.

OperationCommandWhat it does

Read

prdworks docs read DOCUMENT_ID --raw

Get the canonical Markdown, ready to use in a coding session or write to a local file.

Update

prdworks docs update DOCUMENT_ID \
  --file brief.md --expected-version 12

Write against the revision you read. A stale version returns a conflict so a newer edit is not silently overwritten.

Discuss

prdworks discuss list DOCUMENT_ID --relay-agents

Fetch discussion messages flagged for agents. Reply on the same document to keep the decision with its context.

Report

prdworks work status TASK_ID 'Done'

Update a task as work happens. Progress does not have to wait for a commit or pull request.

Concurrent document updates

A person saves v13 while an agent is working from v12.

expected_version: 12409 ConflictRe-read, reconcile, save

Inside the workspace

Documents, work, and access.

A shared API connects the web client and CLI. The project link lives in your repo; credentials live on your machine.

What a workspace contains

Documents: PRD / TRD / Plan / Note
Markdown content, status, version
Revisions: Saved document snapshots
Author and timestamp
Discussions: Comments attached to a document
Resolution and agent relay flags
Work items: Phases with child tasks
Planned / In progress / Blocked / Done

How a repository connects

prdworks login

Save a credential locally, outside the repository.

prdworks link

Select an accessible workspace. Write a credential-free prd-works.toml in the repository.

prdworks docs list

Work from the repo or its child directories. Agent tokens are scoped to a workspace and subject to membership permissions.

Sync and collaboration behavior

Document saves are versioned. Connected clients receive refresh events. Concurrent keystrokes are not merged; conflicting drafts need reconciliation.

Agent relay is pull-based. A relay flag makes a comment discoverable through the CLI. It does not start an agent or push into an active coding session.

Task status is independent of Git. Work updates appear in the workspace. Task status uses the last submitted change.

Get started

Connect your next coding session.

Install the CLI, sign in, and link your repository to a workspace.

Start now Explore the sample workspace

curl -fsSL https://prd.works/install.sh | sh

Standalone binary for x64 or ARM64. No Node.js required. Verifies SHA-256 before installing.