j.dooo

Orchestrates parallel task execution by launching sub-agents and looping through eligible board items.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running multiple implementation tasks one at a time wastes session time, and manually tracking which stories or tasks are ready to run in parallel is error-prone. This Skill automates the loop of starting implementations via sub-agents and continuously offering the next parallelisable work item from the board. ## Core Features & Use Cases - Parallel execution orchestration: Calls the /do skill to launch background sub-agents for implementations, then returns to the board to find more work. - Eligibility filtering: Reads stories and tasks from the Markdown board and only offers items that are Pending, unblocked, and listed in project/todo.md (or whose parent story is). - Interactive selection loop: Presents a numbered list of candidates with a "Done" option, looping until the user stops or no eligible tasks remain. - Use Case: After planning a sprint, invoke this Skill to kick off one implementation, then keep selecting additional unblocked tasks so multiple sub-agents work in parallel until you choose "Done". ## Quick Start Ask the agent to run all pending board tasks in parallel using j-dooo, then pick tasks from the offered list until you select Done.

Frequently Asked Questions about j.dooo

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

FAQPage Schema
How do I run multiple tasks in parallel with an AI agent?▼

Invoke the j-dooo skill, which calls /do to start an implementation in a background sub-agent, then returns to the board and offers the next eligible task. Keep selecting tasks to run them in parallel, or choose Done to stop.

Which tasks are eligible for parallel execution?▼

A story or task is eligible if its status is Pending, all its blocking dependencies are at least Running or Passed, and it is listed in project/todo.md or its parent story is. Ineligible items are never offered.

Why use j-dooo instead of the dooo command?▼

j-dooo is a collision-safe alias of the dooo skill. It exists so the same parallel orchestration flow remains reachable when a host tool's built-in command shadows the bare /dooo name.

What happens when no tasks are eligible to run in parallel?▼

If all remaining todos are blocked or already running, the skill skips the selection prompt and ends the loop, informing you that no more implementations will be started in this session.

Does j-dooo update the board status of started tasks?▼

Yes. After /do hands back control, the skill marks the story or task that was just started as Running by updating the status field in its board file's YAML frontmatter.