- Agent Orchestration
- Agent
- Advanced
- Claude Code
- Published
DAG Scheduler with Fan-Out/Fan-In Barriers and Resumable Run Ledger for Agent Pipelines
Guides Claude Code to build or refactor a dependency-aware DAG scheduler for agent phases, with cycle validation, bounded parallelism, join policies, retries, and an append-only run ledger so interrupted runs resume without redoing finished nodes.
You get: Summary and merge recommendation, verified Facts vs Assumptions and node table
The prompt
mkdir -p .agents/skills/dag-scheduler-with-fan-out-fan-in-barriers-and-resumable-run-led && curl -sL "https://prompts-gpt.com/prompts/dag-scheduler-with-fan-out-fan-in-barriers-and-resumable-run-ledger-for-agent-pipelines/raw" -o .agents/skills/dag-scheduler-with-fan-out-fan-in-barriers-and-resumable-run-led/SKILL.mdTips and common edits
Run in a repository that already has an executor or a documented list of agent phases. Approve the Phase 1 plan before edits begin. Provide idempotency details for each node, since resume safety depends on them. Pair with separate prompts for checkpoint/rollback and handoff contracts rather than expanding this one.
Questions about this prompt
More like this
More in Agent OrchestrationAgent Run Post-Mortem: Trace Root Cause and Prompt or Tool Fixes
Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.
Checkpoint and Rollback Manager with Compensation Steps and Failure Injection Tests
Guides Claude Code to implement checkpoint snapshots, rollback modes, and compensating actions for side-effecting agent phases, then prove them with failure-injection tests. Helps you decide the rollback strategy per phase.
Orchestrator System Prompt Builder with Progress Ledger and Stop Conditions
Writes a ready-to-deploy orchestrator system prompt that delegates to your workers, tracks progress in a ledger, merges results and stops on defined conditions.
Parallel Git Worktree Task Split with Interface Contracts and Merge Order
Turns a pasted feature spec into independent coding-agent tasks with file ownership, interface contracts, a merge order and a done command for each task.
Subagent Fan-Out Plan for a Large Codebase Migration
Plans a big migration so an orchestrating agent can split it into independent chunks for parallel subagents, each with a clear brief, a verification command and merge rules.
Typed Phase Handoff Contracts and Validator for Multi-Agent Pipelines
Has Claude Code define schema-based handoff contracts between agent phases, generate a validator, and add contract tests. Supports the decision of which phase boundaries need strict contracts versus lightweight checks.
Dependency Graph Planner for a Multi-Agent Software Release Workflow
Turns a list of release tasks into a dependency graph with parallel batches, critical path, shared-resource conflicts, and agent assignments. Supports the decision on what to run now versus wait on.
Characterization Tests Before a Refactor
Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.
Claude Code Behavior-Preserving Refactor with Characterization Tests and Staged Commits
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.
Claude Code Feature Implementation Plan and Build from a Ticket with Repo Convention Discovery
Has Claude Code investigate how similar features are built in the repository, produce an implementation plan with acceptance tests, then implement it in verified increments. Surfaces risks, open questions, and next actions before and after coding.
Claude Code Hook Writer: Auto-Run Lint, Typecheck or Tests After Edits
Produces a PostToolUse hook entry for settings.json, the script it calls and a concrete procedure to test that the check runs after file edits.
Claude Code Plan-Then-Implement a Feature With Approval Checkpoints
Makes Claude Code explore the repo, write a step-by-step plan for your approval, then build the feature in small verified steps, stopping at each checkpoint for your go-ahead.