Skip to content
PlanBridge

Precision feedback on a file

/planbridge-open docs/spec.md

The file opens in your browser for inline annotation. Your comments come back to the agent on stdout.

This is the on-demand sibling to the automatic plan-mode hook. The hook fires when your agent finishes planning. planbridge-open fires whenever you ask for it.

When to use it

Section titled “When to use it”
  • You want inline comments on a design doc, RFC, or spec.
  • Your agent uses a workflow that bypasses plan mode. For example, the obra/superpowers plugin never enters Claude Code’s plan mode. You can still use PlanBridge with it. See the Superpowers recipe for details.
  • You want to redirect the agent before it starts work, and the relevant context lives in a file rather than in plan mode.

To mark up the answer your agent just wrote instead of a file on disk, use Annotate the last message.

Agent skill

Section titled “Agent skill”

Use planbridge-open for files:

/planbridge-open path/to/file.md

You can also describe the file in plain language and your agent resolves it:

/planbridge-open the design doc we drafted yesterday

The planbridge-open skill ships with the planbridge@contextbridge Claude plugin.

Claude Code may display plugin skills as /planbridge:planbridge-open. Use that form if it appears in your slash-command picker.

What you see

Section titled “What you see”
  1. Your agent resolves the argument and runs contextbridge open.
  2. PlanBridge opens the file in your browser.
  3. You leave inline annotations and general comments, then submit or approve.
  4. PlanBridge writes a markdown summary of your feedback to stdout.
  5. Your agent reads the summary and responds conversationally.

The output is feedback for discussion, not a directive. The agent treats your comments the way it would treat a colleague’s review notes, not a checklist to silently execute.

Direct CLI use

Section titled “Direct CLI use”

The skill is a thin wrapper around contextbridge open. You can run the binary yourself from any harness:

terminal
contextbridge open path/to/file.md

Or pipe content via stdin (useful when the document lives in conversation rather than on disk):

terminal
printf "%s" "$content" | contextbridge open

Full flags and exit codes live in the CLI reference.

Limitations

Section titled “Limitations”

open takes a single markdown file or a single piped document. Folders, URLs, HTML, and multi-file sessions are not supported in this release.