FAQ
How do I install todo-write?
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/todo-write". Inspect the command and pinned source before running it.
nexu-io/open-design
TodoWrite-driven plan that the agent commits to before generation.
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/todo-write"Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Limited to facts supported by the pinned source
Before writing any artifact files, the agent commits to a numbered plan via the TodoWrite tool. The plan is the audit trail; subsequent turns either tick items off or rewrite the plan. The atom's prompt fragment teaches the agent to:
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/todo-write"The pinned source contains about 122 English words and 0 usable sections. That evidence supports a source profile, not a complete guide.
122 source words · 0 usable sections
FAQ
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/todo-write". Inspect the command and pinned source before running it.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Before writing any artifact files, the agent commits to a numbered plan via the TodoWrite tool. The plan is the audit trail; subsequent turns either tick items off or rewrite the plan. The atom's prompt fragment teaches the agent to:
The Open Design daemon does not enforce a particular tool name; the agent is free to use TodoWrite (Claude Code) or an in-prompt list. The atom's job is to keep "make a plan first" in the system prompt so non-trivial workflows don't skip the planning step.