j.do

Executes scrum board tasks through developer agents with scope routing and rollback anchors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? AI coding sessions lose track of queued work and mix implementation with verification, producing unreviewed code and vanished progress. This Skill reads tasks from a Markdown scrum board, resolves each to its full Epic/Story/Task context, and drives a developer agent through implementation with enforced scope tiers, file locking, and rollback on failure. ## Core Features & Use Cases - Scoped task execution: Routes each task to inline, light, or full task pipelines based on execution_scope frontmatter and configurable thresholds in scope-thresholds.json. - Story-bundle mode: Executes all tasks of a story sequentially in one shared worktree with an epic-level lock, atomic bundle manifests, cross-bundle conflict detection, and git-anchor rollback on failure. - Scope-creep detection: Runs an intent-vs-diff check comparing changed files against the task description, writing non-blocking conflict reports and divergence flags. - Use Case: A developer types /do E32_S05 to execute an entire story; the Skill locks the epic, spawns one developer subagent in a shared worktree, updates each task's board status, and rolls back cleanly if any task fails. ## Quick Start Ask the agent to run /do and pick the next task from the scrum board todo list to implement it.

Frequently Asked Questions about j.do

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

FAQPage Schema
How do I execute a task from the scrum board?▼

Run /do to list queued tasks from project/todo.md, then choose a task by number, title, or ID. The Skill resolves it to its full board context and dispatches a developer agent to implement it.

How do I run all tasks of a story at once?▼

Invoke /do with a story ID like /do E32_S05 to enter story-bundle mode. It acquires an epic-level lock, spawns one shared developer subagent in a bundle worktree, and executes the story's tasks sequentially with rollback on failure.

What does the --trivial flag do in /do?▼

The --trivial flag forces an existing task's execution_scope to inline at dispatch time, skipping the worktree and subagent pipeline. It is human-only, records an override justification for audit, and falls back to the full task pipeline if the smoke test fails.

What happens when a bundle task fails during execution?▼

The failing task is marked Failed, a partial diff patch is saved, uncommitted changes are stashed, and the repository is reset to the pre-bundle anchor SHA via git reset --hard. The bundle manifest and epic lock are then removed and execution halts.

Does /do detect when a task changes unexpected files?▼

Yes. After each task, an intent-vs-diff check compares git diff output against the task description and acceptance criteria. Unexpected files trigger a non-blocking conflict report in project/queue and a divergence_flag on the task frontmatter.