jds-execute

Execute confirmed implementation plans by dispatching isolated subagents with rubber-duck verification.

13|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/josipmusa/jds --skill jds-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jds-execute
Source: https://github.com/josipmusa/jds/tree/main/skills/jds-execute
Command: npx skills add https://github.com/josipmusa/jds --skill jds-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the execution of a confirmed implementation plan by dispatching isolated subagents, ensuring context isolation and a disciplined workflow.

Core Features & Use Cases

  • End-to-end plan execution with a configurable concurrency model.
  • Isolated subagents receive only task-relevant context to avoid leakage of session history.
  • Built-in verification flow using the rubber-duck reviewer to validate results before marking tasks complete.

Quick Start

Run jds-plan to generate a plan and then invoke jds-execute to run tasks one by one with isolated subagents.

Frequently Asked Questions about jds-execute

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

FAQPage Schema
How do I execute an implementation plan with isolated subagents?

To execute an implementation plan with isolated subagents, you need a confirmed plan stored under docs/jds/plans/ and then invoke the execution workflow to dispatch tasks one-by-one with context isolation and concurrency control.

How does context isolation work when dispatching subagents for task execution?

Context isolation works by providing each dispatched subagent with only task-relevant context, preventing the leakage of previous session history and ensuring a disciplined workflow during plan execution.

What is the best way to verify task completion during automated plan execution?

The best way to verify task completion during plan execution is using a built-in rubber-duck reviewer workflow that validates results before marking individual tasks as complete.

Can I control concurrency when executing implementation plans with multiple subagents?

Yes, you can control concurrency when executing implementation plans with multiple subagents through a configurable concurrency model that manages how isolated subagents process tasks sequentially or in parallel.

Do I need a specific plan format before I can start dispatching subagents?

Yes, you need a confirmed implementation plan located under the docs/jds/plans/ directory before you can start dispatching isolated subagents to execute it.

Why use isolated subagents for workflow execution instead of a single agent context?

Isolated subagents prevent session history leakage during workflow execution, ensuring each task receives only relevant context for disciplined context isolation and verifier-based completion validation.