Introduction¶
DeepSeek Harness (DSH) adopts a plugin architecture and allows functionality to be extended through Cordis plugins. The default agent-loop behavior usually lacks structured engineering constraints. The dsh-gsd-bundle plugin reimplements Git Ship Done (GSD) as a host-plane Cordis plugin set, replacing the default agent-loop with a GSD phase loop. This turns every session into a controlled, artifact-based engineering loop.
Core Positioning¶
The core goal of this plugin is to reimplement opengsd-core and integrate it into the DSH ecosystem. It provides checkpoint-resume, window ledger, conversational UAT loop, capability gates, and background-job runtime. The data shows that the plugin contains 28 Cordis plugin entries (1 override + 27 inserts), 37 gsd_* tools, and 34 /gsd-* commands.
GSD Phase Loop¶
Each work unit is defined as a phase and must pass through the following steps in order:
Spec → Discuss → (UI design, optional) → Plan → Execute → Verify → Ship
The loop is constrained by advisory soft gates, such as gap-analysis after Plan, code-review and ui-review after Execute, and validate before Ship. System state is stored in the .planning/ directory on disk. STATE.md serves as the navigation anchor, ensuring that state persists across sessions and remains available after context resets.
Key Features¶
The plugin completed its feature build through two major milestone versions:
-
v3.1 (core-loop-helpers)
- phase-management: Manages phases directly in
ROADMAP.md. - smart-entry: Detects the current project state and routes to the best next step.
- freeform-routing: Parses natural-language intent and dispatches commands.
- quick-batch: Runs tasks in batches.
- fast-mode: Provides a lightweight single-pass path.
- mvp-phase: Interactive scope definition flow.
- node-repair: Performs bounded automatic repair for phases that fail validation.
- review-fix-companion: Refactors code review remediation.
- phase-management: Manages phases directly in
-
v3.0 (upstream-parity)
- spec-phase: Generates
SPEC.mdand gates it by an ambiguity score (≤ 0.20). - gap-analysis: Generates a requirements-to-plan coverage table.
- code-review & ui-review: Performs code and UI reviews.
- validate-phase: Maps requirements to test infrastructure.
- undo: Performs safe rollback via
git revert. - health: Diagnoses the integrity of the
.planning/directory. - assumption-delta: Checks architectural assumption changes in the
plan:prehook. - pause-resume-work: Supports pausing and resuming phases.
- autonomous: Drives the remaining incomplete phases.
- add-tests: Automatically generates test files.
- spec-phase: Generates
Typical Usage¶
Below are fact-based command usage scenarios:
-
Phase management
Use/gsd-phase-manageto add, insert, remove, reorder, or edit phases inROADMAP.md. The system automatically keepsROADMAP.md, the progress table, andSTATE.mdconsistent. -
State routing
Use/gsd-nextto detect the current project state and automatically route to the best next operation. -
Intent parsing
Use/gsd-routeto parse natural-language intent and dispatch it to the most suitable GSD command (recommendation only; it does not run automatically). -
Fast mode
For simple phases, use/gsd-fast-modeto start the lightweight single-pass path. -
MVP definition
Use/gsd_mvp_phasefor interactive scope proposal and confirmation, generatingPLAN.md. -
Repair flow
Use/gsd_repairto perform bounded automatic repair on phases that fail validation (up to 2 rounds), generating a repair report. -
Code review remediation
Use/gsd_code_review --fixto rebuild review remediation functionality and execute a bounded anchored editing contract.
Environment and Dependencies¶
- Runtime environment: Requires Node.js >= 20.
- License: MIT License.
- State storage: State is stored in the
.planning/directory and relies onworkflow.assumption_deltafor architectural checks. - Gating mechanism: The spec-phase stage is gated by an ambiguity score (the total score across 4 weighted clarity dimensions ≤ 0.20).