dos-replan-loop

Automate bounded dos-replan sweeps with fixed iteration limits and guarded release.

18|4|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-replan-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dos-replan-loop
Source: https://github.com/anthony-chaudhary/dos-kernel/tree/main/claude-plugin/skills/dos-replan-loop
Command: npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-replan-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates repeated planning sweeps so a workspace can stay refreshed on a fixed cadence without constant manual supervision.

Core Features & Use Cases

  • Recurring planning runs: Re-executes dos-replan at a chosen interval and stops after a configured iteration cap.
  • Guarded release flow: Checks whether the workspace is safely on the resolved trunk before allowing commit and release actions.
  • Fail-closed safety: Skips release when the default branch cannot be resolved, or when the changes are not suitable for an on-trunk release.
  • Use case: Run unattended planning refreshes for a repository that needs periodic queue updates and optional release handling.

Quick Start

Ask the skill to run a bounded dos-replan loop for this workspace with your preferred interval and maximum iteration count.

Frequently Asked Questions about dos-replan-loop

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

FAQPage Schema
How do I automate recurring planning sweeps on a fixed cadence without manual supervision?

Automated recurring planning sweeps execute dos-replan at a chosen interval and stop after a configured iteration cap, keeping workspace queues refreshed without manual babysitting.

What happens to commit and release actions when the default git branch cannot be resolved?

Fail-closed safety skips release actions when the default branch is unknown, ensuring guarded on-trunk release behavior only proceeds when git trunk resolution succeeds.

Can I run unattended workflow loops with periodic wakeups and optional release gating?

Unattended workflow loops support periodic wakeups with optional commit-and-release gating, applying fixed iteration limits to control bounded dos-replan sweeps safely.

How does guarded on-trunk release behavior protect changes during workflow orchestration?

Guarded on-trunk release behavior checks whether the workspace is safely on the resolved trunk before allowing commit and release, skipping actions when changes are unsuitable for release.

Do I need git trunk resolution before starting a bounded dos-replan loop?

Git trunk resolution is required before starting a bounded dos-replan loop, as fail-closed handling prevents release actions when the default branch cannot be determined.