Skill

Todowrite

Route TODO checklists to the right storage. session - in-session tracking via /wip, file - persistent TODO (fix_plan.md, TODO.md), issue - team-shared via Gi...

Verified: 2026-05-15 (clawhub-ingest-2026-05-15)

When to use Todowrite

Choose if

You're an agent inside a Claude Code / Codex session that needs to decide where a new TODO belongs — `/wip` for in-session, fix_plan.md / TODO.md for persistent local, or GitHub Issues for team-shared. This skill gives you the routing decision tree and the formatting conventions for each backend.

Avoid if

You only need a single storage backend and already know which (skip the router and write directly). Also avoid if your workflow uses Jira / Linear / Asana — the skill targets GitHub Issues via `gh` CLI for the team-shared path.

Risk Flags

  • LOW dependency Team-shared issue path depends on GitHub CLI (`gh`) being installed and authenticated per README; non-GitHub trackers are not supported.
  • LOW dependency Depends on the `wip` skill for session-based routing per README; install that alongside if you want the session backend.

Cost

Type: Free

Distribution

ClawHub
todowrite
License
MIT-0