@ktpartners/dgs-platform 2.6.2

package/commands/dgs/new-project.md

@@ -0,0 +1,42 @@
+---
+name: dgs:new-project
+description: Initialize a new project with deep context gathering and PROJECT.md
+argument-hint: "[--auto]"
+allowed-tools:
+  - Read
+  - Bash
+  - Write
+  - Task
+  - AskUserQuestion
+---
+<context>
+**Flags:**
+- `--auto` — Automatic mode. After config questions, runs research → requirements → roadmap without further interaction. Expects idea document via @ reference.
+</context>
+
+<objective>
+Initialize a new project through unified flow: questioning → research (optional) → requirements → roadmap.
+
+**Creates:**
+- `.planning/PROJECT.md` — project context
+- `.planning/config.json` — workflow preferences
+- `.planning/research/` — domain research (optional)
+- `.planning/REQUIREMENTS.md` — scoped requirements
+- `.planning/ROADMAP.md` — phase structure
+- `.planning/STATE.md` — project memory
+
+**After this command:** Run `/dgs:plan-phase 1` to start execution.
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/new-project.md
+@~/.claude/deliver-great-systems/references/questioning.md
+@~/.claude/deliver-great-systems/references/ui-brand.md
+@~/.claude/deliver-great-systems/templates/project.md
+@~/.claude/deliver-great-systems/templates/requirements.md
+</execution_context>
+
+<process>
+Execute the new-project workflow from @~/.claude/deliver-great-systems/workflows/new-project.md end-to-end.
+Preserve all workflow gates (validation, approvals, commits, routing).
+</process>

package/commands/dgs/node-repair.md

@@ -0,0 +1,26 @@
+---
+name: dgs:node-repair
+description: Autonomous repair operator for failed task verification during plan execution
+argument-hint: ""
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+---
+<objective>
+Repair a failed task during plan execution. Diagnoses the failure and applies one of four strategies: RETRY, DECOMPOSE, PRUNE, or ESCALATE.
+
+Invoked automatically by execute-plan when a task fails its done-criteria.
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/node-repair.md
+</execution_context>
+
+<process>
+Execute @~/.claude/deliver-great-systems/workflows/node-repair.md.
+Preserve all repair strategy gates and logging requirements.
+</process>

package/commands/dgs/overlap-check.md

@@ -0,0 +1,20 @@
+---
+name: dgs:overlap-check
+description: Show which repos are touched by multiple active projects
+allowed-tools:
+  - Read
+  - Bash
+---
+<objective>
+Show cross-project repo and file overlaps. Informational only — never blocks work.
+
+Displays which repos are touched by multiple active projects, file-level conflicts for high-severity overlaps, and any warnings (ghost projects, etc.).
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/overlap-check.md
+</execution_context>
+
+<process>
+Execute the overlap-check workflow from @~/.claude/deliver-great-systems/workflows/overlap-check.md end-to-end.
+</process>

package/commands/dgs/pause-work.md

@@ -0,0 +1,38 @@
+---
+name: dgs:pause-work
+description: Create context handoff when pausing work mid-phase
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+<objective>
+Create `.continue-here.md` handoff file to preserve complete work state across sessions.
+
+Routes to the pause-work workflow which handles:
+- Current phase detection from recent files
+- Complete state gathering (position, completed work, remaining work, decisions, blockers)
+- Handoff file creation with all context sections
+- Git commit as WIP
+- Resume instructions
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/pause-work.md
+</execution_context>
+
+<context>
+State and phase progress are gathered in-workflow with targeted reads.
+</context>
+
+<process>
+**Follow the pause-work workflow** from `@~/.claude/deliver-great-systems/workflows/pause-work.md`.
+
+The workflow handles all logic including:
+1. Phase directory detection
+2. State gathering with user clarifications
+3. Handoff file writing with timestamp
+4. Git commit
+5. Confirmation with resume instructions
+</process>

package/commands/dgs/plan-milestone-gaps.md

@@ -0,0 +1,34 @@
+---
+name: dgs:plan-milestone-gaps
+description: Create phases to close all gaps identified by milestone audit
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+---
+<objective>
+Create all phases necessary to close gaps identified by `/dgs:audit-milestone`.
+
+Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase.
+
+One command creates all fix phases — no manual `/dgs:add-phase` per gap.
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/plan-milestone-gaps.md
+</execution_context>
+
+<context>
+**Audit results:**
+Glob: .planning/v*-MILESTONE-AUDIT.md (use most recent)
+
+Original intent and current planning state are loaded on demand inside the workflow.
+</context>
+
+<process>
+Execute the plan-milestone-gaps workflow from @~/.claude/deliver-great-systems/workflows/plan-milestone-gaps.md end-to-end.
+Preserve all workflow gates (audit loading, prioritization, phase grouping, user confirmation, roadmap updates).
+</process>

package/commands/dgs/plan-phase.md

@@ -0,0 +1,44 @@
+---
+name: dgs:plan-phase
+description: Create detailed phase plan (PLAN.md) with verification loop
+argument-hint: "[phase] [--auto] [--research] [--skip-research] [--gaps] [--skip-verify]"
+agent: dgs-planner
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Task
+  - WebFetch
+  - mcp__context7__*
+---
+<objective>
+Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.
+
+**Default flow:** Research (if needed) → Plan → Verify → Done
+
+**Orchestrator role:** Parse arguments, validate phase, research domain (unless skipped), spawn dgs-planner, verify with dgs-plan-checker, iterate until pass or max iterations, present results.
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/plan-phase.md
+@~/.claude/deliver-great-systems/references/ui-brand.md
+</execution_context>
+
+<context>
+Phase number: $ARGUMENTS (optional — auto-detects next unplanned phase if omitted)
+
+**Flags:**
+- `--research` — Force re-research even if RESEARCH.md exists
+- `--skip-research` — Skip research, go straight to planning
+- `--gaps` — Gap closure mode (reads VERIFICATION.md, skips research)
+- `--skip-verify` — Skip verification loop
+
+Normalize phase input in step 2 before any directory lookups.
+</context>
+
+<process>
+Execute the plan-phase workflow from @~/.claude/deliver-great-systems/workflows/plan-phase.md end-to-end.
+Preserve all workflow gates (validation, research, planning, verification loop, routing).
+</process>

package/commands/dgs/progress.md

@@ -0,0 +1,24 @@
+---
+name: dgs:progress
+description: Check project progress, show context, and route to next action (execute or plan)
+allowed-tools:
+  - Read
+  - Bash
+  - Grep
+  - Glob
+  - SlashCommand
+---
+<objective>
+Check project progress, summarize recent work and what's ahead, then intelligently route to the next action - either executing an existing plan or creating the next one.
+
+Provides situational awareness before continuing work.
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/progress.md
+</execution_context>
+
+<process>
+Execute the progress workflow from @~/.claude/deliver-great-systems/workflows/progress.md end-to-end.
+Preserve all routing logic (Routes A through F) and edge case handling.
+</process>

package/commands/dgs/quick.md

@@ -0,0 +1,41 @@
+---
+name: dgs:quick
+description: Execute a quick task with DGS guarantees (atomic commits, state tracking) but skip optional agents
+argument-hint: "[--full]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Glob
+  - Grep
+  - Bash
+  - Task
+  - AskUserQuestion
+---
+<objective>
+Execute small, ad-hoc tasks with DGS guarantees (atomic commits, STATE.md tracking).
+
+Quick mode is the same system with a shorter path:
+- Spawns dgs-planner (quick mode) + dgs-executor(s)
+- Quick tasks live in `.planning/quick/` separate from planned phases
+- Updates STATE.md "Quick Tasks Completed" table (NOT ROADMAP.md)
+
+**Default:** Skips research, plan-checker, verifier. Use when you know exactly what to do.
+
+**`--full` flag:** Enables plan-checking (max 2 iterations) and post-execution verification. Use when you want quality guarantees without full milestone ceremony.
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/quick.md
+</execution_context>
+
+<context>
+$ARGUMENTS
+
+Context files are resolved inside the workflow (`init quick`) and delegated via `<files_to_read>` blocks.
+</context>
+
+<process>
+Execute the quick workflow from @~/.claude/deliver-great-systems/workflows/quick.md end-to-end.
+Preserve all workflow gates (validation, task description, planning, execution, state updates, commits).
+</process>

package/commands/dgs/reactivate-project.md

@@ -0,0 +1,70 @@
+---
+name: dgs:reactivate-project
+description: Reactivate a completed project
+argument-hint: "[--slug name] [--set-current]"
+allowed-tools:
+  - Read
+  - Bash
+  - AskUserQuestion
+---
+<objective>
+Reactivate a completed project. Restores it to "In progress" status and optionally sets it as the current active project.
+
+Requires confirmation before acting. Shows project status first so the user can verify before reactivating.
+</objective>
+
+<process>
+
+## 1. Show Current Status
+
+```bash
+LIST=$(node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs projects list --raw)
+```
+
+Parse JSON. Identify the target project:
+- If `$ARGUMENTS` contains `--slug <name>`, use that slug.
+- Otherwise, ask the user to specify which completed project to reactivate (there is no "current completed" default).
+
+If no target project can be identified, display "No project specified. Use `--slug <name>` to specify which completed project to reactivate." and exit.
+
+Display the target project's current status (name, completed date).
+
+## 2. Confirm Reactivation
+
+Use AskUserQuestion:
+```
+Reactivate project "{name}"? This will:
+- Change status back to "In progress"
+- Remove completion date
+- Optionally set as current project
+
+Type "yes" to confirm or "no" to cancel.
+```
+
+If user does not confirm, display "Cancelled." and exit.
+
+## 3. Reactivate Project
+
+```bash
+RESULT=$(node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs projects reactivate --slug <slug> [--set-current] --raw)
+```
+
+Where `--set-current` is included if the user wants to resume working on the project immediately.
+
+Parse JSON response.
+
+**If `reactivated: true`:**
+```
+DGS > PROJECT REACTIVATED
+
+Project "{slug}" has been reactivated.
+```
+
+If `--set-current` was used, add: "It is now the active project."
+
+Display remaining active project count.
+
+**If error:**
+Display the error message from the response.
+
+</process>

package/commands/dgs/reapply-patches.md

@@ -0,0 +1,110 @@
+---
+description: Reapply local modifications after a DGS update
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+---
+
+<purpose>
+After a DGS update wipes and reinstalls files, this command merges user's previously saved local modifications back into the new version. Uses intelligent comparison to handle cases where the upstream file also changed.
+</purpose>
+
+<process>
+
+## Step 1: Detect backed-up patches
+
+Check for local patches directory:
+
+```bash
+# Global install (path templated at install time)
+PATCHES_DIR=~/.claude/dgs-local-patches
+# Local install fallback
+if [ ! -d "$PATCHES_DIR" ]; then
+  PATCHES_DIR=./.claude/dgs-local-patches
+fi
+```
+
+Read `backup-meta.json` from the patches directory.
+
+**If no patches found:**
+```
+No local patches found. Nothing to reapply.
+
+Local patches are automatically saved when you run /dgs:update
+after modifying any DGS workflow, command, or agent files.
+```
+Exit.
+
+## Step 2: Show patch summary
+
+```
+## Local Patches to Reapply
+
+**Backed up from:** v{from_version}
+**Current version:** {read VERSION file}
+**Files modified:** {count}
+
+| # | File | Status |
+|---|------|--------|
+| 1 | {file_path} | Pending |
+| 2 | {file_path} | Pending |
+```
+
+## Step 3: Merge each file
+
+For each file in `backup-meta.json`:
+
+1. **Read the backed-up version** (user's modified copy from `dgs-local-patches/`)
+2. **Read the newly installed version** (current file after update)
+3. **Compare and merge:**
+
+   - If the new file is identical to the backed-up file: skip (modification was incorporated upstream)
+   - If the new file differs: identify the user's modifications and apply them to the new version
+
+   **Merge strategy:**
+   - Read both versions fully
+   - Identify sections the user added or modified (look for additions, not just differences from path replacement)
+   - Apply user's additions/modifications to the new version
+   - If a section the user modified was also changed upstream: flag as conflict, show both versions, ask user which to keep
+
+4. **Write merged result** to the installed location
+5. **Report status:**
+   - `Merged` — user modifications applied cleanly
+   - `Skipped` — modification already in upstream
+   - `Conflict` — user chose resolution
+
+## Step 4: Update manifest
+
+After reapplying, regenerate the file manifest so future updates correctly detect these as user modifications:
+
+```bash
+# The manifest will be regenerated on next /dgs:update
+# For now, just note which files were modified
+```
+
+## Step 5: Cleanup option
+
+Ask user:
+- "Keep patch backups for reference?" → preserve `dgs-local-patches/`
+- "Clean up patch backups?" → remove `dgs-local-patches/` directory
+
+## Step 6: Report
+
+```
+## Patches Reapplied
+
+| # | File | Status |
+|---|------|--------|
+| 1 | {file_path} | ✓ Merged |
+| 2 | {file_path} | ○ Skipped (already upstream) |
+| 3 | {file_path} | ⚠ Conflict resolved |
+
+{count} file(s) updated. Your local modifications are active again.
+```
+
+</process>
+
+<success_criteria>
+- [ ] All backed-up patches processed
+- [ ] User modifications merged into new version
+- [ ] Conflicts resolved with user input
+- [ ] Status reported for each file
+</success_criteria>

package/commands/dgs/refine-spec.md

@@ -0,0 +1,38 @@
+---
+name: dgs:refine-spec
+description: Refine a spec through a conversational editing session
+argument-hint: <spec-slug> [--section <N>]
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Grep
+  - Glob
+  - AskUserQuestion
+---
+
+<objective>
+Refine a spec through a structured conversational editing session. Supports section targeting with --section, increments version on save, appends a Refinement Log entry, and warns when refining a final-status spec (which moves it back to draft).
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/refine-spec.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (spec slug - required; optional --section flag)
+</context>
+
+<process>
+**Follow the refine-spec workflow** from `@~/.claude/deliver-great-systems/workflows/refine-spec.md`.
+
+The workflow handles:
+1. Argument parsing (extract spec-slug, optional --section)
+2. Spec lookup and content loading
+3. Final-status warning (asks before demoting to draft)
+4. Project context loading for informed refinement
+5. Section targeting (if --section provided)
+6. Conversational refinement dialogue
+7. Atomic save (version increment, body update, format-preserving write)
+8. Refinement Log entry and git commit
+</process>

package/commands/dgs/reject-idea.md

@@ -0,0 +1,43 @@
+---
+name: dgs:reject-idea
+description: Reject an idea, moving it from pending to rejected
+argument-hint: <idea-id>
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - AskUserQuestion
+---
+
+<objective>
+Reject a pending idea, moving it from pending to rejected state.
+
+Routes to the reject-idea workflow which handles:
+- Finding and displaying the idea
+- Confirmation before rejection (always required, no --force bypass)
+- Optional rejection reason prompt
+- State transition via git mv
+- Auto-commit to git
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/reject-idea.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (idea ID)
+
+State is resolved in-workflow via dgs-tools.cjs ideas list.
+</context>
+
+<process>
+**Follow the reject-idea workflow** from `@~/.claude/deliver-great-systems/workflows/reject-idea.md`.
+
+The workflow handles all logic including:
+1. Argument parsing (idea ID extraction)
+2. Finding and displaying the idea to confirm identity
+3. Confirmation prompt (always required)
+4. Optional rejection reason prompt
+5. State transition from pending/ to rejected/ via git mv
+6. Auto-commit to git
+</process>

package/commands/dgs/remove-doc.md

@@ -0,0 +1,44 @@
+---
+name: dgs:remove-doc
+description: Remove a document or move it between scopes
+argument-hint: <slug> --scope <product|idea|spec> [--scope-id <id>] [--move --to-scope <scope> --to-id <id>]
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - AskUserQuestion
+---
+
+<objective>
+Remove a document from its scope or move it between scopes. Removal requires mandatory confirmation (no --force bypass). Move mode relocates a document with its sidecars between scopes.
+
+Routes to the remove-doc workflow which handles:
+- Argument parsing (slug, scope, optional move flags)
+- Document existence verification
+- Confirmation prompt for removal (always required)
+- Document removal with sidecar cleanup
+- Document move between scopes via --move flag
+- Git commit for all changes
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/remove-doc.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (slug, scope, and optional move flags)
+
+Document operations are handled in-workflow via `dgs-tools.cjs docs` subcommands.
+</context>
+
+<process>
+**Follow the remove-doc workflow** from `@~/.claude/deliver-great-systems/workflows/remove-doc.md`.
+
+The workflow handles all logic including:
+1. Argument parsing (slug, scope, optional --move with --to-scope and --to-id)
+2. Document existence verification
+3. Mandatory confirmation for removal (no --force bypass)
+4. Removal via dgs-tools with sidecar cleanup and INDEX.md update
+5. Move via dgs-tools with source and target INDEX.md updates
+6. Git commit for all affected files
+</process>

package/commands/dgs/remove-phase.md

@@ -0,0 +1,31 @@
+---
+name: dgs:remove-phase
+description: Remove a future phase from roadmap and renumber subsequent phases
+argument-hint: <phase-number>
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+---
+<objective>
+Remove an unstarted future phase from the roadmap and renumber all subsequent phases to maintain a clean, linear sequence.
+
+Purpose: Clean removal of work you've decided not to do, without polluting context with cancelled/deferred markers.
+Output: Phase deleted, all subsequent phases renumbered, git commit as historical record.
+</objective>
+
+<execution_context>
+@~/.claude/deliver-great-systems/workflows/remove-phase.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS
+
+Roadmap and state are resolved in-workflow via `init phase-op` and targeted reads.
+</context>
+
+<process>
+Execute the remove-phase workflow from @~/.claude/deliver-great-systems/workflows/remove-phase.md end-to-end.
+Preserve all validation gates (future phase check, work check), renumbering logic, and commit.
+</process>

package/commands/dgs/remove-repo.md

@@ -0,0 +1,69 @@
+---
+name: dgs:remove-repo
+description: Unregister a repository from REPOS.md
+argument-hint: "<repo-name>"
+allowed-tools:
+  - Read
+  - Bash
+  - AskUserQuestion
+---
+<objective>
+Unregister a repository from REPOS.md. Includes safety checks — if active projects reference the repo, shows a warning and requires explicit confirmation before force-removing.
+</objective>
+
+<process>
+
+## 1. Parse Arguments
+
+Extract repo name from `$ARGUMENTS`.
+
+If no name provided, list repos and ask user to pick:
+```bash
+LIST=$(node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs projects list --raw)
+```
+Parse the response to show available repos, then use AskUserQuestion to ask which repo to remove.
+
+## 2. Attempt Removal
+
+```bash
+RESULT=$(node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs repos remove "$REPO_NAME" --raw)
+```
+
+Parse JSON response.
+
+**If `removed: true`:**
+```
+DGS > REPO REMOVED
+
+Repository "{repo}" has been unregistered from REPOS.md.
+```
+
+**If `removed: false` (active projects reference this repo):**
+```
+DGS > REPO REMOVAL BLOCKED
+
+Repository "{repo}" is referenced by active projects:
+- {project1}
+- {project2}
+
+Removing it may break these projects' repo resolution.
+```
+
+Use AskUserQuestion:
+```
+Force remove "{repo}" despite active project references? Type "yes" to force remove or "no" to cancel.
+```
+
+If user confirms, run force removal:
+```bash
+RESULT=$(node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs repos remove "$REPO_NAME" --force --raw)
+```
+
+Display result.
+
+If user declines, display "Cancelled. Repo was not removed." and exit.
+
+**If error:**
+Display the error message from the response.
+
+</process>