Dsh Plans

This is an agent preset: a directory containing one agent.cordis.yml, which gives a session its own tools and prompt. Presets are not installed with dsh plugin add either — drop the directory into your preset root and DSH picks it up, after which it can be copied or deleted from the UI.

git clone https://github.com/Optim-Agent/dsh-plans.git <preset-root>/dsh-plans

# the directory must contain agent.cordis.yml at its top level
ls <preset-root>/dsh-plans/agent.cordis.yml

Then start the profile you want the preset available in: dsh --profile my-profile.

Prerequisites

API key

Not required.

Network access

Not required at runtime.

Language

Python

Verdict reason

agent-preset uses its own install path, so bundle checks do not apply

Rules applied from

docs/user/develop/basic/publish.md

Checked at

2026-08-15

Human-in-the-loop planning preset for the [DeepSeek Harness] (DSH): researched, refined Markdown plans before any code changes, then goal-driven execution after an explicit handoff. Turn a rough repository-change request into a traceable plan under `./dsh-plans/`, refine that plan with reviewer or criticizer subagent rounds, and hand the accepted plan to a persistent DSH goal that drives implementation until the plan's Verifier Checklist passes. Everything runs on DSH's native mechanisms — `ask_user_question`, subagents, the goal loop, and bundled skills — with no separate execution engine. 1. The agent inspects the target repository read-only, then asks the workspace's language setting once (persisted for every later run in that workspace). 2. Planning questions come one at a time, in a s