do-in-steps

Decompose complex tasks into sequential sub-agent steps with per-step judge verification.

1.5k|154|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/NeoLabHQ/context-engineering-kit --skill do-in-steps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-in-steps
Source: https://github.com/NeoLabHQ/context-engineering-kit/tree/main/plugins/sadd/skills/do-in-steps
Command: npx skills add https://github.com/NeoLabHQ/context-engineering-kit --skill do-in-steps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex multi-step tasks often fail when executed in a single pass because later steps depend on earlier results and errors compound silently. This Skill orchestrates a task as ordered, dependent steps run by isolated sub-agents, passing context forward and verifying each step with an independent LLM-as-a-judge before proceeding.

Core Features & Use Cases

  • Sequential Orchestration: Decomposes a task into ordered subtasks with a dependency graph, then dispatches implementation sub-agents step by step with context summaries from prior steps.
  • Meta-Judge Verification: Runs a meta-judge in parallel with each implementation agent to generate a tailored evaluation specification, then an independent judge scores the step with up to 3 retries.
  • Per-Step Model Selection: Assigns haiku, sonnet, or opus tiers per step based on scope, complexity, and risk, with escalation rules and cross-provider model mapping.
  • Use Case: Refactoring a shared interface across implementations and consumers — the interface change is verified before implementations update, and implementations are verified before callers are touched.

Quick Start

Ask the agent to run do-in-steps with a task description such as "Refactor UserService class and update all consumers", optionally adding --strict or a --model override.

Frequently Asked Questions about do-in-steps

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

FAQPage Schema
How do I break a complex coding task into sequential steps with an AI agent?

Invoke do-in-steps with a free-form task description. The orchestrator analyzes dependencies, decomposes the work into ordered subtasks, dispatches a sub-agent per step, and passes summarized context from each completed step to the next.

How does LLM-as-a-judge verification work per step?

A meta-judge agent generates a step-specific evaluation specification in parallel with implementation. An independent judge then scores the step output against that specification, and the step retries with judge feedback up to 3 times if it fails.

Can I force a specific model like opus for all steps?

Yes, pass --model haiku, sonnet, or opus to override the per-step model selection policy for every sub-agent. Without the flag, the orchestrator picks a tier per step based on scope, complexity, and criticality.

What does the --strict flag do in do-in-steps?

The --strict flag disables the Iteration Discretion Rule, so a step passes only when the judge score is 4.0 or higher. Otherwise the step retries until the maximum retry limit is reached.

When should I not use sequential step orchestration?

Avoid it for single-file trivial edits or independent tasks with no inter-step dependencies, where decomposition overhead adds latency without benefit. It is designed for tasks where later steps genuinely depend on earlier results.