sadd:do-in-steps

Decompose complex tasks into sequential subtasks with judge-verified sub-agent dispatch.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/dalawwa/labor-methods --skill sadd-do-in-steps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sadd:do-in-steps
Source: https://github.com/dalawwa/labor-methods/tree/main/.cek/plugins/sadd/skills/do-in-steps
Command: npx skills add https://github.com/dalawwa/labor-methods --skill sadd-do-in-steps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex tasks often require decomposing a request into sequential subtasks, distributing work to specialized sub-agents, and verifying each step with an independent judge to ensure reliability and alignment.

Core Features & Use Cases

  • Task decomposition: Break down complex objectives into ordered subtasks with clear inputs/outputs.
  • Sub-agent orchestration: Dispatch focused agents with scoped context, models chosen per subtask, and controlled data flow.
  • Independent verification: Use judge agents to validate each step before proceeding, with retry loops for failures.
  • Context-aware progression: Pass concise, relevant context between steps to maintain continuity without leaking unnecessary details.
  • Workflow reliability: Enforce sequential execution, error handling, and clear pass/fail criteria for robust automation.

Quick Start

Provide a high-level task description and let the system decompose, dispatch sub-agents, and verify each step via an internal judge.

Frequently Asked Questions about sadd:do-in-steps

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

FAQPage Schema
How do I orchestrate multi-step LLM workflows with sub-agents?

Multi-step LLM orchestration coordinates complex tasks by decomposing objectives into sequential subtasks, dispatching specialized sub-agents, and verifying outputs with independent judge agents. Context passes concisely between steps to maintain continuity without leaking unnecessary details.

How does judge-based verification work for sequential AI tasks?

Judge-based verification uses independent judge agents to validate each sequential AI subtask output against clear pass/fail criteria before proceeding. This enforces workflow reliability through controlled execution and limited retry loops triggered automatically upon step failures.

What is the best way to decompose complex AI tasks into subtasks?

Task decomposition breaks complex objectives into ordered subtasks with clear inputs and outputs. This approach enables sub-agent orchestration by dispatching focused agents with scoped context, models chosen per subtask, and controlled data flow for robust automation.

Can I use different LLMs for specific subtasks within a single workflow?

Yes, sub-agent orchestration supports model selection chosen per subtask. You can dispatch focused agents with scoped context and controlled data flow, allowing specific LLMs to handle individual steps within a single end-to-end workflow.

How do I pass context between sequential AI workflow steps safely?

Context-aware progression passes concise, relevant context between sequential workflow steps to maintain continuity. This controlled data flow ensures sub-agents receive necessary inputs for independent verification without leaking unnecessary details across the orchestration pipeline.

What happens when a sub-agent fails verification in a sequential workflow?

When a sub-agent fails independent judge verification, the workflow enforces error handling via limited retry loops. This mechanism ensures workflow reliability by re-attempting failed steps under clear pass/fail criteria before proceeding to subsequent sequential subtasks.