Skip to content
ISSUE 001·LIVE·13:04 IL

The open journal · Daily series

Builder of the Day

One builder. One open-source project. One engineering choice worth learning from. Every day, in English and Hebrew, under 300 words per language.

GitHub Trending is a discovery source, not a quality score. Credit belongs to each project's creators and contributors. These are independent editorial spotlights, not endorsements or sponsorships.

002MIT · Open source#

Jesse Vincent writes the plan for an executor with no memory

A hand-off habit worth borrowing from superpowers.

Coding agents lose context. Jesse Vincent's open-source superpowers wraps them in a development methodology built from small composable skills, and the agent checks for a relevant skill before starting any task: brainstorm first, then design, then plan, then implement.

The specific choice sits inside writing-plans. Work is broken into tasks of two to five minutes, and every task carries exact file paths, complete code, and verification steps. The plan is written to be followed by someone with no project context at all, because that is exactly who executes it: the subagent-driven-development skill dispatches a fresh subagent per task, reviews each task for spec compliance and code quality, then runs one broad review of the whole branch at the end.

There is a trade-off. This front-loads design and planning effort, and a very detailed plan can go stale as the code moves. The repository itself ships a cheaper path, executing-plans, which runs everything inline in one session with a single final review. What is worth borrowing is the direction of the hand-off: instructions written to survive a context boundary, and review between tasks instead of only at the end.

Repository review, not a hands-on benchmark. Superpowers was not installed or run here; its workflow claims are the project's own.

Sources & credit: Repository & documentation · @obra · GitHub Trending · Observed 2026-11-20

001MIT · Open source#

Cathryn Lavery makes the diagram an editable artifact

A small output-format decision worth borrowing from diagram-design.

A diagram should survive the chat that produced it. Cathryn Lavery's open-source diagram-design skill gives coding agents an opinionated way to draw diagrams, then leaves the result in one self-contained HTML file with inline SVG.

That choice is the interesting part. The output is not a screenshot locked to one canvas app. The repository documents two ways to revise it: ask the agent again, or edit the SVG. Export can produce SVG or PNG for another document without making that export the only surviving source.

The trade-off matters: this is not a Mermaid-like text model or a drag-and-drop canvas. SVG can be edited, but changing the diagram is still lower-level work. What is worth borrowing is the hand-off: keep the drawing, not only a flattened image.

Repository review, not a hands-on benchmark. The project's layout and compatibility claims have not been independently tested here.

Sources & credit: Repository & documentation · @cathrynlavery · GitHub Trending · Observed 2026-11-19