plannotator

Claude Code Plan Mode Plugin - Plannotator youtu.be/a_AT7cEN_9I?si… via @YouTube

@pyrons_ ill have to change it slowly overtime so users dont get frustrated

@plannotator still waiting for the favicon to go from a generic P to a tator

Plannotator 0.19.17 - setup goal skill reworked to simpler facts-based - added `plannotator --version`

@pyrons_ @FUCORY lmao is that good or bad

@plannotator @FUCORY oh wow what a look

Introducing npx claude-p A dropin replacement for claude -p

@pyrons_ @FUCORY Ive been think i can just embed the agents in the browser & integrate the app. do you think users would like this better. prototype made with /plannotator-setup-goal

@FUCORY lmao @plannotator

The more i use `/goal` the more I want to ensure the model gets simple facts right up front. So I use a version of @mattpocockuk grill-me focused on @Everlier's methodology around facts. Facts allow me to describe very clear requirements for a feature or system. & Not always that technical. The more I do with AI, the less patient I get, so I can't read a ton of markdown, but I can afford to read/verify simple lists of facts. Once facts are established i let the agent refine a plan for itself (every decision aligned to those facts) so it can figure out order of operations. have been having a lot of fun with this process. composition by @editframe

@shinedairz Ive been iterating a bunch on this & have refined the skill to a much simpler, yet maybe more powerful state. A lot easier for you to review - focuses on facts of the thing you want. github.com/backnotprop/pl…

@plannotator Hey, just wanted to say that I'm having a blast using this more and more. To give some fb I noticed then that whenever I use the goal setup skill within codex, it will sometimes be impatient and run "plannotator sessions --open 1" while I'm still reading - can this be mitigated?

html spec, activated

built a skill that reorders any diff into a narrative walkthrough, then opens it in @plannotator so you can annotate inline. The agent reads your comments and fixes the code, then regenerates the walkthrough so you can go again. Point it at a remote PR and it'll still generate the walkthrough (just without the fix loop)

@pierrecomputer cmd/ctrl+click on tokens to find where they are defined or used

Now in Plannotator code review - code refs maybe the spiciest diffs in all of the land (diffs lib by @pierrecomputer)

@pierrecomputer *npm had an outage earlier... now released for Pi and OpenCode.

@pyrons_ @JinjingLiang @orca_build I understand that people are gonna hack ways to pty a session and sdk over it. But the prefill im not understanding advantage over just prompting directly. I have a lot of automated aliases that do this

@pyrons_ @JinjingLiang @orca_build I'm not getting it. -p was for background processes esp with structured output. What is difference of --prefill and just `claude "Say hi"`

💡Here's a work around for the Claude Code `-p` change This is actually a hidden option that has been in Claude Code awhile. Simply use `--prefill` We have use it in @orca_build for months to get around the limitations

Release notes: github.com/backnotprop/pl…

Plannotator 0.19.15 released Plan/Annotate: - Copyable hook path + creation guidance in Settings Hooks tab (custom plan instructions) - (fix) Loose list continuation content now indents correctly under parent bullet Code Review: - jj evolution history diff mode - Pick a specific commit as the diff base - (fix) File comment drafts persist across close/reopen - (fix) GitLab: concatenated JSON pagination on large MRs - (fix) GitLab: unposted inline comments saved locally on API timeout OpenCode: - (fix) Commands intercepted before LLM, preventing large files from blowing up agent context Codex: - Hooks feature flag updated to match current CLI - Install script now includes Codex setup guidance Other: - (fix) PLANNOTATOR_PORT=0 accepted without spurious warning - (integrity) CI id-token:write scoped to AWS OIDC jobs only

planned out and ran a low stakes overnight goal to create psuedo-lsp capabilities, should I ship it?

@grantrowberry @0xSero github.com/nicobailon/vis…

Release Notes: github.com/backnotprop/pl…

x.com/plannotator/st… ^ auto create instructions for better planning using /plannotator-compound Enable hooks in Settings > Hooks (currently only supported for planning agents)

Plannotator 0.19.14 released today Plan/Annotate: - Visual Explainer skill + HTML render-annotate mode - Code-file line range (`file.ts:10-20`) hover previews - Hooks: let agent know about GFM syntax and allow you to customize instructions (tell your agent how to plan). - Rendering optimization (fewer re-renders, Sonner toast migration) Code Review: - Configure tab size - Configure diff line background intensity - Ask AI now available in all-files diff view - jj default target resolves dynamically from `trunk()` OpenCode: - Planning agents with display names or special characters now resolve correctly

@pyrons_ @ctatedev Looks cool! Will explore more & try to incorporate. I also how some thoughts, and spec-ish, on how markdown for engineers should be rendered x.com/plannotator/st…

@ctatedev @plannotator

New proposal: mdxg.org Markdown Experience Guidelines A spec for how interfaces should present Markdown Virtual pages, navigation, search, theming Any .md file, zero changes Reference implementation below Would love your input