@ktpartners/dgs-platform 2.7.3 → 2.7.5

package/agents/dgs-roadmapper.md

@@ -92,6 +92,32 @@ If a requirement fits multiple phases → assign to ONE (usually the first that
 
 </philosophy>
 
+<milestone_handling>
+
+## Milestone Version
+
+The orchestrator passes a `<milestone>` block in the planning context with `version` and `name`.
+
+**Reading:** Extract `version` (e.g., "v17.0") and `name` (e.g., "Git Push and Pull Integration") from the `<milestone>` tag in the prompt.
+
+**If no `<milestone>` block provided:** Default to `v1.0` / `milestone` (greenfield).
+
+**Usage:**
+
+When writing **STATE.md frontmatter**, use the provided version:
+```yaml
+---
+dgs_state_version: 1.0
+milestone: {version}       # e.g., v17.0, NOT hardcoded v1.0
+milestone_name: {name}
+status: planning
+---
+```
+
+When writing **ROADMAP.md**, use the version in milestone headings and references instead of assuming v1.0.
+
+</milestone_handling>
+
 <goal_backward_phases>
 
 ## Deriving Phase Success Criteria
@@ -402,6 +428,7 @@ Orchestrator provides:
 - REQUIREMENTS.md content (v1 requirements with REQ-IDs)
 - research/SUMMARY.md content (if exists - phase suggestions)
 - config.json (granularity setting)
+- Milestone version and name (from `<milestone>` block -- use when writing STATE.md/ROADMAP.md)
 
 Parse and confirm understanding before proceeding.
 
@@ -462,8 +489,10 @@ If gaps found, include in draft for user decision.
 Write files first, then return. This ensures artifacts persist even if context is lost.
 
 1. **Write ROADMAP.md** using output format
+   Use milestone version from `<milestone>` block for headings (e.g., "v17.0 [Name]" not "v1.0 MVP").
 
 2. **Write STATE.md** using output format
+   Use milestone version from `<milestone>` block in frontmatter (`milestone: {version}`, `milestone_name: {name}`).
 
 3. **Update REQUIREMENTS.md traceability section**
 

package/deliver-great-systems/bin/lib/init.cjs

@@ -397,6 +397,7 @@ function cmdInitNewProject(cwd, raw) {
   const config = loadConfig(cwd);
   const ctx = resolveProjectContext(cwd);
   const planRootRel = path.relative(cwd, getPlanningRoot(cwd)) || '.';
+  const milestone = getMilestoneInfo(cwd);
 
   // Detect Brave Search API key availability
   const homedir = require('os').homedir();
@@ -461,6 +462,10 @@ function cmdInitNewProject(cwd, raw) {
     requirements_path: ctx.root ? path.join(ctx.root, 'REQUIREMENTS.md') : path.join(planRootRel, 'REQUIREMENTS.md'),
     research_dir: ctx.root ? path.join(ctx.root, 'research') : path.join(planRootRel, 'research'),
 
+    // Milestone info (product-level, shared across projects)
+    milestone_version: milestone.version,
+    milestone_name: milestone.name,
+
     // v2 context
     dgs_mode: ctx.dgs_mode,
     current_project: ctx.current_project,

package/deliver-great-systems/bin/lib/init.test.cjs

@@ -227,6 +227,14 @@ describe('v1 mode: init new-project', () => {
   it('returns dgs_mode v1', () => {
     assert.equal(result.dgs_mode, 'v1');
   });
+
+  it('returns milestone_version defaulting to v1.0 when no milestones exist', () => {
+    assert.equal(result.milestone_version, 'v1.0');
+  });
+
+  it('returns milestone_name defaulting to milestone', () => {
+    assert.equal(result.milestone_name, 'milestone');
+  });
 });
 
 // ─── v1 Mode: other init commands ────────────────────────────────────────────
@@ -462,6 +470,10 @@ describe('v2 mode with project: init new-project', () => {
   it('returns dgs_mode v2', () => {
     assert.equal(result.dgs_mode, 'v2');
   });
+
+  it('returns milestone_version defaulting to v1.0 when no milestones exist', () => {
+    assert.equal(result.milestone_version, 'v1.0');
+  });
 });
 
 describe('v2 mode with project: init progress', () => {

package/deliver-great-systems/workflows/new-project.md

@@ -64,7 +64,7 @@ If the `--auto` argument references a spec file path or spec ID:
 INIT=$(node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs init new-project)
 ```
 
-Parse JSON for: `researcher_model`, `synthesizer_model`, `roadmapper_model`, `commit_docs`, `project_exists`, `has_codebase_map`, `planning_exists`, `has_existing_code`, `has_package_file`, `is_brownfield`, `needs_codebase_map`, `has_git`, `project_path`, `state_path`, `roadmap_path`, `requirements_path`, `research_dir`.
+Parse JSON for: `researcher_model`, `synthesizer_model`, `roadmapper_model`, `commit_docs`, `project_exists`, `has_codebase_map`, `planning_exists`, `has_existing_code`, `has_package_file`, `is_brownfield`, `needs_codebase_map`, `has_git`, `project_path`, `state_path`, `roadmap_path`, `requirements_path`, `research_dir`, `milestone_version`, `milestone_name`.
 
 Load planning-tier context files:
 
@@ -857,6 +857,11 @@ Task(prompt="
 ${product_doc_files}
 </files_to_read>
 
+<milestone>
+version: ${milestone_version}
+name: ${milestone_name}
+</milestone>
+
 </planning_context>
 
 <instructions>
@@ -864,6 +869,7 @@ Create roadmap:
 1. Derive phases from requirements (don't impose structure)
 2. Map every v1 requirement to exactly one phase
 3. Derive 2-5 success criteria per phase (observable user behaviors)
+Use the milestone version from <milestone> when writing STATE.md frontmatter and ROADMAP.md headings.
 4. Validate 100% coverage
 5. Write files immediately (ROADMAP.md, STATE.md, update REQUIREMENTS.md traceability)
 6. Return ROADMAP CREATED with summary

package/deliver-great-systems/workflows/quick.md

@@ -208,8 +208,7 @@ Commit message is NOT shown to user before committing — just commit silently.
 **F5. Commit**
 
 ```bash
-git add -A
-git commit -m "${commit_message}"
+node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" commit "${commit_message}" --push
 ```
 
 Get the short hash:
@@ -264,11 +263,11 @@ If archival occurred (result contains `"archived": true`), `.planning/quick/HIST
 Commit STATE.md and HISTORY.md together so archival data is persisted:
 
 ```bash
-git add "${state_path}"
+FILE_LIST="${state_path}"
 if [ -f "${project_root}/quick/HISTORY.md" ]; then
-  git add "${project_root}/quick/HISTORY.md"
+  FILE_LIST="${FILE_LIST} ${project_root}/quick/HISTORY.md"
 fi
-git commit -m "docs(quick-${quick_id}): track fast task" 2>/dev/null || true
+node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" commit "docs(quick-${quick_id}): track fast task" --push --files ${FILE_LIST} 2>/dev/null || true
 ```
 
 The `|| true` handles the case where nothing changed (e.g., STATE.md wasn't modified).

package/deliver-great-systems/workflows/settings.md

@@ -276,6 +276,11 @@ Set config:
 node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-set workflow.discipline true
 ```
 
+Track CLAUDE.md as modified:
+```bash
+MODIFIED_FILES="${MODIFIED_FILES} ./CLAUDE.md"
+```
+
 Display: `Workflow discipline: On`
 
 **If user selects "Off" (toggle off):**
@@ -314,6 +319,11 @@ Set config:
 node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" config-set workflow.discipline false
 ```
 
+Track CLAUDE.md as modified:
+```bash
+MODIFIED_FILES="${MODIFIED_FILES} ./CLAUDE.md"
+```
+
 Display: `Workflow discipline: Off`
 
 **If "Cancel":**
@@ -421,6 +431,12 @@ Do NOT use AskUserQuestion for any review settings.
 </step>
 
 <step name="update_config">
+Track which files will be modified for the commit step:
+
+```bash
+MODIFIED_FILES="${config_path}"
+```
+
 Merge new settings into existing config:
 
 ```json
@@ -497,6 +513,20 @@ Write `~/.dgs/defaults.json` with:
 ```
 </step>
 
+<step name="commit_and_push">
+Commit the config changes and push if sync_push is enabled:
+
+```bash
+node "$HOME/.claude/deliver-great-systems/bin/dgs-tools.cjs" commit "chore: update DGS settings" --push --files ${MODIFIED_FILES}
+```
+
+This uses dgs-tools commit which:
+- Stages only the specified files
+- Creates the commit
+- With --push, reads sync_push from config and pushes when mode is "auto" (silently) or "prompt" (asks first)
+- If sync_push is "off", no push occurs (commit-only)
+</step>
+
 <step name="confirm">
 Display:
 

package/deliver-great-systems/workflows/update.md

@@ -121,7 +121,7 @@ Exit.
 <step name="show_changes_and_confirm">
 **If update available**, fetch and show what's new BEFORE updating:
 
-1. Fetch changelog from GitHub raw URL
+1. Read changelog from installed package (CHANGELOG.md in the DGS install directory)
 2. Extract entries between installed and latest versions
 3. Display preview and ask for confirmation:
 
@@ -209,7 +209,7 @@ Format completion message (changelog was already shown in confirmation step):
 
 ⚠️  Restart Claude Code to pick up the new commands.
 
-[View full changelog](https://github.com/glittercowboy/deliver-great-systems/blob/main/CHANGELOG.md)
+[View full changelog](https://github.com/KT-Partners-Ltd/deliver-great-systems/blob/main/CHANGELOG.md)
 ```
 </step>
 

package/package.json

@@ -1,10 +1,14 @@
 {
   "name": "@ktpartners/dgs-platform",
   "homepage": "https://kt-partners-ltd.github.io/dgs-platform-docs/",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/KT-Partners-Ltd/deliver-great-systems.git"
+  },
   "bugs": {
     "url": "https://github.com/KT-Partners-Ltd/dgs-platform-docs/issues"
   },
-  "version": "2.7.3",
+  "version": "2.7.5",
   "description": "Deliver Great Systems Platform — A meta-prompting, context engineering and spec-driven development system for Claude Code and Gemini by KT Partners.",
   "bin": {
     "dgs": "bin/install.js"
@@ -18,7 +22,8 @@
     "agents",
     "hooks/dist",
     "scripts",
-    "LICENSE"
+    "LICENSE",
+    "CHANGELOG.md"
   ],
   "keywords": [
     "claude",