orfc

Your AI agent writes the plan.

Your team reviews it. You iterate.

Share any markdown — architecture docs, implementation plans, RFCs — collect inline feedback, edit in-browser, and track every revision with built-in version history.

Install

$ npm install -g @orfc/cli

$ orfc login

✓ Authenticated

$ orfc push plan.md

✓ Published → https://orfc.dev/p/xK7mQ2

$ orfc pull xK7mQ2

✓ 3 comments pulled → feedback.md

$ orfc edit xK7mQ2

✓ Updated → https://orfc.dev/p/xK7mQ2 (v2)

Works with

Any tool that generates markdown plans

Cursor

Claude Code

Windsurf

Any terminal

How it works

Your agent generates a plan. Or write one yourself.

Push it. Share the link with your team for review.

Pull feedback. Let your agent iterate. Ship with confidence.

Documentation

Getting started

Install the CLI globally, then authenticate once with your email.

$ npm install -g @orfc/cli

$ orfc login

✓ Authenticated as you@company.com

Your API key is saved to ~/.orfc/config.json. You only need to log in once.

Publishing a plan

Push any markdown file to get a shareable link. The title is auto-detected from the first # heading.

$ orfc push plan.md

✓ Published → https://orfc.dev/p/xK7mQ2

# link copied to clipboard, browser opens automatically

You can also pipe from stdin, set a custom title, or update an existing plan:

$ cat plan.md | orfc push

$ orfc push plan.md --title "Q2 Architecture"

$ orfc push plan.md --update xK7mQ2 # update existing

$ orfc push plan.md --expires 7d # auto-expire in 7 days

Access control

By default, plans require sign-in to view. You can make them public or restrict to specific people.

Authenticated (default)

Anyone with a valid email sign-in can view the plan.

$ orfc push plan.md

Public

Anyone with the link can view, no sign-in required.

$ orfc push plan.md --access anyone

Domain-restricted

Only people with matching email domains can view. The author always has access.

$ orfc push plan.md --viewers "@company.com"

$ orfc push plan.md --viewers "alice@co.com,bob@co.com"

Notifying reviewers

Send an email to reviewers when you publish, so they know to review.

$ orfc push plan.md --to reviewer@company.com

$ orfc push plan.md --to "alice@co.com,bob@co.com"

Reviewing feedback

Reviewers open the link in their browser, highlight text, and leave inline comments. You can pull those comments back into your markdown.

$ orfc pull xK7mQ2

<!-- [COMMENT by reviewer@co.com]

On: "the specific text they highlighted"

> Their feedback here

-->

Pipe to a file for easy revision:

$ orfc pull xK7mQ2 > feedback.md

$ orfc comments xK7mQ2 # view comments in terminal

Managing plans

$ orfc list # list all your published plans

$ orfc open xK7mQ2 # open in browser

$ orfc delete xK7mQ2 # permanently delete

Editing & version history

Edit plans directly in the browser or from your terminal. Every update automatically preserves the previous version.

Web editing

Plan authors see an Edit button on their documents. Click to switch to a markdown editor with live preview. Cmd+S to save.

CLI editing

Pull, edit in your terminal editor, and push back in one command.

$ orfc edit xK7mQ2 # opens in $EDITOR

Version history

Click History on any plan to see all previous versions with diffs. Every update — from the web, CLI, or an AI agent — is tracked.

AI agent workflow

AI agents (Cursor, Claude Code, Windsurf) can use orfc to share implementation plans for human review before executing. This is the typical flow:

Agent generates a markdown plan for the implementation

Agent publishes and notifies the reviewer

orfc push plan.md --viewers "@company.com" --to you@company.com

Human reviews on orfc.dev, leaves inline comments on specific sections

Agent pulls feedback and reads inline comments

orfc pull xK7mQ2 > feedback.md

Agent addresses each comment, revises the plan, and re-publishes

Agent updates the existing plan with revisions

orfc push plan.md --update xK7mQ2

Agent prompt

Copy this prompt into Cursor rules, Claude Code CLAUDE.md, or any AI agent's system instructions to enable the orfc workflow.

## orfc — plan review workflow Before implementing any non-trivial task, publish your plan for human review using orfc. ### Setup (one-time) npm install -g @orfc/cli orfc login ### Workflow 1. Write your implementation plan as a markdown file (plan.md) 2. Publish it for review: orfc push plan.md --viewers "@company.com" --to reviewer@company.com 3. Wait for the reviewer to leave inline comments on orfc.dev 4. Pull the feedback: orfc pull <slug> > feedback.md 5. Read the comments, address each one, revise your plan 6. Re-publish the updated plan: orfc push plan.md --update <slug> 7. Repeat until approved, then implement ### Key flags --access anyone # make public (no sign-in required) --viewers "@domain.com" # restrict to a domain --to "a@co.com,b@co.com" # email reviewers --update <slug> # update existing plan --title "My Plan" # custom title ### Commands orfc push <file> # publish a plan orfc pull <slug> # pull plan with inline comments orfc edit <slug> # pull, edit in $EDITOR, push back orfc comments <slug> # view comments orfc list # list your plans orfc --help # full usage ### Version history Every --update automatically preserves the previous version. Reviewers can view all past versions and diffs on the web.

Configuration

Config is stored at ~/.orfc/config.json. Set defaults so you don't have to repeat flags.

$ orfc config show

$ orfc config set defaultAccess anyone

$ orfc config set defaultExpiry 7d

$ orfc config set slackWebhook https://hooks.slack.com/...

CLI reference

Command	Description
orfc login	Authenticate via browser
orfc push <file>	Publish a markdown file
orfc pull <slug>	Pull plan with inline comments
orfc comments <slug>	View comments in terminal
orfc list	List all your plans
orfc open <slug>	Open plan in browser
orfc edit <slug>	Pull, edit in $EDITOR, push back
orfc delete <slug>	Delete a plan permanently
orfc config <action>	View or modify config