What problem does it solve? AI-assisted development sessions lose track of queued work, and ad-hoc task capture lacks structure. This Skill captures missions into a persistent project/todo.md backlog, optionally linking each one to Epics and Stories on a Markdown scrum board so work survives session boundaries. ## Core Features & Use Cases - Structured backlog capture: Classifies each mission into an existing story, a new story in an existing Epic, a new Epic, or none, then writes it to project/todo.md via the todo_manager.sh script. - --trivial fast path: Creates a fully-formed task board file immediately with execution_scope forced to inline, including computed-tier audit trail, story frontmatter registration, and direct /do routing. - Collision-safe alias: Provides a guaranteed-unshadowed /j-todo invocation identical to /todo when a host tool's built-in command shadows the bare form. - Use Case: During a planning session you realize three follow-up fixes are needed; invoke /j-todo to queue each one linked to its story, then hand the list off to /do for execution. ## Quick Start Ask the agent to run /j-todo and add a mission such as "Fix typo in error message: E12_S03" to the project todo list.