j.todo

Adds missions to a Markdown todo list linked to epics and stories.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-todo-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: j.todo
Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/j-todo
Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-todo-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

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.

Frequently Asked Questions about j.todo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a task to the project todo list?▼

Invoke /j-todo (or /todo) and answer the prompts about where the work belongs and its goal. The skill classifies the mission into an Epic/Story and appends it to project/todo.md using the todo_manager.sh script.

What does the --trivial flag do in the todo skill?▼

The --trivial flag writes the mission as a fully-formed task board file immediately with execution_scope forced to inline, skipping the normal breakdown pass. It requires an existing story and records the heuristic-computed tier in scope_rationale for audit.

Why use /j-todo instead of /todo?▼

Both invoke identical behavior, but /j-todo is a collision-safe alias. Use it when a host tool's built-in command shadows the bare /todo name, since skill resolution matches literal directory names.

Can --trivial create a new story or epic?▼

No, --trivial only forces the scope of a single task and requires an already-existing story to attach to. If the mission has no story yet, create it through the normal /todo classification flow first, then apply --trivial.

What happens after I finish adding todos?▼

After you answer Done, the skill asks whether to execute the todo list. Answering yes invokes the /do skill, which routes full task IDs straight into its Inline Execution Path without a redundant breakdown pass.