Annotate specifications with structured feedback
annotatecommandsetup L2★5,331
backnotprop/plannotator ↗What it does
Open files and URLs in annotation editor interface
Best for
Teams reviewing specifications, documentation, or design rationales where structured feedback (comments, deletions, image callouts) beats inline email.
Inputs
- · Local file path (Markdown, HTML)
- · URL (documentation, API reference, or blog)
- · Folder path for batch annotation
Outputs
- · Browser-based annotation editor with highlighted text
- · Structured annotation feedback (deletions, comments, labels)
- · Image attachments with highlights
Requires
- · Jina Reader (optional, for URL fetching)
- · Turndown (for HTML to Markdown conversion)
- · Local file system
Preconditions
- · Plannotator CLI installed
- · File or URL accessible
- · Browser available for UI
Failure modes
- · Jina Reader fails on very large or malformed pages
- · HTML conversion loses table structure or formatting
- · Private URLs fail unless --no-jina flag used
- · Folder mode excludes build directories but user may miss them
Trust signals
- · Supports three input modes: local files, URLs, folders
- · Annotation types: deletion, comment, quick label, approval, global comment
- · Image pasting with optional markup
- · Jina Reader toggle for private/authenticated content
- · Folder browser auto-excludes build directories