@ktpartners/dgs-platform 2.7.5 → 2.8.0

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

@@ -22,23 +22,14 @@ Display the complete DGS command reference. Output ONLY the reference content. D
 3. `/dgs:plan-phase 1` - Plan first phase (repos tracked per task)
 4. `/dgs:execute-phase 1` - Execute (commits per-repo automatically)
 
-## Layout Detection
+## Project Structure
 
-DGS supports two directory layouts:
+Planning artifacts live at the repo root. DGS detects single-project or multi-project mode automatically:
 
-- **`.planning/` layout (default):** Planning artifacts live in a `.planning/` subdirectory. Standard for repos that also contain source code.
-- **Root layout:** Planning artifacts live at the repo root. For dedicated planning repos where DGS owns the entire directory.
+- **v1 (single-project):** Standard setup. PROJECT.md, ROADMAP.md, STATE.md, phases/ live at root. All existing commands work as before.
+- **v2 (multi-project):** Detected when `PROJECTS.md` or `REPOS.md` exists. Project artifacts live under `projects/<project-slug>/`. Commands available for repo management and project switching.
 
-Choose your layout during `/dgs:init-product`. DGS detects the active layout from `dgs.config.json` and resolves all paths automatically.
-
-### v1 vs v2 Detection
-
-Within either layout, DGS detects single-project or multi-project mode:
-
-- **v1 (single-project):** Standard setup. The planning root contains PROJECT.md, ROADMAP.md, STATE.md, phases/ directly. All existing commands work as before.
-- **v2 (multi-project):** Detected when `PROJECTS.md` or `REPOS.md` exists in the planning root. Project artifacts live under `<planning-root>/<project-slug>/`. New commands available for repo management and project switching.
-
-No migration required. v1 installations continue working unchanged. Run `/dgs:init-product` when you want to adopt v2 features.
+Run `/dgs:init-product` to set up multi-project mode.
 
 ## Staying Updated
 
@@ -97,7 +88,7 @@ Creates project artifacts:
 - `ROADMAP.md` — phases mapped to requirements
 - `STATE.md` — project memory
 
-**v2 additions:** Prompts for project name (used as folder slug), prompts for which repos this project touches (from REPOS.md), checks for overlap with other active projects. Artifacts are created under `<planning-root>/<project-slug>/`.
+**v2 additions:** Prompts for project name (used as folder slug), prompts for which repos this project touches (from REPOS.md), checks for overlap with other active projects. Artifacts are created under `projects/<project-slug>/`.
 
 Usage: `/dgs:new-project`
 
@@ -143,7 +134,7 @@ Usage: `/dgs:map-codebase --only api-service` (same, explicit flag)
 Switch active project context. *(Tier 1: lite)*
 
 - If no name given, shows picker with all active projects
-- Sets `current_project` in `dgs.config.json`
+- Sets `current_project` in `config.json`
 - All subsequent DGS commands operate on the selected project
 - Shows brief status of the switched-to project
 
@@ -698,7 +689,7 @@ Configure workflow toggles and model profile interactively. *(Tier 1: lite)*
 
 - Toggle researcher, plan checker, verifier agents
 - Select model profile (quality/balanced/budget)
-- Updates `dgs.config.json`
+- Updates `config.json`
 
 Usage: `/dgs:settings`
 
@@ -759,41 +750,13 @@ Usage: `/dgs:join-discord`
 
 ## Files & Structure
 
-DGS supports two directory layouts. Choose during `/dgs:init-product`:
-
-### .planning/ Layout (Default)
+### Directory Layout
 
-Standard layout for repos that also contain source code:
+Planning artifacts live at the repo root:
 
 ```
 my-repo/
-├── .planning/                # Planning root
-│   ├── dgs.config.json       # Workflow mode & gates
-│   ├── PROJECT.md            # Project vision
-│   ├── ROADMAP.md            # Current phase breakdown
-│   ├── STATE.md              # Project memory & context
-│   ├── REQUIREMENTS.md       # Scoped requirements
-│   ├── todos/                # Captured ideas and tasks
-│   ├── debug/                # Active debug sessions
-│   ├── milestones/           # Archived milestone snapshots
-│   ├── codebase/             # Codebase map (brownfield projects)
-│   └── phases/               # Phase directories
-│       ├── 01-foundation/
-│       │   ├── 01-01-PLAN.md
-│       │   └── 01-01-SUMMARY.md
-│       └── 02-core-features/
-│           ├── 02-01-PLAN.md
-│           └── 02-01-SUMMARY.md
-└── src/                      # Your source code
-```
-
-### Root Layout
-
-For dedicated planning repos where DGS owns the entire directory:
-
-```
-my-planning-repo/
-├── dgs.config.json           # Workflow mode & gates
+├── config.json               # Workflow mode & gates
 ├── PROJECT.md                # Project vision
 ├── ROADMAP.md                # Current phase breakdown
 ├── STATE.md                  # Project memory & context
@@ -804,21 +767,25 @@ my-planning-repo/
 ├── codebase/                 # Codebase map (brownfield projects)
 └── phases/                   # Phase directories
     ├── 01-foundation/
+    │   ├── 01-01-PLAN.md
+    │   └── 01-01-SUMMARY.md
     └── 02-core-features/
+        ├── 02-01-PLAN.md
+        └── 02-01-SUMMARY.md
 ```
 
 ### v2 (Multi-Project, Multi-Repo)
 
-Multi-project mode works with either layout. Planning root contains project subfolders:
+Multi-project mode adds project subfolders and a repo registry:
 
 ```
 my-product/                        # Product folder (git repo)
-├── <planning-root>/               # .planning/ or repo root
-│   ├── REPOS.md                   # Repo registry (names, paths, URLs)
-│   ├── PROJECTS.md                # Project index (auto-generated)
-│   ├── dgs.config.json            # Product-level config
-│   ├── codebase/                  # Shared codebase map
-│   │   └── <repo-name>/          # Per-repo codebase maps
+├── REPOS.md                       # Repo registry (names, paths, URLs)
+├── PROJECTS.md                    # Project index (auto-generated)
+├── config.json                    # Product-level config
+├── codebase/                      # Shared codebase map
+│   └── <repo-name>/              # Per-repo codebase maps
+├── projects/
 │   ├── auth-overhaul/             # Project: auth-overhaul
 │   │   ├── PROJECT.md
 │   │   ├── REQUIREMENTS.md
@@ -840,7 +807,7 @@ my-product/                        # Product folder (git repo)
 
 **Key concepts:**
 - **Product** = top-level container with its own git repo for planning changes
-- **Project** = a unit of work (feature, initiative). Lives in `<planning-root>/<project-slug>/`. Multiple can be active.
+- **Project** = a unit of work (feature, initiative). Lives in `projects/<project-slug>/`. Multiple can be active.
 - **Repo** = a source code repository. Registered in REPOS.md. Projects can touch multiple repos.
 
 ## Workflow Modes
@@ -859,11 +826,11 @@ Set during `/dgs:new-project`:
 - Executes plans without confirmation
 - Only stops for critical checkpoints
 
-Change anytime by editing `dgs.config.json`
+Change anytime by editing `config.json`
 
 ## Planning Configuration
 
-Configure how planning artifacts are managed in `dgs.config.json`:
+Configure how planning artifacts are managed in `config.json`:
 
 **`planning.commit_docs`** (default: `true`)
 - `true`: Planning artifacts committed to git (standard workflow)