read-plans

Fetch, parse, and update HTML plans published via postplan URLs.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill read-plans-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: read-plans
Source: https://github.com/gmackie/agent-skills/tree/main/skills/read-plans
Command: npx skills add https://github.com/gmackie/agent-skills --skill read-plans-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nodejs, curl.

What problem does it solve? Plans published as HTML documents on postplan.dev are hard to consume programmatically: URLs come in multiple forms, statuses and tasks are embedded in markup, and updates must be republished without breaking the original draft link. This Skill resolves raw plan URLs, extracts structured content, and republishes updates correctly. ## Core Features & Use Cases - URL Resolution and Fetching: Converts any postplan URL form into its raw endpoint and retrieves the latest or a pinned version with curl. - Structured Plan Parsing: Extracts title, status badge, metadata, phase sections, task tables with statuses, and mermaid diagram sources from the stable HTML structure. - Plan Execution and Updating: Works phase by phase using each task's Verification column as the done-condition, then edits the source file and re-uploads it to publish a new version at the same URL. - Use Case: Given a postplan link in a pull request, fetch the plan, confirm it is approved, execute each phase's tasks, and mark them done by re-uploading the updated source HTML. ## Quick Start Fetch the plan at this postplan URL, summarize its phases and task statuses, and tell me which tasks are still todo.

Frequently Asked Questions about read-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch a plan from a postplan URL?▼

Resolve the URL to its raw form and fetch it with curl. Given https://<id>.postplan.dev/ or https://postplan.dev/d/<id>, request https://postplan.dev/d/<id>/raw; append /v/<n>/raw for a specific version. Omitting the version returns the latest.

How do I list my published postplan drafts?▼

Run npx postplan list to see your account's drafts, descriptions, linked git repos, and version counts. Run npx postplan auth login once beforehand. Local path-to-draft mappings from previous uploads are stored in ~/.postplan.

How do I update a published plan without breaking its URL?▼

Edit the original source file, usually docs/plans/*.html in the repo or the path recorded in ~/.postplan, then run npx postplan upload on that same path. This publishes a new version at the same URL; uploading from a different path or machine creates a new draft.

What structure can I extract from a postplan HTML document?▼

Plans have a stable structure despite free theming: the h1 holds the title and status badge, .meta holds date and repo info, h2 headings mark sections, phase tables contain Task/Files/Verification/Status columns, and mermaid sources sit in details.mermaid-source pre blocks.

What happens if the plan source file is lost?▼

Save the fetched raw HTML back to its original path, edit it, and re-upload from the original machine where ~/.postplan still maps that path to the draft. Uploading from a different path or machine creates a new draft URL, so inform the user if that occurs.