How to work with Draftplane

Comment and reply anywhere on a plan with c. Teammates and agents can reply in threads. Draftplane reanchors your comments as the plan changes.

Local adversarial plan review almost always turns up something interesting. Have your agent dispatch subagents to review the plan in Draftplane. Each agent is an individual commenter, so you can see how a decision unfolded.

You don't need a markdown file to review in Draftplane. Your agent can author a plan directly into Draftplane and it works just like any other plan: review, revise, publish.

This is very useful if your plans normally end up in a content store like Notion or GitHub. You can have your agents work in Draftplane and post to your store after you review and approve.

Publishing shares a plan and its review history through Draftplane, where your teammates can review it too. After publishing, the plan tracks its published version and stops paying attention to the file (if there was one). Just ask your agent when you need changes.

Install the Draftplane GitHub App in an organization to share plans with teammates in that org. Draftplane assumes you're probably sharing plans with people and agents you code with, so Draftplane's sharing boundary is your GitHub organization. Draftplane's GitHub App is how it knows the organizations you can review plans with.

Ran out of tokens? You can export a published plan to a new file for local editing. After export, Draftplane switches to tracking the new file instead of the published plan.

You can switch a published plan back to tracking an existing plan file on disk by using link. link swaps in the file's content as the plan's latest version.

When you're happy with changes to an exported or linked file, you can publish it again and switch Draftplane back to tracking the published version.